Cloudron Forum

I thought I would just restart the server in case that fixes things after the weekend. The dashboard came up and I was able to start troubleshooting the unresponsive apps. I guess this is one of those things that cloudron fixes itself with those health checks. Thanks

@andreasdueren I'd be cautious about implementing it then. Cloudron hardens your server enough - doing more by installing more software, which is NOT recommended, will only lead to problems, especially if you don't already have a deep enough understanding of what is happening. It seems to be that @BrutalBirdie's gang knows their stuff (they're using Ansible to install Cloudron??? Yeah, that is next level coding there). Of course, they may also be paying for the Enterprise level of service (I'm not asking btw, no need to respond to that @BrutalBirdie ) so if they have hassles then I suppose it's fine for them to get help beyond typical Cloudron support, especially if they are doing more to their servers than what Cloudron themselves advise.

Thank you that worked!

Hm was there some namecheap API change recently?

@nebulon

That sounds like exactly what happened, what kind of monitoring solution would you recommend for cloudron (interested in space and RAM monitoring)? We've been hesitant about using any sort of apt get for fear of interfering with cloudron operation

So turns out we've resolved this portion.

Main issue is there were way too many confs pointing to the main problematic certficate. Everything in /home/yellowtent/platformdata/nginx/applications basically needed to be moved (/removed) in order to get nginx to restart again once more

@zezaung could this be related to your DNS issue from your other forum thread? Which certificate provider have you configured?

Adding a redirection made things work.

@zezaung hey sorry been sick today so I've been sleeping what page had the issue? Cause the site loads great for me

@zezaung hm in this case, it may be better reported in the upstream project I think, they are the experts on their app internals.

@johannesjom generally it is not supported to install other things via apt manually. There are some warnings about this when you SSH into your server, but we can't quite prevent users who have root access to their own server to install things or also change essential config files. So not sure what we can do here besides warning the user.

Debugged this with @ZeZaung a bit. Somehow, it was possible to re-run cloudron-setup on the existing install and this reset the database even though the app containers and data were still there. I have made a fix which should hopefully mitigate the problem.

Perhaps try the All in One Migration plugin, at least couple of us have successfully used that to migrate WordPress to Cloudron.

See e.g. this thread on How to move Wordpress.

Nope, there's no AAAA record, just an "A+ Dynamic DNS Record"

Incidentally, I'm about to switch this domain to Hetzner, in any event. Namecheap is ok but also quite annoying from time to time...