Simon Smith

`if (Directory.Exists(modulesdir.FullName) == false) { displayMessage("Can't find node_modules folder, installation failed.", 2); workerThread = null; return; }` are you customing where meshcentral gets installed at all? all it does is...

the is something wrong with your setup/internet **attempt 1 failed with SELF_SIGNED_CERT_IN_CHAIN** **verbose stack FetchError: request to https://registry.npmjs.org/meshcentral failed, reason: self-signed certificate in certificate chain** try visiting the url `https://registry.npmjs.org/meshcentral`...

closing this as stale, plus issue was due to customers firewall/router/proxy

@inzi the post you are tagging into this issue shows that the fix was only merged and released in 1.1.29 but you say in the issue you are running 1.1.27...

@n1smithy have you updated to the latest version 1.1.32? can you share ur config.json? (hide secrets)

@n1smithy you can check in the web ui under the 'My Server' tab, just click 'check server version', but chances are if you have updated the docker image TODAY AND...

@Br0kenSilos in theory our docker image `ghcr.io/ylianst/meshcentral` is the same as `typhonragewind/meshcentral:latest` However, a lot of people seem to have problems with `typhonragewind/meshcentral:latest` This is why we always tell people...

can you run it with the `authlog` debug at all for me and replicate ur issue in various ways? `node node_modules/meshcentral --debug authlog` the logs from the console will show...

in theory 1. if you set `authLog: "/mypath/mylog.log"` under `settings` in your config.json, it should generate an authlog which u can check for auth issues 3. if you set `log:...

is this still an issue?