Issue Running cloudron-support --troubleshoot After Reboot
-
Hello everyone,
I ran into an issue with Cloudron and had to run the following command:
sudo cloudron-support --recreate-dockerHowever, now after the first reboot, when I try to run the command again, I get this error:
/usr/bin/cloudron-support: line 685: warning: command not foundYou will find some logs here :
sudo cloudron-support --troubleshoot Vendor: ASUSTeK COMPUTER INC. Product: 5001_OVH Linux: 5.15.0-163-generic Ubuntu: jammy 22.04 Processor: Intel(R) Xeon(R) E-2236 CPU @ 3.40GHz x 12 RAM: 65758136KB Disk: /dev/md3 3.3T [FAIL] node version is incorrect. Expecting 20.18.0. Got 22.20.0. You can try the following to fix the problem: ln -sf /usr/local/node-20.18.0/bin/node /usr/bin/node ln -sf /usr/local/node-20.18.0/bin/npm /usr/bin/npm systemctl restart box2025-12-09T11:00:37.419Z box:server ========================================== 2025-12-09T11:00:37.419Z box:server Cloudron 8.3.2 2025-12-09T11:00:37.419Z box:server ========================================== 2025-12-09T11:00:37.419Z box:platform initialize: start platform 2025-12-09T11:00:37.438Z box:tasks stopAllTasks: stopping all tasks 2025-12-09T11:00:37.438Z box:shell tasks /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all 2025-12-09T11:00:37.451Z box:shell All tasks stopped 2025-12-09T11:00:37.539Z box:locks releaseAll: all locks released 2025-12-09T11:00:37.543Z box:reverseproxy writeDashboardConfig: writing dashboard config for mamoot.be 2025-12-09T11:00:37.550Z box:shell reverseproxy: openssl x509 -in /home/yellowtent/platformdata/nginx/cert/_.mamoot.be.cert -noout -ocsp_uri 2025-12-09T11:00:37.560Z box:shell reverseproxy /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx 2025-12-09T11:00:37.849Z box:platform onActivated: starting post activation services 2025-12-09T11:00:37.850Z box:platform startInfra: checking infrastructure 2025-12-09T11:00:37.850Z box:platform startInfra: infra is uptodate at version 49.8.0 2025-12-09T11:00:37.850Z box:platform onInfraReady: platform is ready. infra changed: false 2025-12-09T11:00:37.850Z box:apps schedulePendingTasks: scheduling app tasks 2025-12-09T11:00:37.871Z box:apptaskmanager started 2025-12-09T11:00:37.872Z box:cron startJobs: starting cron jobs with hour 20 and minute 15 2025-12-09T11:00:37.886Z box:cron backupPolicyChanged: schedule 00 00 23 * * * (Europe/Brussels) 2025-12-09T11:00:37.890Z box:cron autoupdatePatternChanged: pattern - 00 00 1,3,5,23 * * * (Europe/Brussels) 2025-12-09T11:00:37.891Z box:cron Dynamic DNS setting changed to true 2025-12-09T11:00:37.892Z box:dockerproxy start: listening on 172.18.0.1:3003Can anyone help me with this?
Thanks,
-
@roloufgoudebin there has been many changes to that script since 8.3 release. Can you try the latest one? You can replace /usr/bin/cloudron-support with the contents of this:
https://git.cloudron.io/platform/box/-/raw/master/scripts/cloudron-support?ref_type=heads
Also, can you elaborate why you are running that command in the first place?
-
/usr/bin/cloudron-support: line 766: warning: command not foundI tried to modify the content, but that doesn’t work either. I had to run this command because it helped me a lot a few months ago for a similar issue—my Cloudron instance wasn’t working at all, and it had solved the problem.
Thanks for your response.
-
Here’s what the command outputs :
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? -
Thanks! Here’s the current output of the command:
sudo cloudron-support --recreate-docker Starting docker afresh at /var/lib/docker Downloading addon images /usr/bin/cloudron-support: line 742: node: command not found -
ls: cannot access '/usr/local/node-20.18.0/bin/node': No such file or directoryI’ve tried both "ln" commands, but nothing works. I’m a bit desperate.
-
ls: cannot access '/usr/local/node-20.18.0/bin/node': No such file or directoryI’ve tried both "ln" commands, but nothing works. I’m a bit desperate.
-
@joseph There is version 22.20.0.
Thanks again for your help! -
What am I supposed to do now?
sudo ln -sf /usr/local/node-22.20.0/bin/node /usr/bin/node ubuntu@ns3046382:/usr/local$ sudo ln -sf /usr/local/node-22.20.0/bin/npm /usr/bin/npm ubuntu@ns3046382:/usr/local$ sudo cloudron-support --recreate-docker Starting docker afresh at /var/lib/docker Downloading addon images Pulling registry.docker.com/cloudron/graphite:3.5.0@sha256:ee7c9dc49a6507cb3e3cee25495b2044908feb91dac5df87a9633dea38fdeb8a ubuntu@ns3046382:/usr/local$ sudo cloudron-support --troubleshoot Vendor: ASUSTeK COMPUTER INC. Product: 5001_OVH Linux: 5.15.0-163-generic Ubuntu: jammy 22.04 ubuntu@ns3046382:/usr/local$ -
What am I supposed to do now?
sudo ln -sf /usr/local/node-22.20.0/bin/node /usr/bin/node ubuntu@ns3046382:/usr/local$ sudo ln -sf /usr/local/node-22.20.0/bin/npm /usr/bin/npm ubuntu@ns3046382:/usr/local$ sudo cloudron-support --recreate-docker Starting docker afresh at /var/lib/docker Downloading addon images Pulling registry.docker.com/cloudron/graphite:3.5.0@sha256:ee7c9dc49a6507cb3e3cee25495b2044908feb91dac5df87a9633dea38fdeb8a ubuntu@ns3046382:/usr/local$ sudo cloudron-support --troubleshoot Vendor: ASUSTeK COMPUTER INC. Product: 5001_OVH Linux: 5.15.0-163-generic Ubuntu: jammy 22.04 ubuntu@ns3046382:/usr/local$@RoloufGoudebin just to take a step back. Can you give us more background as to what happened to the server? Trying to understand why node symlinks have disappeared. If you can write to me at support@cloudron.io with more details, I can take a look.