Not sure when this started. Mesh Router related.
Mesh: 0.5.49
All the "RDP", "HTTP", "SSH" quick buttons are grayed out. However, you can do a map manually with no issue.


@Ylianst - possibly is related to last post in #1309 ?!?!?!
@MordyT - I have the same issue, not sure what your setup is.
@vitko-bg Maybe. I have (in each domain) a user in the managealldevicegroups that is local to mesh and in the primary domain I have both a local user and a SSO user there.
No users (admins, local, SSO, etc) have the quicklinks working.
The buttons are normally grayed out when your account does not have "Remote Control" rights to the devices. That is the permission required to perform traffic forwarding. If you have some detail as to how the permissions are granted (thru a user group?) I will debug this.
The account is a member of a user group. That user group is a full administrator on a mesh device group.
If I manually add a specific user to a specific device as Remote Control, the button lights up right away.
Excellent, I see the same problem now. Working on it.
Ok, fixed it. Will be in the next version of MeshCentral, however since the problem is with the MeshCentral Router only, you can get the latest version here.
@Ylianst your link to meschcentral router is incorrect, this one is working http://info.meshcentral.com/downloads/MeshCentral2/MeshCentralRouter.exe
Thanks @peteranv, fixed my link.
New router does fix the buttons grayed out. However, I'm facing an issue on some PCs (even with old router) where the router can launch normally, but when launched from the webapp we get this error. Only on some machines - is there a dependency missing on those machines?
````
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
*** Exception Text ***
System.UriFormatException: Invalid URI: The hostname could not be parsed.
at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
at MeshCentralRouter.MainForm.nextButton1_Click(Object sender, EventArgs e)
at MeshCentralRouter.MainForm.MainForm_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
*** Loaded Assemblies ***
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B
MeshCentralRouter
Assembly Version: 1.0.7458.922
Win32 Version: 1.0.7458.922
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4150.0 built by: NET48REL1LAST_C
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
*** JIT Debugging ***
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
````
This URL seems somewhat related although for another platform?
https://support.microsoft.com/en-us/help/976213/fix-error-message-when-you-run-a-managed-application-that-uses-a-webbr
Thanks for the report. I am pretty sure I found the problem and fixed it, you can try the latest MeshCentral Router here. Let me know if it works. The updated MeshCentral Router will be in the next version of MeshCentral v0.5.51 when it comes out.
@Ylianst
Progress. Login works, but clicking the RDP icon crashes it with a similar message (Invalid URI: The hostname could not be parsed).
Strange how it works well on some of our PCs and others have this error.
One more version of MeshCentral Router here. This one should fix the Invalid URI exception, let me know if it works.
Tried the latest version, I'm still getting this when clicking the RDP button:

I have another user who reported getting this when trying any RDP from router:

HA!! Ok, I see the problem now. Thanks for posting the details, will work on this.
I just did a quick, end of day fix... new MeshCentral Router is here. Let me know if it works now.
@Ylianst My team is telling me that the newest version has fixed all reported issues. I'll close this for now and let you know if the issue returns.
THANK YOU!