Solved Unable to turn up ScreenConnect server on Fedora 28
-
@hobbit666 said in Unable to turn up ScreenConnect server on Fedora 28:
Strange, I've got it running on a Fedora 28 machine.
Give me 10 or so and i'll try and dig out my instructions I made while installing it.
I had no issues on CentOS 7 previously.
I did not expect any issues here.
Haven't had troubleshooting time yet.
I installed Fedora 28 minimal. installed
tarandwget. Disabled selinux. Ran the installer and had problems.So I installed Fedora 28 Server. Same result on install. no packages needed installed though.
I'm visiting my dad, so I'll do more troublshooting tonight or tomorrow.
-
Just had a look and looks like I didn't do a "install guide" for ScreenConnect when I re-did all my Linux servers on HyperV host
I think I had some issues but I think the solutions were on the ConnectWise Forums.
-
Apparently is an issue with the Mono package as below:
https://github.com/mono/mono/issues/6752 -
@jaredbusch said in Unable to turn up ScreenConnect server on Fedora 28:
System.Exception: Magic number is wrong: 542
Searching for the error leads to a mono bug https://github.com/mono/mono/issues/6752#issuecomment-365212655
Which supposedly you can get working by exporting an enviromental variable
export TERM=xtermAccording to the last comment on the thread https://github.com/mono/mono/issues/6752#issuecomment-404527450 the issue fix should already be backported on fedora which makes it strange as the error is happening on fedora 28 for jared.
-
@romo said in Unable to turn up ScreenConnect server on Fedora 28:
export TERM=xterm
This did resolve my problem. Sorry for not posting sooner.
@romo said in Unable to turn up ScreenConnect server on Fedora 28:
According to the last comment on the thread https://github.com/mono/mono/issues/6752#issuecomment-404527450 the issue fix should already be backported on fedora which makes it strange as the error is happening on fedora 28 for jared.
The comment said it was backported by Fedora, but I saw no links, just the comment saying it was backported.
@scottalanmiller tag his post as the answer.
-
Once it was working with the above fix, I hadn'thad time to take our systemdown and move it.
Just did that today. Working perfectly.
-
Answer marked.
-
Just went to upgrade the install today to the current version and had this error again.
Again, setting up the
TERMvariable prior to running./install.shresolved the issue. -
Still an issue with ScreenConnect 19.1
-
Recently posted this...
So anyone that wants to configure Nginx in front of it can do that, too.
