Cloudron Forum

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$ 

@joseph There is version 22.20.0.
Thanks again for your help!

ls: cannot access '/usr/local/node-20.18.0/bin/node': No such file or directory

I’ve tried both "ln" commands, but nothing works. I’m a bit desperate.

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

Here’s what the command outputs :

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

/usr/bin/cloudron-support: line 766: warning: command not found

I 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.

Hello everyone,

I ran into an issue with Cloudron and had to run the following command:

sudo cloudron-support --recreate-docker

However, 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 found

You 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 box

2025-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:3003

Can anyone help me with this?

Thanks,

Hello,

I finally managed to solve the issue as suggested above. I installed a second instance, which ended up working, then created a backup of version 3.1.3 (the one that wasn’t working) and imported that backup into the new instance.

Thanks for your help!

Thank you for your answer. I tried to clone the version before the update but I have this error in logs :

=> Healtheck error: Error: connect EHOSTUNREACH 172.18.19.202:8000
Oct 06 23:10:53 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.202:8000
Oct 06 23:11:03 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.202:8000
Oct 06 23:11:13 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.202:8000
Oct 06 23:11:14 DELETE 0
Oct 06 23:11:14 ERROR: syntax error at or near ","
Oct 06 23:11:14 LINE 1: ...n_endpoint', 'https://my.example.com/openid/auth', , 17597850...
Oct 06 23:11:14 UPDATE 1

Hi again,

I’ve tried installing Moodle on another Cloudron instance, but it doesn’t work either. Even with a fresh setup, the installation fails the same way as on my other instance.

It seems the issue is not limited to a single server, so it might be related to the recent update or the packaging itself.

Thanks!

Hi all,

Since the automatic Moodle update via Cloudron last night, my Moodle instance won’t start. The healthcheck fails (ECONNREFUSED), and PostgreSQL logs show repeated errors like:

2025-10-06 12:48:40.132 UTC ERROR: syntax error at or near "," at character 170
STATEMENT: INSERT INTO mdl_oauth2_endpoint (issuerid, name, url, usermodified, timecreated, timemodified)
VALUES (1, 'authorization_endpoint', 'https://my.ciamtc.com/openid/auth', , 1759754919, 1759754919)

It seems Moodle is trying to insert an OAuth2 endpoint with an empty usermodified field, which produces a syntax error in PostgreSQL.

I’ve already tried:

Restoring the Cloudron DB backup

Running SQL fixes manually

cloudron repair

… but nothing works. The problem seems to be with the OAuth2 plugin code deployed with the update, not the DB itself.

Has anyone else experienced this issue after the Cloudron update? Any ideas on how to start Moodle without breaking the DB?

Thanks in advance!

Hello,
I have this problem again, that's what I see in the log file :

