Unable to turn up ScreenConnect server on Fedora 28

JaredBusch

Yes, I opened port 8040 on the firewall.

[jbusch@sc ~]$ firewall-cmd --add-port=8040/tcp --permanent
success
[jbusch@sc ~]$ firewall-cmd --reload
success

black3dynamite

This post is deleted!

black3dynamite

The installer depends on zlib.
I found it in the redhat.sh file, located in ScreenConnect_6.7.19388.6796_Install/Installer/Distributions/ directory

JaredBusch

@black3dynamite said in Unable to turn up ScreenConnect server on Fedora 28:

The installer depends on zlib.
I found it in the redhat.sh file, located in ScreenConnect_6.7.19388.6796_Install/Installer/Distributions/ directory

zlib is already installed, so that is not it.

hobbit666

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.

JaredBusch

@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 tar and wget. 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.

hobbit666

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.

dbeato

Apparently is an issue with the Mono package as below:
https://github.com/mono/mono/issues/6752

Romo

@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=xterm

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.

JaredBusch

@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.

JaredBusch

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.

scottalanmiller

Answer marked.

JaredBusch

Just went to upgrade the install today to the current version and had this error again.

Again, setting up the TERM variable prior to running ./install.sh resolved the issue.

JaredBusch

Still an issue with ScreenConnect 19.1

scottalanmiller

Recently posted this...

https://mangolassi.it/topic/20124/has-anyone-got-a-guide-to-installing-screenconnect-on-fedora-30-with-let-s-encrypt/

So anyone that wants to configure Nginx in front of it can do that, too.

Solved Unable to turn up ScreenConnect server on Fedora 28