Cloudron Forum

@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!

@cleveradmin OK, I reread your original post and understood now. You are offering your setup as a way to understand how to recover MySQL which is in some indeterminate state. In general, we don't attempt to recover databases unless it's super crucial. It's almost always just easy to recover from a backup and we also don't support setups with no backup. (IMO, MySQL recovery is very complicated and kind of arcane. Fixing one issue leads to another and it can take days really. So, not worth the effort.)

@DAMO11-coder see https://docs.cloudron.io/troubleshooting/#expired-domain

@Nozy said in Error: listen EADDRNOTAVAIL: address not available 172.18.0.1:3003: the gm docker still is not remove If you click on the app icon, it will show you the error as to why it's not uninstalling.

@jjhill Can you check if nginx is running ? See https://docs.cloudron.io/troubleshooting/

Hi, brilliant - that was the solution thank you so much kr, Andreas @girish said in Forgot primary domain: cloudron-support --admin-login

@jdaviescoates you could set up a cron that gets usage info, and prints out a webpage you can monitor with Kuma for a keyword. When a threshold is met, you add/remove the keyword and fire off an alert via TG. Similar for monitoring something with change detection app or n8n workflow.