Agent connected with bad signature.

[ghost]

Hi,

On a daily basis the MeshCentral status page (sudo systemctl status meshcentral.service) reports the following problem/error:
Agent connected with bad signature, holding connection (undefined).

I am not sure what this error actually means and which agent is causing this?
My question is how do I troubleshoot the agent problems/errors from the users that are connected to the meshcentral server in general?
How would I troubleshoot the problem I am reporting?

MeshCentral server installation (currently using version 1.1.38:
Ubuntu 22.04
Database MongoDB: ver. 8.0.4

All of the agents connecting to meshcentral from either Windows 10 or 11 PCs, meshagents (ver. 9th Dec 2022), all on 64bit apart from one.

Best Regards,
Lutz Lorenz

[PrplHaz4]

This means that the agent is trying to connect with a certificate that's different from what the server pulled down when it started (or what it was configured with). This often happens if you're using a proxy or split dns.

[si458]

You haven't followed the bug report template correctly
We need to see a copy of your config.json

[si458]

you need to set certurl to the URL you are using to access meshcentral (e.g.https://my.domain.com)

also sessionkey should be uncommented and set as well to a completely random value thats kept secret
(this helps with logout and logs in the web ui between restarts)

also you say you use a reverse proxy, what reverse proxy is it? also whats its config look like?