ScreenConnect Unable to Start on Fedora 33
-
@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.
-
oh boy, I've not tried that version yet. That might take some research.
-
@scottalanmiller Probably not worth the effort at this point. Everything else on the system is working and since Screenconnect for linux is EOL, I need to move away from it. Someone else (on reddit) suggested migrating to a Windows install temporarily to help migrate the clients to whatever is next; they at least have a guide for that on the website, seems like it should be easy. Gonna have to install MeshCentral and give it a go I think. I looked like about the only low cost (free in this instance) self hosted multiple client option I could find.
-
@toomanytoons said in ScreenConnect Unable to Start on Fedora 33:
@scottalanmiller Probably not worth the effort at this point. Everything else on the system is working and since Screenconnect for linux is EOL, I need to move away from it. Someone else (on reddit) suggested migrating to a Windows install temporarily to help migrate the clients to whatever is next; they at least have a guide for that on the website, seems like it should be easy. Gonna have to install MeshCentral and give it a go I think. I looked like about the only low cost (free in this instance) self hosted multiple client option I could find.
TacticalRMM includes a MeshCentral instance. You can use the MeshCentral instance as a standalone if you want. I'm using TacticalRMM for a bunch of personal stuff, and I've not had an issue with it yet.
-
@toomanytoons said in ScreenConnect Unable to Start on Fedora 33:
@scottalanmiller Probably not worth the effort at this point. Everything else on the system is working and since Screenconnect for linux is EOL, I need to move away from it. Someone else (on reddit) suggested migrating to a Windows install temporarily to help migrate the clients to whatever is next; they at least have a guide for that on the website, seems like it should be easy. Gonna have to install MeshCentral and give it a go I think. I looked like about the only low cost (free in this instance) self hosted multiple client option I could find.
Fixing Linux is likely easier than the Windows install, but yes. We were in the same boat for SO many reasons, we dumped it and thank goodness, since they were hacked (for the very reasons we dumped them - no support, no idea how to write code, no patching, no updates.) They were a good product in the past but went hard core downhill and since about four years ago I would not trust them to be installed on my equipment. I don't trust the work of their developers, their code decisions that we can see have long been questionable at best and quickly became outright pathetically unqualified. For a system that is so key to security, I'd never qualify it as deployable today. I'd move off as quickly as you can.
Given that vastly better quality, more professionally approached software is free today, I see no value to this stuff and its ilk. And certainly nothing from ConnectWise will ever be allowed in our shop again.
-
@travisdh1 said in ScreenConnect Unable to Start on Fedora 33:
@toomanytoons said in ScreenConnect Unable to Start on Fedora 33:
@scottalanmiller Probably not worth the effort at this point. Everything else on the system is working and since Screenconnect for linux is EOL, I need to move away from it. Someone else (on reddit) suggested migrating to a Windows install temporarily to help migrate the clients to whatever is next; they at least have a guide for that on the website, seems like it should be easy. Gonna have to install MeshCentral and give it a go I think. I looked like about the only low cost (free in this instance) self hosted multiple client option I could find.
TacticalRMM includes a MeshCentral instance. You can use the MeshCentral instance as a standalone if you want. I'm using TacticalRMM for a bunch of personal stuff, and I've not had an issue with it yet.
We replaced ScreenConnect with MeshCentral and years ago the transition was rough, but today MC is beyond parity and by far the leader rather than the follower. More features, way better everything. We added Tactical later, but if you are deploying new today, yeah, start with Tactical and get both for free right from the beginning.
-
@scottalanmiller said in ScreenConnect Unable to Start on Fedora 33:
@travisdh1 said in ScreenConnect Unable to Start on Fedora 33:
@toomanytoons said in ScreenConnect Unable to Start on Fedora 33:
@scottalanmiller Probably not worth the effort at this point. Everything else on the system is working and since Screenconnect for linux is EOL, I need to move away from it. Someone else (on reddit) suggested migrating to a Windows install temporarily to help migrate the clients to whatever is next; they at least have a guide for that on the website, seems like it should be easy. Gonna have to install MeshCentral and give it a go I think. I looked like about the only low cost (free in this instance) self hosted multiple client option I could find.
TacticalRMM includes a MeshCentral instance. You can use the MeshCentral instance as a standalone if you want. I'm using TacticalRMM for a bunch of personal stuff, and I've not had an issue with it yet.
We replaced ScreenConnect with MeshCentral and years ago the transition was rough, but today MC is beyond parity and by far the leader rather than the follower. More features, way better everything. We added Tactical later, but if you are deploying new today, yeah, start with Tactical and get both for free right from the beginning.
being stuck in the browser still sucks compared to the stand alone window of SC.
-
@Dashrender said in ScreenConnect Unable to Start on Fedora 33:
@scottalanmiller said in ScreenConnect Unable to Start on Fedora 33:
@travisdh1 said in ScreenConnect Unable to Start on Fedora 33:
@toomanytoons said in ScreenConnect Unable to Start on Fedora 33:
@scottalanmiller Probably not worth the effort at this point. Everything else on the system is working and since Screenconnect for linux is EOL, I need to move away from it. Someone else (on reddit) suggested migrating to a Windows install temporarily to help migrate the clients to whatever is next; they at least have a guide for that on the website, seems like it should be easy. Gonna have to install MeshCentral and give it a go I think. I looked like about the only low cost (free in this instance) self hosted multiple client option I could find.
TacticalRMM includes a MeshCentral instance. You can use the MeshCentral instance as a standalone if you want. I'm using TacticalRMM for a bunch of personal stuff, and I've not had an issue with it yet.
We replaced ScreenConnect with MeshCentral and years ago the transition was rough, but today MC is beyond parity and by far the leader rather than the follower. More features, way better everything. We added Tactical later, but if you are deploying new today, yeah, start with Tactical and get both for free right from the beginning.
being stuck in the browser still sucks compared to the stand alone window of SC.
I think it's better. Faster and more efficient. Fewer problems. More standard across platforms. No need for Java. The SC Java client was the worst and so many support issues.
That said, I'm not stuck in the browser on MC. I just choose it because its superior. You can use an RDP client if you want for Windows users.
-
@scottalanmiller said in ScreenConnect Unable to Start on Fedora 33:
You can use an RDP client if you want for Windows users.
I've read that - I need to figure how how that works.
-
@Dashrender said in ScreenConnect Unable to Start on Fedora 33:
@scottalanmiller said in ScreenConnect Unable to Start on Fedora 33:
You can use an RDP client if you want for Windows users.
I've read that - I need to figure how how that works.
We have some customers using them, but we don't use them internally AFAIK.
