Not Able to access the the cloudron dashboard
-
My simple dashboard has an problem, Unable to access the Cloudron Dashboard,
But my all app is accessed through their URL.
All App is running fine, But Only I am unable to access the dashboard.
systemctl status box
systemctl status docker
systemctl status nginxAll app is running fine, But I see the the SSL of cloudron dashboard SSL is expired, Not able to renew that SSL, I have restarted several time Complete software,
But New SSL is not generated by the nginx for dashboard.
And the Log file is empty. Nothing in log file. -
@shivamkb17 Which DNS provider are you using ? If you go to Domains -> Select the domain -> Click Save. Does it save or show some error?
-
Now I used Old generated SSL,
I am using cloudflare.Not able to access dashboard.
https://ibb.co/b1WZ80S
Also I am ataching the output of some commands.
systemctl status nginx● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/nginx.service.d
└─cloudron.conf
Active: active (running) since Fri 2023-05-05 16:35:21 UTC; 34s ago
Docs: man:nginx(8)
Process: 419 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
Process: 460 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
Main PID: 480 (nginx)
Tasks: 5 (limit: 9477)
Memory: 17.2M
CGroup: /system.slice/nginx.service
├─480 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;
├─481 nginx: worker process
├─482 nginx: worker process
├─483 nginx: worker process
└─484 nginx: worker processMay 05 16:35:21 my.xxxxxxxx.com nginx[460]: nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/yellowtent/platformdata/nginx/cert/.xxxxxxxx.com.cert"
May 05 16:35:21 my.xxxxxxxx.com nginx[460]: nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/yellowtent/platformdata/nginx/cert/.xxxxxxxx.com.cert"
May 05 16:35:21 my.xxxxxxxx.com nginx[460]: nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/yellowtent/platformdata/nginx/cert/.xxxxxxxx.com.cert"
May 05 16:35:21 my.xxxxxxxx.com nginx[460]: nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/yellowtent/platformdata/nginx/cert/.xxxxxxxx.com.cert"
May 05 16:35:21 my.xxxxxxxx.com nginx[460]: nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/yellowtent/platformdata/nginx/cert/.xxxxxxxx.com.cert"
May 05 16:35:21 my.xxxxxxxx.com nginx[460]: nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/yellowtent/platformdata/nginx/cert/.xxxxxxxx.com.cert"
May 05 16:35:21 my.xxxxxxxx.com nginx[460]: nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/yellowtent/platformdata/nginx/cert/.xxxxxxxx.com.cert"
May 05 16:35:21 my.xxxxxxxx.com nginx[460]: nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/yellowtent/platformdata/nginx/cert/.xxxxxxxx.com.cert"
May 05 16:35:21 my.xxxxxxxx.com nginx[460]: nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/home/yellowtent/platformdata/nginx/cert/_.xxxxxxxx.com.cert"
May 05 16:35:21 my.xxxxxxxx.com systemd[1]: Started A high performance web server and a reverse proxy server.root@my:~# systemctl status box
● box.service - Cloudron Admin
Loaded: loaded (/etc/systemd/system/box.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-05-05 16:39:50 UTC; 284ms ago
Main PID: 10048 (node)
Tasks: 6 (limit: 9477)
Memory: 4.8M (max: 400.0M)
CGroup: /system.slice/box.service
└─10048 node /home/yellowtent/box/box.jsMay 05 16:39:50 my.xxxxxxxx.com systemd[1]: Started Cloudron Admin.
Docs: https://docs.docker.com
Main PID: 1194 (dockerd)
Tasks: 131
Memory: 118.4M
CGroup: /system.slice/docker.service
├─1194 /usr/bin/dockerd -H fd:// --log-driver=journald --exec-opt native.cgroupdriver=cgroupfs --storage-driver=overlay2 --experimental --ip6tables
├─1691 /usr/bin/docker-proxy -proto udp -host-ip 0.0.0.0 -host-port 10000 -container-ip xx.xx.x.xx.xxx -container-port 10000
├─1812 /usr/bin/docker-proxy -proto udp -host-ip :: -host-port 10000 -container-ip fd00:c107:d509::b -container-port 10000
├─1845 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 222 -container-ip xx.xx.x.xx.xxx -container-port 22
├─1907 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 4443 -container-ip fd00:c107:d509::b -container-port 4443
├─1947 /usr/bin/docker-proxy -proto tcp -host-ip 127.0.0.1 -host-port 2003 -container-ip xx.xx.x.xx.xxx -container-port 2003
├─1979 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 29418 -container-ip fd00:c107:d509::11 -container-port 29418
├─2075 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 4443 -container-ip xx.xx.x.xx.xxx -container-port 4443
└─2105 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 29418 -container-ip xx.xx.x.xx.xxx -container-port 29418systemctl status docker
May 05 16:37:25 my.xxxxxxxx.com systemd[1]: Started Docker Application Container Engine.
May 05 16:37:25 my.xxxxxxxx.com dockerd[1194]: time="2023-05-05T16:37:25.889886185Z" level=info msg="API listen on /run/docker.sock"
May 05 16:37:25 my.xxxxxxxx.com dockerd[1194]: time="2023-05-05T16:37:25.959715570Z" level=info msg="ignoring event" container=bac0396730e1db68e775e2f38476200a69b4c7061b7487fc8645a04fc0d65faf module=libcontainerd namespace=moby top>
May 05 16:37:27 my.xxxxxxxx.com dockerd[1194]: time="2023-05-05T16:37:27.576959315Z" level=info msg="ignoring event" container=bac0396730e1db68e775e2f38476200a69b4c7061b7487fc8645a04fc0d65faf module=libcontainerd namespace=moby top>
May 05 16:37:28 my.xxxxxxxx.com dockerd[1194]: time="2023-05-05T16:37:28.566711891Z" level=info msg="ignoring event" container=f1135a0dc56f67022331f65041838834a429b1d45cc95fd0036c954147884c79 module=libcontainerd namespace=moby top>
May 05 16:37:29 my.xxxxxxxx.com dockerd[1194]: time="2023-05-05T16:37:29.278192921Z" level=info msg="ignoring event" container=bac0396730e1db68e775e2f38476200a69b4c7061b7487fc8645a04fc0d65faf module=libcontainerd namespace=moby top>
May 05 16:37:29 my.xxxxxxxx.com dockerd[1194]: time="2023-05-05T16:37:29.492749424Z" level=info msg="ignoring event" container=3a3ae1007095d7bf0a28b6e08e7ab2edd03f79d6b706f0465385903b18628b03 module=libcontainerd namespace=moby top>
May 05 16:37:31 my.xxxxxxxx.com dockerd[1194]: time="2023-05-05T16:37:31.663128380Z" level=info msg="ignoring event" container=bac0396730e1db68e775e2f38476200a69b4c7061b7487fc8645a04fc0d65faf module=libcontainerd namespace=moby top>
May 05 16:37:31 my.xxxxxxxx.com dockerd[1194]: time="2023-05-05T16:37:31.835449797Z" level=info msg="ignoring event" container=f1135a0dc56f67022331f65041838834a429b1d45cc95fd0036c954147884c79 module=libcontai -
Output of journalctl -u box -fa
Actually app is continously crashing.
May 06 03:50:52 my.examples.com systemd[1]: box.service: Main process exited, code=exited, status=1/FAILURE
May 06 03:50:52 my.examples.com systemd[1]: box.service: Failed with result 'exit-code'.
May 06 03:50:53 my.examples.com systemd[1]: box.service: Scheduled restart job, restart counter is at 83.
May 06 03:50:53 my.examples.com systemd[1]: Stopped Cloudron Admin.
May 06 03:50:53 my.examples.com systemd[1]: Started Cloudron Admin.
May 06 03:50:53 my.examples.com box.js[289867]: /home/yellowtent/box/src/apps.js:372
May 06 03:50:53 my.examples.com box.js[289867]: let schedulerConfig = app.manifest.addons?.scheduler || null;
May 06 03:50:53 my.examples.com box.js[289867]: ^
May 06 03:50:53 my.examples.com box.js[289867]: SyntaxError: Unexpected token .
May 06 03:50:53 my.examples.com box.js[289867]: at Module._compile (internal/modules/cjs/loader.js:723:23)
May 06 03:50:53 my.examples.com box.js[289867]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
May 06 03:50:53 my.examples.com box.js[289867]: at Module.load (internal/modules/cjs/loader.js:653:32)
May 06 03:50:53 my.examples.com box.js[289867]: at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
May 06 03:50:53 my.examples.com box.js[289867]: at Function.Module._load (internal/modules/cjs/loader.js:585:3)
May 06 03:50:53 my.examples.com box.js[289867]: at Module.require (internal/modules/cjs/loader.js:692:17)
May 06 03:50:53 my.examples.com box.js[289867]: at require (internal/modules/cjs/helpers.js:25:18)
May 06 03:50:53 my.examples.com box.js[289867]: at Object.<anonymous> (/home/yellowtent/box/src/ldap.js:12:12)
May 06 03:50:53 my.examples.com box.js[289867]: at Module._compile (internal/modules/cjs/loader.js:778:30)
May 06 03:50:53 my.examples.com box.js[289867]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
May 06 03:50:53 my.examples.com systemd[1]: box.service: Main process exited, code=exited, status=1/FAILURE
May 06 03:50:53 my.examples.com systemd[1]: box.service: Failed with result 'exit-code'.
May 06 03:50:53 my.examples.com systemd[1]: box.service: Scheduled restart job, restart counter is at 84.
May 06 03:50:53 my.examples.com systemd[1]: Stopped Cloudron Admin. -
@shivamkb17 This looks like you updated the node version on the server . Can you check the output of
node --version
? -
Finally I got the issue, The Issue is same as
https://forum.cloudron.io/topic/6274/dashboard-unavailable-apps-are-currently-fine/3 -
@shivamkb17 Yes, looks like that. The correct version of node should be 16.18.1 .
First, uninstall the nodejs package from the package manager. Then,
ln -sf /usr/local/node-16.18.1/bin/node /usr/bin/node ln -sf /usr/local/node-16.18.1/bin/npm /usr/bin/npm
Now, check the node version again.
-
ok, Now Server is running smooth.
-
-
-
@girish Are you saying that the user manually updated the node version, which I assume is the one that Cloudron that installed, and it installed that version so that it works, but then had this issue because they did something that they aren't advised to do (which is manually update)???
It might be worthwhile to highlight the fact (on the homepage or in the install instructions) that Cloudron manages the VPS for the user so that new users don't keep doing this, _running
apt-get update
on their own!