Please add proper support for TLS 1.3 in Mono so that Chrome/Firefox users don't have to disable TLS 1.3 to make ScreenConnect work.
Related KB: https://docs.connectwise.com/ConnectWise_Control_Documentation/Technical_support_bulletins/Can_no_longer_load_Control_website_after_updating_Chrome
from the release notes:
Updated Mono support for Linux on-premises installations
We've updated the Mono architecture that's used for our Linux on-premises installers.This fixes many security issues such as TLS 1.0 limitations, and it helps us keep Mono up-to-date in the future.
We officially support these Linux distributions:
Could someone from Connectwise please give us an official answer on this?
I am currently using HAProxy with Centos to get TLS v1.3 compatibility
I am keen to build a new Ubuntu/ Debian VM to run without HAProxy, but can't do anything until this is conformed. Although v19.6 Stable doesn't appear to be available right now anyway...
Could someone from Connectwise please give us an official answer on this?
I am currently using HAProxy with Centos to get TLS v1.3 compatibility
I am keen to build a new Ubuntu/ Debian VM to run without HAProxy, but can't do anything until this is conformed. Although v19.6 Stable doesn't appear to be available right now anyway...
19.6 does support TLS 1.3, however, it causes service crashing. I am upgraded to it and have to keep rebooting services every 0.5-3 days.
Have not experienced the services instability but had problems installing Lets Encrypt SSL, have switched to paid basic RapidSSL and it works with TLS 1.3, but although installed using the SSL configurator, there is a problem with the intermediate cert which is not appearing in the chain, even though it is installed. But SSL is working OK for me - using Ubuntu 16.04, just needs the intermediate cert to work properly.
Until they switch from mono to .NET they will continue to have issues. Even with the latest update they STILL don't support deployments > 1,000 clients. We have 2,000 now and growing.
We have started to migrate to Mesh Central, free and works better than SC.
Until they switch from mono to .NET they will continue to have issues. Even with the latest update they STILL don't support deployments > 1,000 clients. We have 2,000 now and growing.
We have started to migrate to Mesh Central, free and works better than SC.
Thanks for the Mesh Central info... just in case Control Wise no longer want us ...???
Since Jeff Sold SC I personally have found keeping my on premises a real pain.
Thanks for the Mesh Central info... just in case Control Wise no longer want us ...???
Since Jeff Sold SC I personally have found keeping my on premises a real pain.
https://control.product.connectwise.com/communities/6/topics/2798-portal-not-responding
sc has said the writing is on the wlal fro Linux in another thread:
Thoughts for moving forward--
I actually think most of it has been fixed already in a 20.2 build. It's just in a parallel universe to our existing release pipeline, which is why it has lagged.
I personally think it's a shame the Linux/Mono usage has declined to such a degree. I thought it was neat technically we could really master (*ducks*) both platforms in a very unique way-- what other commercial product runs on Mono?
Our code base is in good shape and could be moved to .NET Core without a lot of obvious work. The one thing stopping it is our Extensions; most extensions have ASP.NET components, and we can't easily change and break compatibility without a lot of impact.
Y'all should probably see the writing on the wall if you haven't already. I know that when I'm a consumer of something, I like to feel like my business is valuable to the vendor. And although y'all are very valuable to me personally because I like Linux, I like arguing, I like critique of my creations, etc, I think y'all probably have an opinion about how much you think my superiors care about this particular enjoyment of mine. And we're sitting with just maybe 40-50 of y'all who are looking at a $65/year renewal? To the credit of my superiors, they have very much supported us doing the right thing and getting y'all in a good state, but we've spent a good $50k+ on this Linux/Mono refork, and we won't see nearly the return to cover that, so eventually they'll probably come a-calling for resources to be spent elsewhere. So I'd say the work on the Mono framework to get it compatible with 20.3+ seems unlikely.
Like I said before, ConnectWise wants to do the right thing. So what's the right thing?--
There will be a 20.2 release which addresses what we perceive as the stability/compatibility issues.
You know you can move to host SC no Windows with your existing SC license, right? (including this option for completeness ;))
If you're interested in moving to Cloud, let us know. I think there are existing deals that a bunch of customers have taken advantage of here. I'm sure if you are constructive about it, that could likely be sweetened.
Thread is at the following URL:
The community has had success with a workaround for this issue. This may work for your situation. https://tylermade.net/2017/05/04/easy-ssl-for-screenconnect-with-nginx-reverse-proxy/