Agent v2.0.1 - Unable to install agent

[JoachimVeulemans]

I am unable to install the new agent version on Windows 7. This was working in the previous release.

The error I am getting is Get "https://rmmapi.DOMAIN/api/v3/installer/": EOF

[JoachimVeulemans]

I am getting this when executing in the command line:

[wh1te909]

please run /rmm/api/env/bin/python /rmm/api/tacticalrmm/manage.py check_mesh and paste output (redact sensitive info)

[JoachimVeulemans]

I'm using a docker-compose setup

[JoachimVeulemans]

In MeshCentral I am getting this error when executing the installer:

Version:

[JoachimVeulemans]

I'm now getting "Unable to download the mesh agent from the RMM." on Windows 7 & Windows 10.

[wh1te909]

where are you running docker and can you describe your env in detail. anything custom? not able to reproduce, just tested a docker install on a vps. try adding "CookieIpCheck": false to meshcentral's config.json

[silversword411]

In trying to find out what 1005 is in Mesh parlance it looks like the websocket isn't up:
Ylianst/MeshCentral#1459

Do you have any problems/quirks with using mesh natively, or controlling a machine, downloading setup from mesh?

Just want to eliminate proxy/connection issues.

Also common troubleshooting questions:
How many agents do you have in TRMM?
Has it ever worked?
What changed between working, and not?
Is this specific to one location or everywhere?
Have you deviated from the install anywhere/proxies etc?

[silversword411]

Just tested Win7 virgin install, worked fine here.

[JoachimVeulemans]

I have found the problem. The configuration for Mesh Central in Tactical RMM was incorrect. The username contained upper case letters and the username in Mesh Central was in all lowercase. Changing the username to lowercase in Tactical RMM and generating a new .exe solved the issue.

The username hasn't changed recently and it stopped working after the update to the new agent repo. Maybe Mesh Central is now checking the case of the username?

Thanks for the help! Issue can be closed for me.

[JoachimVeulemans]

Ok the connection is not quite perfect

Everything is working in Mesh Central.

An old agent in Tactical RMM is also working, when executing remote control, the visited url is:
https://rmmmesh.DOMAIN/?login=FkhzyREDACTED=&gotonode=7C2REDACTED&viewmode=11&hide=31

When executing remote control on the new agent, the visited url is:
https://rmmmesh.DOMAIN/?login=xo$O7qREDACTED=&gotonode=&viewmode=11&hide=31

When manually filling in the node id in "gotonode". This is working (so login key is correct). Why is the node id not filled in? Problem in communication during installation?

I also upgraded to v.1.12.2. Thanks.

[JoachimVeulemans]

When looking in the database, I can see that the column "mesh_node_id" has a value and the same "format" as the other agents. So I believe that the id is saved but not correctly placed in the url when requesting remote desktop.

[JoachimVeulemans]

Ok after rebooting the docker setup, it is working now. Very strange...

Issue can be closed I guess?

[fts-tmassey]

I had a related problem (details here: amidaware/tacticalrmm#1051 )

My MeshCentral ID was "TacticalRMM". I'm also 100% certain I entered the user ID in mixed case when it was created on MeshCentral, and 100% certain it was mixed case in TRMM 0.11.3, which worked correctly against MC 1.02. However in 0.12.2, mixed case no longer works.

Changed the user name to "tacticalrmm" and running the 'check_mesh' command now works correctly. As does the agent install.

[wh1te909]

@JoachimVeulemans @fts-tmassey thank you both for figuring it out, we'll be adding some validation to the UI and also forcing the username to be lowercase before sending it to meshcentral in the next release.