starred/tacticalrmm

Fork 0

mirror of https://github.com/amidaware/tacticalrmm.git synced 2026-04-26 15:05:57 +03:00

[GH-ISSUE #639] Certain Agents unable to contact MeshCentral #2354

New issue

Closed

opened 2026-03-14 03:40:58 +03:00 by kerem · 13 comments

kerem commented

2026-03-14 03:40:58 +03:00

Owner

Originally created by @FrinkMan on GitHub (Jul 16, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/639

Server Info (please complete the following information):

OS: Ubuntu 20.04
Browser: Microsoft Edge
RMM Version (as shown in top left of web UI): v0.7.2

Installation Method:

Standard
Docker

Agent Info (please complete the following information):

Agent version (as shown in the 'Summary' tab of the agent from web UI): v1.5.9
Agent OS: Windows 10 Enterprise LTSC 2019, 64 bit v1809 (build 17763.2029)

Describe the bug
Installed the agent, and it populated in TacticalRMM fine, although nothing appears in MeshCentral. MeshAgent is installed but unable to contact the server. Stopping the Mesh Agent service and running it manually from the .exe in Program Files shows it's sticking at connecting to the server

Expected behavior
Start MeshAgent, receive connecting to, connected, etc. Can confirm that most other computers I've installed on work fine, so far only two have had this issue.

Screenshots
No screenshots really necessary imo, the agent isn't registered in MeshCentral, and command line just shows "Connecting to: wss://mesh.myserver.com:443/agent.ashx

Originally created by @FrinkMan on GitHub (Jul 16, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/639 **Server Info (please complete the following information):** - OS: Ubuntu 20.04 - Browser: Microsoft Edge - RMM Version (as shown in top left of web UI): v0.7.2 **Installation Method:** - [x] Standard - [ ] Docker **Agent Info (please complete the following information):** - Agent version (as shown in the 'Summary' tab of the agent from web UI): v1.5.9 - Agent OS: Windows 10 Enterprise LTSC 2019, 64 bit v1809 (build 17763.2029) **Describe the bug** Installed the agent, and it populated in TacticalRMM fine, although nothing appears in MeshCentral. MeshAgent is installed but unable to contact the server. Stopping the Mesh Agent service and running it manually from the .exe in Program Files shows it's sticking at connecting to the server **Expected behavior** Start MeshAgent, receive connecting to, connected, etc. Can confirm that most other computers I've installed on work fine, so far only two have had this issue. **Screenshots** No screenshots really necessary imo, the agent isn't registered in MeshCentral, and command line just shows "Connecting to: wss://mesh.myserver.com:443/agent.ashx

kerem closed this issue

2026-03-14 03:41:03 +03:00

kerem commented

2026-03-14 03:41:09 +03:00

Author

Owner

@wh1te909 commented on GitHub (Jul 16, 2021):

Hi mesh is a separate product please check https://github.com/Ylianst/MeshCentral for docs and see if can run the mesh agent in debug mode to see where it's getting stuck

your title says certain agents cant connect, does that mean some are working? if so maybe on those machines websocket traffic being blocked? edit: nvm just saw you said it's only having issues on 2 agents so try and see whats different about those 2 agents why traffic is being blocked

@wh1te909 commented on GitHub (Jul 16, 2021): Hi mesh is a separate product please check https://github.com/Ylianst/MeshCentral for docs and see if can run the mesh agent in debug mode to see where it's getting stuck your title says certain agents cant connect, does that mean some are working? if so maybe on those machines websocket traffic being blocked? edit: nvm just saw you said it's only having issues on 2 agents so try and see whats different about those 2 agents why traffic is being blocked

kerem commented

2026-03-14 03:41:14 +03:00

Author

Owner

@FrinkMan commented on GitHub (Jul 16, 2021):

I'm assuming it's something with websocket traffic, but I haven't traced down anything in event logs yet. Will do some digging and let you know if I figure anything out

@FrinkMan commented on GitHub (Jul 16, 2021): I'm assuming it's something with websocket traffic, but I haven't traced down anything in event logs yet. Will do some digging and let you know if I figure anything out

kerem commented

2026-03-14 03:41:19 +03:00

Author

Owner

@FrinkMan commented on GitHub (Jul 16, 2021):

Not sure if you want me to start a new issue for this or not, but I'm also trying to deploy to some agents and I'm getting this error when I run the script using ConnectWise:

Waiting for network
C:\WINDOWS\TEMP\ScreenConnect\21.8.3663.7830\ea634c0f-e424-4e28-8765-2c9285d3a4e7run.ps1 : The remote server returned 
an error: (403) Forbidden. 
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,ea634c0f-e424-4e28-8765-2c9285d3a4e7ru 
   n.ps1
 
Remove-Item : Cannot find path 'C:\WINDOWS\TEMP\winagent-v1.5.9.exe' because it does not exist.
At C:\WINDOWS\TEMP\ScreenConnect\21.8.3663.7830\ea634c0f-e424-4e28-8765-2c9285d3a4e7run.ps1:76 char:13
+             Remove-Item -Path $OutPath\$output
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\WINDOWS\TEMP\winagent-v1.5.9.exe:String) [Remove-Item], ItemNotFound 
   Exception
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.RemoveItemCommand

Could this also be a proxy issue? I can download the file fine if I browse to the URL using a browser such as Chrome

@FrinkMan commented on GitHub (Jul 16, 2021): Not sure if you want me to start a new issue for this or not, but I'm also trying to deploy to some agents and I'm getting this error when I run the script using ConnectWise: ``` Waiting for network C:\WINDOWS\TEMP\ScreenConnect\21.8.3663.7830\ea634c0f-e424-4e28-8765-2c9285d3a4e7run.ps1 : The remote server returned an error: (403) Forbidden. + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,ea634c0f-e424-4e28-8765-2c9285d3a4e7ru n.ps1 Remove-Item : Cannot find path 'C:\WINDOWS\TEMP\winagent-v1.5.9.exe' because it does not exist. At C:\WINDOWS\TEMP\ScreenConnect\21.8.3663.7830\ea634c0f-e424-4e28-8765-2c9285d3a4e7run.ps1:76 char:13 + Remove-Item -Path $OutPath\$output + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (C:\WINDOWS\TEMP\winagent-v1.5.9.exe:String) [Remove-Item], ItemNotFound Exception + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.RemoveItemCommand ``` Could this also be a proxy issue? I can download the file fine if I browse to the URL using a browser such as Chrome

kerem commented

2026-03-14 03:41:25 +03:00

Author

Owner

@dinger1986 commented on GitHub (Jul 16, 2021):

I'd suggest getting on discord and hopefully others can help there

@dinger1986 commented on GitHub (Jul 16, 2021): I'd suggest getting on discord and hopefully others can help there

kerem commented

2026-03-14 03:41:30 +03:00

Author

Owner

@FrinkMan commented on GitHub (Jul 16, 2021):

@FrinkMan commented on GitHub (Jul 16, 2021): Ok

kerem commented

2026-03-14 03:41:35 +03:00

Author

Owner

@silversword411 commented on GitHub (Jul 16, 2021):

Sounds like AV issue

@silversword411 commented on GitHub (Jul 16, 2021): Sounds like AV issue

kerem commented

2026-03-14 03:41:40 +03:00

Author

Owner

@FrinkMan commented on GitHub (Jul 18, 2021):

I don't think it's antivirus either because I run SentinelOne, and it's installed on all the other machines in the corporation with SentinelOne just fine

@FrinkMan commented on GitHub (Jul 18, 2021): I don't think it's antivirus either because I run SentinelOne, and it's installed on all the other machines in the corporation with SentinelOne just fine

kerem commented

2026-03-14 03:41:45 +03:00

Author

Owner

@dinger1986 commented on GitHub (Jul 18, 2021):

Can you telnet from those agents to your mesh server? Use putty if you don't have telnet client installed.

Have you added exclusions to your antivirus? We have seen it for some customers where av is fine on some PCs and on others can't even install.

@dinger1986 commented on GitHub (Jul 18, 2021): Can you telnet from those agents to your mesh server? Use putty if you don't have telnet client installed. Have you added exclusions to your antivirus? We have seen it for some customers where av is fine on some PCs and on others can't even install.

kerem commented

2026-03-14 03:41:50 +03:00

Author

Owner

@silversword411 commented on GitHub (Jul 18, 2021):

You're using the screenconnect script from docs to deploy TRMM?

That is a deployment url?

The deployment url works from the browser on the machine? (Not an expired link?)

If it downloads fine in the browser, you're getting a forbidden error.

Uninstall SentinelOne and retest. If it works with no av, then you have your answer.

@silversword411 commented on GitHub (Jul 18, 2021): You're using the screenconnect script from docs to deploy TRMM? That is a deployment url? The deployment url works from the browser on the machine? (Not an expired link?) If it downloads fine in the browser, you're getting a forbidden error. Uninstall SentinelOne and retest. If it works with no av, then you have your answer.

kerem commented

2026-03-14 03:41:55 +03:00

Author

Owner

@dinger1986 commented on GitHub (Jul 18, 2021):

I strongly suggest if you require more support then get it on discord where a number of users can help.

I am going to close this now.

@dinger1986 commented on GitHub (Jul 18, 2021): I strongly suggest if you require more support then get it on discord where a number of users can help. I am going to close this now.

kerem commented

2026-03-14 03:42:00 +03:00

Author

Owner

@FrinkMan commented on GitHub (Jul 19, 2021):

Was able to get this resolved, it turns out something specific to the proxy on those machines was performing SSL Inspection, and so the hashes for the certificates weren't matching serverside/clientside. Disabling that temporarily fixed it, and I'm working with the proxy provider now to get an exclusion added. Thank-you for your help!

@FrinkMan commented on GitHub (Jul 19, 2021): Was able to get this resolved, it turns out something specific to the proxy on those machines was performing SSL Inspection, and so the hashes for the certificates weren't matching serverside/clientside. Disabling that temporarily fixed it, and I'm working with the proxy provider now to get an exclusion added. Thank-you for your help!

kerem commented

2026-03-14 03:42:05 +03:00

Author

Owner

@silversword411 commented on GitHub (Jul 19, 2021):

What proxy do you have client side?

@silversword411 commented on GitHub (Jul 19, 2021): What proxy do you have client side?

kerem commented

2026-03-14 03:42:10 +03:00

Author

Owner

@FrinkMan commented on GitHub (Jul 22, 2021):