Your comments

Is this bug fixed? I can't find any submitted ticket about it.

@Jake, first of all, thank you for your reply, it's the first time we hear honest and detailed explanation from CW and I appreciate it.

As many of us wrote here, announce the new version of CWC based on .NET Core and don't focus on incompatible extensions. Yes I know, the problem is yours extensions which are adding connection between products in CW family. But I guess, nobody with CWC on Linux platform is using them. Because all other CW products are not compatible with Linux.

You have to solve the instability problem at first and then add a new/old features, as extensions. Everybody knows that extensions are not parts of product core, many of them are not created by CW and can by disabled anytime.

It's frustrating that you have courage to offer us the cloud version of CWC again and again, even that you know that there are CW clients who have to use the on-premise version. That's the reason why we choose the CWC/ScreenConnect years ago. 
A few months ago (maybe a year) I communicated with your colleague about CW Manage and other products and about using CW products on Windows platform. You sent me so messed up info about Microsoft licensing that many of your clients - MSPs are using CW products against Microsoft agreement, I suppose.

Please, consult the Microsoft licensing with some MS licensing specialist and offer your product to MSPs after you clarify it internally.

We are using ConnectWise Control on Linux for a years and I understand your disappointment. The text below is NOT defense of ConnectWise at all.

But I don't understand anyone who want to run a service as ConnectWise Control on on-premise Windows Server. I hope that you looked at the Microsoft license before you made a choice, Product Terms especially, because you have assign assign CAL license to every device which will be connected with ConnectWise Control, or buy External Connector to allow unlimited external devices and users. And be aware, you have to assign CAL license to every internal user or device as well, even though you're using External Connector.

So we are running ConnectWise Control on Linux with Apache proxy for more than a year. OS (Ubuntu) and Apache (and all other packages) are upgrading automatically, without any problems at all. Yes, we have to do some research at the start and invested a few hours to done it right, but it's same with all Linux problems. And now a few of us here created a easy manual and script to do it in a few minutes.

I hope that the ConnectWise do not "win" this situation by forcing every client to Windows, one by one, like you :(

Hello Eric, it's Ubuntu 14.04. The bug it not permanent and it's seems as it's working for a little time window after CWC service is restarted. Later when I click to my account icon and Report Manager nothing happens. I found the error by browser debug console.

How can I enable any debug log in CWC to get more info?

I closed it soon, problem is still exists. It's seems like Report Manager is working a few minutes after restart and bug appears a hours of running. (I tested it again after >10 hours.)

Error is same as before.

Report Manager is fixed/working again after upgrade ConnectWise Control to 19.4 (19.4.25699.7240).

Thank you for resolving this issue.

Issue is not fixed in ConnectWise Control 19.3.25169.7170 with Report Manager 1.8.3. Server reports

Connection string must be set: SessionDatabase

Description: HTTP 500.Error processing request.

Details: Non-web exception. Exception origin (name of application or object): System.ServiceModel.
Exception stack trace:
at System.ServiceModel.MonoInternal.ClientRuntimeChannel.Request (System.ServiceModel.Description.OperationDescription od, System.Object[] parameters) [0x00000] in :0
at System.ServiceModel.MonoInternal.ClientRuntimeChannel.DoProcess (System.Reflection.MethodBase method, System.String operationName, System.Object[] parameters) [0x00000] in :0
at System.ServiceModel.MonoInternal.ClientRuntimeChannel.Process (System.Reflection.MethodBase method, System.String operationName, System.Object[] parameters) [0x00000] in :0

It seems that ConnectWise will end Linux support soon, regarding the ending support for macOS due to problematic Mono branch. They are recommend transitioning from macOS to Windows server or ConnectWise Control Cloud only and do not recommend Linux literally, because "many of the same Mono issues exist on Linux Server".

You can read the article here:

I don't beleive that ConnectWise operates ConnectWise Control Cloud on Windows platform and it seems like they are force us to move to the cloud, because it's much more expensive = profitable for them. And I don't want to imagine what we would have to do after migration to cloud against to GDPR.

It's sad, unbelievable, unprofessional and ConnectWise create the worst reputation of all our partners.

Hello, do you have any news about this bug? Do you plan to fix it in next release?