MeshCentral: My RASPI Meshcentral2 no longer does updates and my Letsencrypt certificate expires in 11 days
Hello My RASPI Meshcentral2 no longer does updates and my Letsencrypt certificate expires in 11 days, Is this due to the update of the MC since Letsencrypt needs the ACME 2? is my productive remote maintenance server. It worked the last few years and now such a stress. My System : Raspberry 4/ 8 GB / SSD am USB Debian 12 RASPIAN / Node Version 22.11.0 / NPM Version 10.9.0 7 / MariaDB Version 10.11.3 / PHP 8.2.7 System is up-to-date, I don’t know what to do right now I hope someone has a solution
359 / 5.000 Here is the solution that I found myself and it works.
Step 1 systemctl stop meshcentral
Step 2: Rename two directories to “node_modules” .uglify-js-mem12Ene to .uglify-js-mem12Ene.old uglify-js to uglify-js.old
Step 3 npm install meshcentral@1.1.35
Step 4 npm audit fix --force
Step 5 systemctl start meshcentral Feedback geben Übersetzungsergebnisse verfügbar
Let’s Debug Result: OK
Hier noch meine config.json
{
"$schema": "http://info.meshcentral.com/downloads/meshcentral-config-schema.json",
"__comment1__": "This is a simple configuration file, all values and sections that start with underscore (_) are ignored. Edit a section and remove the _ in front of the name. Refer to the user's guide for details.",
"__comment2__": "See node_modules/meshcentral/sample-config-advanced.json for a more advanced example.",
"settings": {
"cert": "XXXXXXXX.de",
"WANonly": true,
"_LANonly": true,
"_FastCert": true,
"_sessionKey": "KXKXKXKXKXKXKXKXKKXKXKXKXKKXKXKKX",
"port": 443,
"aliasPort": 443,
"redirPort": 80,
"redirAliasPort": 80,
"mariadb" : { "host": "127.0.0.1", "user": "XXXXXXUSERXXXXX", "password": "SAGICHNICHT", "secure" : true },
"compression": true,
"_wscompression": true,
"agentwscompression": true,
"allowframing": true,
"clickonce": true,
"webrtc": true,
"selfupdate": true
},
"domains": {
"": {
"title": "XXXXXXXXXX.de",
"_certUrl": "https://XXXXXXXXXX.de:443/",
"agentFileInfo": {
"icon": "MeshServer1.ico"
},
"assistantCustomization": {
"title": "XXXXXXXXXX",
"image": "XXX_msc.png",
"fileName": "XXXXXXXXXX_Assistent",
"allowHighQualityDesktop": false
},
"consentMessages": {
"Title": "XXXXXXXXXX - Service TEL : 0000000000000",
"Desktop": "{0} ({1}) hat einen Remote-Desktop-Zugriff angefordert. Die Fernwartung von XXXXXXXXXXr ist kostenpflichtig und wird mit 60 Euro a Stunde berechnet. Zugriff gewähren? ",
"Terminal": "{0} ({1}) hat einen Remote-Terminal-Zugriff angfordert. Die Fernwartung von XXXXXXXXXX Service ist kostenpflichtig und wird mit 52 Euro a Stunde berechnet Zugriff gewähren? ",
"Files": "{0} ({1}) hat einen Remote-Dateizugriff angefordert. Die von XXXXXXXXXX ist kostenpflichtig und wird mit 60 Euro a Stunde berechnet. Zugriff gewähren?"
},
"notificationMessages": {
"title": "Nachricht",
"desktop": "{0} Eine Remote Desktop Session wurde gestartet.",
"terminal": "{0} Eine Terminal Session wurde gestartet.",
"files": "{0} Eine Datenübertragung ist Aktiv."
},
"agentCustomization": {
"displayName": "XXXXXXXXXX",
"description": "Die Fernwartung von XXXXXXXXXX ist kostenpflichtig und wird mit 60 Euro a Stunde berechnet - Service Tel: 000000000000",
"companyName": "XXXXXXXXXX Service",
"serviceName": "XXXXXXXXXX.de",
"image": "XXXX_msc.png",
"installText": "Die Fernwartung von XXXXXXXXXX ist kostenpflichtig und wird mit 60 Euro a Stunde berechnet - Service Tel : 000000000000",
"fileName": "Fernwartung_Agent",
"foregroundColor": "255,0,0",
"backgroundColor": "255,255,0"
},
"_title2": "Server",
"_minify": true,
"siteStyle": 2,
"titlepicture": "XXXX.png",
"loginPicture": "login.png",
"meshMessengerTitle": "XXXX-Chat",
"MeshMessengerPicture": "messenger.png",
"footer": "XXXXXXXXXXX",
"newAccounts": false,
"userNameIsEmail": false
}
},
"letsencrypt": {
"__comment__": "Requires NodeJS 8.x or better, Go to https://letsdebug.net/ first before trying Let's Encrypt.",
"email": "XXXXXXXX@mail.com",
"names": "XXXXXXXXXX.de",
"production": true
}
}
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15
OK, thanks, the problem was solved. I still had an Apache server running on port 80 in the background. I think it crept in when I upgraded from Debian11 to 12, there should actually be an NGINX running on port 8181… The permissions in my router made me look there. Now the certificate has been renewed, thanks so far.
But the update from 1.29 to the current version still doesn’t work.
so the first picture shows that basically LetsEncrypt couldnt get the challenge from your meshcentral server for some reason?
as for the 2nd picture, this hasnt run meshcentral correctly as it running on port 1025,
you might need to do as it explains
sudo setcap 'cap_net_bind_service=+ep'...this allows node to run with less than port 1025 also remember to STOP meshcentral before handsystemctl stop meshcentraland also maybe usesudo