ScreenConnect Unable to Start on Fedora 33
-
If you are running Screenconnect, at least some versions, on Fedora 33 you may find that it cannot start. If you use netstat -tulpn you will find that mono is running on ports 8041 and 8042, but not on critical 8040. Check your logs, there is likely an issue with
libc.soWhat to do? This is a little dangerous, so only do this on a dedicated ScreenConnect system:
- Change directory into /usr/lib64 -
cd /usr/lib64 - Remove the existing
libc.sofile -mv libc.so /opt - Symlink the file to an older version -
ln -s libc-2.32.so libc.so - Restart SC -
systemctl restart screenconnect
Simple to say, but very complex to track down. SC should be up and running now.
- Change directory into /usr/lib64 -
-
Some updates can cause this to revert, so be aware that you might want to set something up to verify it.
-
@scottalanmiller said in ScreenConnect Unable to Start on Fedora 33:
Some updates can cause this to revert, so be aware that you might want to set something up to verify it.
What Updates? I have not seen an update to the Linux server version in months.
-
@JaredBusch said in ScreenConnect Unable to Start on Fedora 33:
@scottalanmiller said in ScreenConnect Unable to Start on Fedora 33:
Some updates can cause this to revert, so be aware that you might want to set something up to verify it.
What Updates? I have not seen an update to the Linux server version in months.
Something that touches that library.
-
@scottalanmiller said in ScreenConnect Unable to Start on Fedora 33:
@JaredBusch said in ScreenConnect Unable to Start on Fedora 33:
@scottalanmiller said in ScreenConnect Unable to Start on Fedora 33:
Some updates can cause this to revert, so be aware that you might want to set something up to verify it.
What Updates? I have not seen an update to the Linux server version in months.
Something that touches that library.
ah, Fedora updates.. Understood.
-
FYI, CentOS updates do that as well. Constantly.
-
@scottalanmiller said in ScreenConnect Unable to Start on Fedora 33:
FYI, CentOS updates do that as well. Constantly.
Because of the lack of updating from ConnectWise, I moved my instance to Windows Server on Vultr.
-
@jaredbusch said in ScreenConnect Unable to Start on Fedora 33:
@scottalanmiller said in ScreenConnect Unable to Start on Fedora 33:
FYI, CentOS updates do that as well. Constantly.
Because of the lack of updating from ConnectWise, I moved my instance to Windows Server on Vultr.
Even with many updates, they never fixed it. They aren't updating now, but they went years and many major releases with the bug and never fixed it. I'd never deploy them on Windows because of their fundamental lack of support. I don't trust them at all. When Linux was "supported" they had no clue how to make it work. Going to Windows because it's limping along there and hasn't exposed their total lack of support doesn't install confidence. It just hides the underlying issue.
Given that I know that they are not supporting the product and don't know how to work their own software work, I don't feel that I could have it deployed any longer. If anyone is begging to be the next Kaseya...
-
@scottalanmiller said in ScreenConnect Unable to Start on Fedora 33:
@jaredbusch said in ScreenConnect Unable to Start on Fedora 33:
@scottalanmiller said in ScreenConnect Unable to Start on Fedora 33:
FYI, CentOS updates do that as well. Constantly.
Because of the lack of updating from ConnectWise, I moved my instance to Windows Server on Vultr.
Even with many updates, they never fixed it. They aren't updating now, but they went years and many major releases with the bug and never fixed it. I'd never deploy them on Windows because of their fundamental lack of support. I don't trust them at all. When Linux was "supported" they had no clue how to make it work. Going to Windows because it's limping along there and hasn't exposed their total lack of support doesn't install confidence. It just hides the underlying issue.
Given that I know that they are not supporting the product and don't know how to work their own software work, I don't feel that I could have it deployed any longer. If anyone is begging to be the next Kaseya...
Just because you never used Windows, does not mean it is poor quality, unsupported, or secondary. ScreenConnect was only ever developed for Windows. Having a Linux server was always an after thought. This was true years before it was purchased by ConnectWise.
As of June it is has been officially killed anyway.
As for your current favorite, Mesh Central? It is horrible to use in the browser as a technician. That you force your people to use it does not make it a good experience.
If they ever fixed that, I would consider moving things.
-
@jaredbusch said in ScreenConnect Unable to Start on Fedora 33:
Just because you never used Windows, does not mean it is poor quality, unsupported, or secondary.
That's really not relevant. What I tested was their support as it was sold and it was garbage to the point that I could never in good faith use the product. That you have used the Windows version and not witnessed their incompetence because that process hides it doesn't mean that it isn't there. The issues with their support are fact, and you ran into them (and mentioned them.) They failed to support the product. That we saw this lack of support only on Linux is irrelevant. It was a supported platform at the time, they didn't provide support. That's the issue. Linux vs Windows isn't relevant when the issue is their lack of standing behind the product and/or knowing what they are doing.
-
@jaredbusch said in ScreenConnect Unable to Start on Fedora 33:
ScreenConnect was only ever developed for Windows.
You are calling them liars then, because they sold is as "for Linux" and "with support." So if you are saying that they are dishonest people, you are making my point. I was just calling them incompetent, you are calling them dishonest crooks.
In my case, I was worried about putting someone incompetent in a position of risking customer data. In your case, I'd worry that they themselves would steal customer data. Once a thief, where do you draw the line? It seems like deploying them is letting the wolf in the door.
-
@jaredbusch said in ScreenConnect Unable to Start on Fedora 33:
Having a Linux server was always an after thought. This was true years before it was purchased by ConnectWise.
Not to their sales and marketing department, the official representatives of the business.
-
@jaredbusch said in ScreenConnect Unable to Start on Fedora 33:
It is horrible to use in the browser as a technician. That you force your people to use it does not make it a good experience.
Having used both, I'd say that about SC. For techs, I prefer MC by a wide margin. It's faster and easier. I have issues resolved before SC even gives me access. And needing to install Java to run SC... hell no. What a freaking joke even when it works.
-
@jaredbusch said in ScreenConnect Unable to Start on Fedora 33:
That you force your people to use it does not make it a good experience.
I don't let them make excuses to waste time. We get far more done on MC. It's not perfect. But security and efficiency have to take some precedence over "people are used to the quirks."
-
@jaredbusch said in ScreenConnect Unable to Start on Fedora 33:
As for your current favorite, Mesh Central? It is horrible to use in the browser as a technician. That you force your people to use it does not make it a good experience.
If they ever fixed that, I would consider moving things.
This is my same feeling about MC.
I'm guessing Scott doesn't care about the GUI aspect of it much, and likely mostly lives on the commandline access to the devices.
-
@scottalanmiller said in ScreenConnect Unable to Start on Fedora 33:
@jaredbusch said in ScreenConnect Unable to Start on Fedora 33:
It is horrible to use in the browser as a technician. That you force your people to use it does not make it a good experience.
Having used both, I'd say that about SC. For techs, I prefer MC by a wide margin. It's faster and easier. I have issues resolved before SC even gives me access. And needing to install Java to run SC... hell no. What a freaking joke even when it works.
Where do you need java installed? I don't have java on my laptop and I use SC from it all the time... perhaps you're talking on the server side?
-
@dashrender said in ScreenConnect Unable to Start on Fedora 33:
@scottalanmiller said in ScreenConnect Unable to Start on Fedora 33:
@jaredbusch said in ScreenConnect Unable to Start on Fedora 33:
It is horrible to use in the browser as a technician. That you force your people to use it does not make it a good experience.
Having used both, I'd say that about SC. For techs, I prefer MC by a wide margin. It's faster and easier. I have issues resolved before SC even gives me access. And needing to install Java to run SC... hell no. What a freaking joke even when it works.
Where do you need java installed? I don't have java on my laptop and I use SC from it all the time... perhaps you're talking on the server side?
If you run a linux desktop you need to install
icedtea-webto load the connectwise session as a tech. -
@jaredbusch said in ScreenConnect Unable to Start on Fedora 33:
@dashrender said in ScreenConnect Unable to Start on Fedora 33:
@scottalanmiller said in ScreenConnect Unable to Start on Fedora 33:
@jaredbusch said in ScreenConnect Unable to Start on Fedora 33:
It is horrible to use in the browser as a technician. That you force your people to use it does not make it a good experience.
Having used both, I'd say that about SC. For techs, I prefer MC by a wide margin. It's faster and easier. I have issues resolved before SC even gives me access. And needing to install Java to run SC... hell no. What a freaking joke even when it works.
Where do you need java installed? I don't have java on my laptop and I use SC from it all the time... perhaps you're talking on the server side?
If you run a linux desktop you need to install
icedtea-webto load the connectwise session as a tech.That always used to work. But something changed at some point and it got more complex. I'm pretty sure it still works, but the old processes don't work the same.
-
@dashrender said in ScreenConnect Unable to Start on Fedora 33:
I'm guessing Scott doesn't care about the GUI aspect of it much, and likely mostly lives on the commandline access to the devices.
I care about how much the GUI lets me get the job done. The GUI portion of SC is superior, for sure. But the speed of getting in and out of hte GUi and other components is far superior on MC. I'm doing IT work, not remote work, via the console so that the GUI isn't quite as nice rarely has any effect.
-
Hey Scott,
Sorry to pull up such an old topic but I just ran into this same problem. I finally got around to updating my Ubuntu 18.04 to 22.04 and realized my screenconnect installation is having this exact issue, showing mono on port 8041/8042 instead of 8040/8041. Any idea how to fix it on Ubuntu 22.04? I found the libc.so in /usr/lib/x96_64-linux-gnu folder but it's just a text file thats says.../* GNU ld script
Use the shared library, but some functions are only in
the static library, so try that secondarily. */
OUTPUT_FORMAT(elf64-x86-64)
GROUP ( /lib/x86_64-linux-gnu/libc.so.6 /usr/lib/x86_64-linux-gnu/libc_nonshared.a AS_NEEDED ( /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 ) )Any ideas what I might be able to do to get this running again, at least until I can switch to something else?
Thanks for reading.
