Hi,
Anybody has an idea how to troubleshoot this ? I'm running MC on Debian 10, no reverse proxy.
I've noticed this since I updated to v. 0.7.52.
Thank you for your help.

@Ylianst @elpibedeoro I was seeing this this morning as well for two agents. I reinstalled the agents and this error corrected itself. I think this is related to a previous install of the agent. Not 100% sure though. In either case I was able to fix it by reinstalling the agent.
That is a weird one. I will take a look and see if there is anything I can find on this.
Thank you guys for your answers. I'll reinstall the agent and I will check.
To add an information, this morning I've got also an "InvalidRsaSignatureCount".
Is there a way to get a summary list of the impacted agents for instance ?
Agents that fail the signature check will not be allowed to be connected to the server. So, agents that successfully connect should be ok.
That's a good news if they will not be allowed to be connected to the server but how could I know the impacted agent ?
I'm trying to search in the logs but maybe I'm in the wrongs ones because I cannot find any information.
Yesterday I was lucky because a bad signature agent was showed in the console server.
About @LPJon suggestion, one PC is now ok after a reinstall thank you. The other one surprised me because the agent has been updated automatically. Yesterday I couldn't even type any command in the agent's console but now it's ok.
One thing I can do is log the IP address of the connections that are causing the bad signatures. I can't really say that agent because the process of authenticating the agent is failing, but the IP address will probably help. I will need to work on this.
That would be useful, thank you !
I added the "AgentIssues" command in upcoming MeshCentral v0.7.62. It shows the last 50 agent connections issues with time, ip:port and issue. Hopefully that will help figure things out.

Great, thank you !
Hi,
The AgentIssues command works great !
Thank you!

Hi Ylian,
Could it be possible to add the full date in the agentissues result please ?
The problem is that only time is showed.
It would be practical to have something like :
11/02/2021 10:17:07, 123.123.123.123:59708, duplicateAgent
Thank you.
Most helpful comment
I added the "AgentIssues" command in upcoming MeshCentral v0.7.62. It shows the last 50 agent connections issues with time, ip:port and issue. Hopefully that will help figure things out.