Simon Smith

Something isn't right with ur setup? Why is it code-signing the applications every time u start meshcentral? It should only do that once and never again. What's the layout of...

Try rerunning `amtconfig` in the console tab of one of the devices and see what it outputs (might take a min to finish with logs) Then shut the device down...

The problem is the code-siging only happens if the dns name changes, which in turn regenerates certificates, like the amt certificate, which in turn would explain WHY they can't connect...

Try also running `node node_modules/meshcentral --debug` This will output ALL debug logs and might give more of an insight! Note the will be loads of logs too

The full log above, did you switch the computers on? Where they already switched on? Did they show in the Web panel as online but offline?

~~Oh wow, any hardware I can use for testing is appreciated! Do email me! Check my github page~~ sorry just realised u said states, dont worry about it, im UK...

these are the changes we did between 1.1.20 and 1.1.24 - https://github.com/Ylianst/MeshCentral/compare/1.1.20...1.1.24 we changed 0% to do with AMT so im totally confused? altho my test machine which uses AMT...

are your AMT machines local to your meshcentral server? because in theory as ur using a reverse proxy they should be connecting over CIRA as they arent local to meshcentral...

@vedran-dobos can u explain ur setup at all? Nodejs version? Server os? What amt version? Reverse proxy infront of meshcentral or direct to meshcentral? I'm struggling to replicate the issue...

@vedran-dobos, are u also proxing the amt port 4433 through ur haproxy? Or is the 4433 port directly connected to meshcentral? In theory when u visit https://mymeshcentral.com:4433 u should get...