Cloudron Forum

@girish Well I managed to get the config back by copying it regardless. So no harm was really done.

One thing I've noticed is that I saw that Cloudron had created a DNS query off of a redirect I had because I had wanted to change domains, and had a redirect set for the old one, I tried deleting that. And now off my home wifi, I can access mastodon again in full, but not the cloudron admin panel. Trying to access it causes the connection to time out.

Would it be ok to post the box logs here? Do they contain any sensitive/private information that shouldn't be posted publicly?

I kept removing and adding a second domain both from digital ocean's interface to fully purge and then adding it again from the cloudron interface as a way to troubleshoot a mastodon server I was adding matrix to that wouldn't work no matter how many times I entered a known hosts. But now after adding the second domain, the page suddenly refreshed, and I can't access the dashboard anymore, and while I can access my mastodon's interface. It keeps saying "Oops! An unexpected error occurred." and won't show anything. Rebooting did not fix the issue either.

So far I tried deleting the nginx config file in /etc/nginx, but that didn't work (Nor did Cloudron make a new file like the docs said it would). I used the cloudron digitalocean droplet in the marketplace to make this one.

It doesn't seem to be a problem with the DNS configuration on my Digitalocean because I can access the GUI of Mastodon, but not the inner parts like the profile configuration. Is there a command I can use to repair my cloudron or would it be easier to backup everything and blow up the droplet, then reimport?