One of our clients has it so that when using Connectwise control with guest video disabled they can't use the snip tool. If they turn guest video back on it shows up like they have two cursors.

Trying to configure the OIDC login provider with AzureAD. Login is successful (i'm logged in) but can't do anything as it hasn't picked up my permissions:

The requested resource requires more permissions than provided by your existing authentication. Please login to continue.

I suspect this is because ScreenConnect is not reading the roles from the ID token correctly using the "'UserInfoRoleNamesPath" key. I can validate this by specifying my role 'Administrator' in the "ExtraRoleNames" field which then logs me in with fine. The documentation indicates the field should have 'JSON path, slash-separated ("/"), to a user's roles", but this isn't very helpful to understand what value you want entered here. I've tried the following values but none of them work:

• roles
• $.roles
• $['roles']

Here is the JWT 'ID Token' (anonymised) from Azure that was obtained using the same Client ID, Client Secret & Scope as ScreenConnect, which clearly shows my role.

{
  "aud": "fb6c9e00-e011-45a5-b47b-84a9493c0bb1",
  "iss": "https://login.microsoftonline.com/9022722a-13a8-4a53-a9ba-4974a96be07d/v2.0",
  "iat": 1591317833,
  "nbf": 1591317833,
  "exp": 1591321733,
  "email": "firstname.lastname@domain.com",
  "name": "FirstName LastName",
  "oid": "932b3f5a-575b-4716-8088-3198ea5b5001",
  "preferred_username": "FirstName.Berthoud@vista.co",
  "roles": [
    "Administrator"
  ],
  "sub": "SKDJhfs9d-ASDOFjn09dsf-SDnvcfisduvc9h3nfcsd",
  "tid": "861b4c2d-dc36-4e80-a700-9fb413388daa",
  "uti": "aDSBJHKd8sfsdf",
  "ver": "2.0"
}

Self-hosted version 20.13.1633.7620

After enabling and testing SAML w/ Azure AD, I disabled internal authentication. Once I did that I was completely locked out of the server, and clicking the Login button on the main page resulted in a 404 error. I tried resetting the installation and configuring a new default Administrator account, but doing so did not re-enable internal authentication as expected so I still couldn't log in.

Support showed me how to edit the web.config file to re-enable internal authentication in order to log in with the default administrator account. Search web.config for "user.xml" and change the "enabled" value to true. 

After re-enabling internal authentication, Azure SSO started working as well. It appears that disabling internal authentication prevents SSO from working, so for now I have to keep internal authentication enabled even though we want to use SSO exclusively.

Ubuntu 20.04 is still non-functional with both the latest stable and debug versions on the website.

The is a similar bug that was marked fix that should not have been- https://control.product.connectwise.com/communities/6/topics/3030-ubuntu-2004-lts-screenconnect_201270367360-not-working

You can see in the 4nd to last comment it is stated that the libc issue is still present with the debug version.  So far the only workaround is to manually change things in the library directory which is not a good long term solution (and potentially dangerous to other applications running on the system).

I get the following error repeatedly in the logs:

Event (2020/09/17 08:47:20.943 -05:00, ScreenConnect Session Manager, Information): Starting service...
Event (2020/09/17 08:47:21.440 -05:00, ScreenConnect Session Manager, Information): Successfully started service.
Event (2020/09/17 08:47:21.440 -05:00, ScreenConnect Relay, Information): Starting service...
Event (2020/09/17 08:47:21.691 -05:00, ScreenConnect Relay, Information): Successfully started service.
Event (2020/09/17 08:47:21.691 -05:00, ScreenConnect Web Server, Information): Starting service...
Event (2020/09/17 08:47:31.275 -05:00, ScreenConnect Web Server, Information): Successfully started service.

Unhandled Exception:
System.TypeInitializationException: The type initializer for 'libc' threw an exception. ---> System.InvalidOperationException: Unable to load native library from 'libc.so'
at ScreenConnect.DiskNativeLibrary..ctor (System.String libraryPath) [0x00039] in :0
at ScreenConnect.MonoToolkit+MonoDiskNativeLibrary..ctor (System.String libraryPath) [0x00000] in <13284ac991af480facb74ab3873c80af>:0
at ScreenConnect.MonoToolkit.LoadNativeLibraryFromDisk (System.String libraryPath) [0x00001] in <13284ac991af480facb74ab3873c80af>:0
at ScreenConnect.NativeLibrary.LoadLibrary (System.String libraryName, System.Type lookInAssemblyWithType) [0x00041] in :0
at ScreenConnect.NativeLibrary.LoadLibrary (System.Type type, System.Type lookInAssemblyWithType) [0x00008] in :0
at ScreenConnect.NativeLibrary.LoadProxy (System.Type type, System.Type lookInAssemblyWithType) [0x00010] in :0
at ScreenConnect.NativeLibrary.LoadProxy[T] (System.Type lookInAssemblyWithType) [0x00001] in :0
at ScreenConnect.MonoNative+libc..cctor () [0x0000a] in <13284ac991af480facb74ab3873c80af>:0
--- End of inner exception stack trace ---
at ScreenConnect.Program.Main (System.String[] args) [0x004a1] in :0
[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for 'libc' threw an exception. ---> System.InvalidOperationException: Unable to load native library from 'libc.so'
at ScreenConnect.DiskNativeLibrary..ctor (System.String libraryPath) [0x00039] in :0
at ScreenConnect.MonoToolkit+MonoDiskNativeLibrary..ctor (System.String libraryPath) [0x00000] in <13284ac991af480facb74ab3873c80af>:0
at ScreenConnect.MonoToolkit.LoadNativeLibraryFromDisk (System.String libraryPath) [0x00001] in <13284ac991af480facb74ab3873c80af>:0
at ScreenConnect.NativeLibrary.LoadLibrary (System.String libraryName, System.Type lookInAssemblyWithType) [0x00041] in :0
at ScreenConnect.NativeLibrary.LoadLibrary (System.Type type, System.Type lookInAssemblyWithType) [0x00008] in :0
at ScreenConnect.NativeLibrary.LoadProxy (System.Type type, System.Type lookInAssemblyWithType) [0x00010] in :0
at ScreenConnect.NativeLibrary.LoadProxy[T] (System.Type lookInAssemblyWithType) [0x00001] in :0
at ScreenConnect.MonoNative+libc..cctor () [0x0000a] in <13284ac991af480facb74ab3873c80af>:0
--- End of inner exception stack trace ---
at ScreenConnect.Program.Main (System.String[] args) [0x004a1] in :0

As mentioned in the Output Stream entry for this version, the bug "Router service on-prem doesn't forward traffic" was indeed fixed.

But, in addition to the issue I've detailed here which requires you to edit the web.config file before the router service can start working again, I've also noticed that all the ScreenConnect services (Web Server, Relay, Session Manager and Router) terminate unexpectedly after a while when a router service is configured.

Also, a look at the Event Viewer shows that the Router service is always the first to terminate, with the other services following soon thereafter.

I did some testing and I've confirmed that when the Router service is stopped, the remaining three services run just fine. So it has to be the Router service that is the source of whatever bug is causing all services to fail.

Due to this bug, my server crashes at least once a day. Until it's fixed, the Router service is still pretty much unusable.

When I try to build and download installer for access in the windows app, it does nothing and then the app hangs. Send link and Copy URL seem to work ok, but download does not. Clicking the X or Done does nothing. Have to hit escape, but the app is still unresponsive and has to be closed.

Version 20.11.1385.7587 Self hosted.

I have been getting this and similar errors popping up randomly while doing anything, refresh a client, click on a group, click on a client, etc...

This has been an ongoing issue over several versions.

Like the title says. Blanking the guest monitor, blanks my monitor as well.

In this case for example its the guest is running W10 with a GeForce GT 740 and 3 monitors.

Anyone else having issues with multi-monitor setups?

After upgrade of phone to Android 11, whenever I connect to client machines the screen flickers constantly not allowing control of device.

Computer offline in Console after it wakes up from hibernation.  The only fix is for end user to restart the computer or restart the ScreenConnect service.  I am on 20.11 but this problem has been happening for a while, before 20.11 i know that.