Cloudron Forum

indeed,

uninstall nodejs entirely. apt remove nodejs. Then, you will find Cloudron's nodejs in /usr/local/node-14.15.4 . Just ln -sf /usr/local/node-14.15.4/bin/node /usr/bin/node. Then, if node --version gives the correct output, do systemctl restart box .

did the trick.

You folks rock, thanks!!!

Just to note here, a server reboot often is not the best idea if some services are still up and running. Nearly everything can be fixed while the server is active and a reboot might just bring down those unnecessarily.

Many thanks, after deleting config file for freshrss the restart of nginx went OK.

@ReessKennedy said in Digital Ocean Issues after altering Droplet name?:

Changed name of droplet.

but this is a superficial change that I think only occurs in a Digital Ocean database just for labeling and does not impact any server config.

In DigitalOcean, the name of the droplet is also the reverse/PTR address for the IP address. Just something to remember, this is not the reason your Cloudron is unreachable though.

All systems seem like they are working fine

Can you also run cloudron-support --troubleshoot on the server?

Thanks @girish for the quick reply. I'm getting there.

@nebulon said in Cloudron dashboard not loading after reboot after NextCloud "not responding":

Most likely you are hitting an unbound issue then. Checkout the unbound section at https://docs.cloudron.io/troubleshooting/

Unbound solved my issues, thank you! 🙂

@natzilla Ah ok, I think I will improve the docs to say how to exactly recover if mysql is not even running. The troubleshooting guide assumes mysql is running but corrupt.