Welcome to the ConnectWise Control Bug Report Portal

If you do not have an account, click "Sign in/ Sign up" to get started.


Tips

  • Search for an existing bug report before adding your own. This helps us prevent duplicate entries and improve bug tracking.
  • If you find a matching bug report, give it a thumbs up and throw in a comment with more details about the problem.
  • If you can't find a request for an item you need, create your own bug report. Provide as many details as you can, especially:
    • Software version of the server, host client, and guest client
    • Operating systems affected
    • Any error messages
    • Screenshots

Rules

  • No spam, advertising, or self-promotion.
  • No offensive posts, links, or images.
  • Only one request per post.
  • Administrators have the ability to moderate the forums, including editing, deleting, and moving posts. Posts may be deleted for any reason, with or without notification.

Thank you for sharing your thoughts with us!


Recently updated topics 704

0
Under review

OpenID Connect - UserInfoRoleNamesPath format?

CBVista 4 months ago updated by RYC KLC 1 day ago 3

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"
}

0
Under review

sc-7bb06d585deac872 link

Mary Craft 2 days ago 0

When trying to "Join" to the remote PC, this message popped up - first time ever!  Also, my ConnectWise Control version is 20.10.957.7556

0
Under review

Remote Printing Brother MFC-L5850DW

Marty Marks 4 weeks ago updated by Technicalguy 2 days ago 1

Printing from a remote machine to a local Brother MFC-L5850DW immediately throws an error on the local machine and leaves the printer stuck in an error state locally.  The printer itself is fine and continues to print from every other local computer, and no errors are thrown on the remote computer.

+17
Under review

URL Launch from FireFox 66.0.3 Not Working

phils 1 year ago updated by dakruhm 3 days ago 28

When launching ConnectWise Automate Web or Control web consoles, "Control" button doesn't launch the installed application and instead attempts to force re-download of the app.

0
Waiting for information

Trigger E-mails not being sent still in 20.10.957.7556

Steven Woodhouse 5 days ago updated 3 days ago 2

Trigger e-mails work for a few hours before stopping again.  SMTP Test button works ok.  Using the latest SMTP Advanced Settings plugin.

Reverted to 20.7 for the time being which works correctly.

+14
Under review

Control launches off screen

Dan Belam 10 months ago updated by Rishikesh Gajul (Product Manager) 4 days ago 11

I'm a laptop user, and often use a second monitor. Control launches onto the second monitor fine. When I unplug my second monitor, and just use laptop screen, some sessions launch beyond the display size of my laptop, ie where a second screen would be, and you cannot get to the window to move back onto the single laptop screen.

Answer

Hi Cee, thanks for contacting us. Kindly tell us what version are you on?

Meanwhile, you can fix the issue by deleting the user config c:\ProgramData\ScreenConnect Client (xxx)\user.config

0
Under review

enter @ on macbook

rk 2 weeks ago updated 5 days ago 7

I can't enter "@" on macbook pro over Screenconnect session
After enter "@" Screenconnect session will be closed

Model: Macbook Pro
OS: Catalina 10.15.6

Thanks in advance.

0
Under review

Undocumented Changes in Control Product - Bug Report

earl.kelly 1 week ago 0

There are some undocumented changes in the latest versions of your control product that I think you need to be aware of. I’ve written about it previously and no one really seemed to know what I’m talking about. We just updated our On-Prem control and I was able to get a clear picture of exactly what is happening. In the attached I’ve shown you the picture of the standard themes that come with Connectwise control. These are not custom themes…but you will see there is a defiant color change from version 19.x and prior to version 20.X. I’ve also documented this with support.

This need to be corrected back the more muted colors in version 19.x and prior. I’ve combed thru the CSS to see if there is an actual color change in the CSS but I am unable to locate any differences. Someone however made the PNG files I downloaded and should have noticed this change.

Most people may not find this a big deal…but the new green and the blue are so neon that they trigger migraines when viewed.

Please let me know if you have any questions.

0
Under review

Ubuntu 20.04 does not work with Screen Connect 20.1.27036.7360 or 20.2.29488.7519_Debug

Chris Feist 1 week ago updated by Rishikesh Gajul (Product Manager) 1 week ago 1

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

Answer

Hi Chris,

Thank you for contacting us. Please try to symlinking to resolve this error. In testing, we found it was possible to work around this error by symlinking to the necessary files in /lib/x86_64-linux-gnu:

ln -s libc-2.31.so libc.so
ln -s libdl-2-31.so libdl.so
ln -s libz.so.1.2.11 libz.so
After that's done, restart the screenconnect service, and you should be up and running.