2025-05-09T08:24:38.385Z box:services startPostgresql: starting postgresql container
2025-05-09T08:24:38.385Z box:shell services: /bin/bash -c docker run --restart=always -d --name=postgresql                 --hostname postgresql                 --net cloudron                 --net-alias postgresql                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=postgresql                 --ip 172.18.30.2                 --shm-size=128M                 -e 2025-05-09T08:24:50.285Z box:services Waiting for postgresql
2025-05-09T08:24:50.293Z box:services Attempt 1 failed. Will retry: Network error waiting for postgresql: connect ECONNREFUSED 172.18.30.2:3000
2025-05-09T08:25:05.461Z box:services importDatabase: Importing postgresql
2025-05-09T08:25:05.465Z box:services importDatabase: Importing addon postgresql of app 10a7e7b7-f03f-47f1-a7b1-8b09381cc623
2025-05-09T08:25:05.465Z box:services Setting up postgresql
2025-05-09T08:25:05.855Z box:services Setting postgresql addon config to [{"name":"CLOUDRON_POSTGRESQL_URL","value":"postgres://user10a7e7b7f03f47f1a7b18b09381cc623:8dd5dd83f64d820e4173e852f6a7ef77a3e5a14b4d7d8cd7919a806fa95c331fef3332ff671ecbe7ae5aa2b1be42d8fe2df3070dec515a3244e6549eafa43e60@postgresql/db10a7e7b7f03f47f1a7b18b09381cc623"}
2025-05-09T08:25:05.946Z box:services Clearing postgresql
2025-05-09T08:25:07.154Z box:services Restore postgresql
2025-05-09T08:25:07.156Z box:services pipeFileToRequest: piping /home/yellowtent/appsdata/10a7e7b7-f03f-47f1-a7b1-8b09381cc623/postgresqldump to 
2025-05-09T08:26:07.407Z box:services pipeFileToRequest: request completed with status code 200
2025-05-09T08:26:07.408Z box:services importDatabase: Importing addon postgresql of app 1af2288a-5400-4614-89ee-cc800cdaf016
2025-05-09T08:26:07.408Z box:services Setting up postgresql
2025-05-09T08:26:18.703Z box:services Setting postgresql addon config to {"name":"CLOUDRON_POSTGRESQL_USERNAME","value":"user1af2288a5400461489eecc800cdaf016"},{"name":"CLOUDRON_POSTGRESQL_PASSWORD","value":"7d6e2ed68b46efddd891307499d2acdb1d9ad70dbcfa2680848750b61955734a5017f11ea86bc928fb592f2079c6db2a1ef2040101a0b2e60af9fc62adc524a3"},{"name":"CLOUDRON_POSTGRESQL_HOST","value":"postgresql"},{"name":"CLOUDRON_POSTGRESQL_PORT","value":"5432"},{"name":"CLOUDRON_POSTGRESQL_DATABASE","value":"db1af2288a5400461489eecc800cdaf016"}]
2025-05-09T08:26:19.208Z box:services Clearing postgresql
2025-05-09T08:26:24.404Z box:services Restore postgresql
2025-05-09T08:26:24.406Z box:services pipeFileToRequest: piping /home/yellowtent/appsdata/1af2288a-5400-4614-89ee-cc800cdaf016/postgresqldump 
2025-05-09T08:26:53.512Z box:services pipeFileToRequest: request completed with status code 200
2025-05-09T08:26:53.513Z box:services importDatabase: Importing addon postgresql of app 2fb04af2-7707-4871-9d69-bca802607b24
2025-05-09T08:26:53.513Z box:services Setting up postgresql
2025-05-09T08:26:54.863Z box:services Setting postgresql addon config to 
2025-05-09T08:26:55.063Z box:services Clearing postgresql
2025-05-09T08:26:57.426Z box:services Restore postgresql
2025-05-09T08:26:57.428Z box:services pipeFileToRequest: piping /home/yellowtent/appsdata/2fb04af2-7707-4871-9d69-bca802607b24/postgresqldump to http://172.18.30.2:3000/databases/
2025-05-09T08:27:26.952Z box:services pipeFileToRequest: request completed with status code 200
2025-05-09T08:27:26.952Z box:services importDatabase: Importing addon postgresql of app 6732610f-b711-434e-8ba3-f30a3394682d
2025-05-09T08:27:26.952Z box:services Setting up postgresql
2025-05-09T08:27:27.351Z box:services Setting postgresql addon config to 
2025-05-09T08:27:27.420Z box:services Clearing postgresql
2025-05-09T08:27:31.539Z box:services Restore postgresql
2025-05-09T08:27:31.540Z box:services pipeFileToRequest
2025-05-09T08:27:43.041Z box:services pipeFileToRequest: request completed with status code 200
2025-05-09T08:27:43.041Z box:services importDatabase: Importing addon postgresql of app 6f2bfa4b-ed98-44be-b47b-78320c84bf7e
2025-05-09T08:27:43.041Z box:services Setting up postgresql
2025-05-09T08:27:43.878Z box:services Setting postgresql addon config to {"name":"CLOUDRON_POSTGRESQL_USERNAME","value":"user6f2bfa4bed9844beb47b78320c84bf7e"},{"name":"CLOUDRON_POSTGRESQL_PASSWORD","value":"b6586362dda5535a1c170593eea62d166216495ef7740bfa07b2c91049e6ce1defb66e9ba4fc9295c0635913c98796ef5a906e459530fff12f3c84e0b92a1db9"},{"name":"CLOUDRON_POSTGRESQL_HOST","value":"postgresql"},{"name":"CLOUDRON_POSTGRESQL_PORT","value":"5432"},{"name":"CLOUDRON_POSTGRESQL_DATABASE","value":"db6f2bfa4bed9844beb47b78320c84bf7e"}]
2025-05-09T08:27:44.143Z box:services Clearing postgresql
2025-05-09T08:27:49.983Z box:services Restore postgresql
2025-05-09T08:27:49.988Z box:services pipeFileToRequest: piping /home/yellowtent/appsdata/6f2bfa4b-ed98-44be-b47b-78320c84bf7e/postgresqldump to http://172.18.30.2:3000/databases/db6f2bfa4bed9844beb47b78320c84bf7e/restore?
2025-05-09T08:28:08.711Z box:services pipeFileToRequest: request completed with status code 200
2025-05-09T08:28:08.712Z box:services importDatabase: Importing addon postgresql of app 867da859-2dcd-4a93-9f37-969f0b2fe7b7
2025-05-09T08:28:08.712Z box:services Setting up postgresql
2025-05-09T08:28:09.205Z box:services Setting postgresql addon config to [{"name":"CLOUDRON_POSTGRESQL_URL","value":"postgres://user867da8592dcd4a939f37969f0b2fe7b7:879a359f96cd77df1c061a9376a3deed9b1b8aef5e5ad9a1915bec4950a92a204325efaea251fe76b16e15942442ad0fcf4d6871d7ea99ffc8799bac46bc1a37@postgresql/db867da8592dcd4a939f37969f0b2fe7b7"},{"name":"CLOUDRON_POSTGRESQL_USERNAME","value":"user867da8592dcd4a939f37969f0b2fe7b7"},{"name":"CLOUDRON_POSTGRESQL_PASSWORD","value":"879a359f96cd77df1c061a9376a3deed9b1b8aef5e5ad9a1915bec4950a92a204325efaea251fe76b16e15942442ad0fcf4d6871d7ea99ffc8799bac46bc1a37"},{"name":"CLOUDRON_POSTGRESQL_HOST","value":"postgresql"},{"name":"CLOUDRON_POSTGRESQL_PORT","value":"5432"},{"name":"CLOUDRON_POSTGRESQL_DATABASE","value":"db867da8592dcd4a939f37969f0b2fe7b7"}]
2025-05-09T08:28:09.283Z box:services Clearing postgresql

It looks like there is an issue with postgresql but I don't know how to solve it.

Thanks

After some restart it looks like it's working again.
Thank you for your help

Hello,

Cloudron automatically updated itself last night to version 8.0.3. This caused a crash, and I had to manually restart my server from the OVH panel. The server eventually restarted, but none of the applications are starting; they are all in the "configuring, queued" state since 2 hours.
I don't know what to do to fix the situation.

Thank you for reading.

Hello,

I can't start time tracking at my tasks.

I have this error on the dev console :

Response Status Error Code 404 from https://leantime.permafrost.mamoot.be/hx/timesheets/stopwatch/start-timer/
y @ htmx.min.js:1
fe @ htmx.min.js:1
ue @ htmx.min.js:1
qr @ htmx.min.js:1
E.onload @ htmx.min.js:1

Does someone knows something about that ?

Thanks,
Robin