Unable to login to my admin panel and Cloudron apps (Possible local DNS or unbound issue?)

[girish]

@marylou when it's not reachable, try to ping the server and also ssh in to see if it's some issue from Contabo side.

[coniunctio]

@girish Thank you! I downloaded the Cloudron support diagnostics through terminal and emailed them with the link to this support forum post and the diagnostics / logs + my Cloudron ID. Hopefully I will hear back from someone soon.

[girish]

@coniunctio I have replied now. Let's continue there and post the conclusion here.

[coniunctio]

This post is deleted!

[coniunctio]

@girish I have gathered the information you requested and responded via email. I would really like (need) some live assistance from a support person.

[coniunctio]

To anyone following this thread, I have good news and bad news:

Good news: My issue is resolved. I am now able to log into my Cloudron Dashboard and apps at their respective subdomains, and Cloudron reverse proxying to my Docker apps/containers hosted outside of Cloudron.

Bad news: I tried every troubleshooting angle that I could find both via my own research, via Cloudron tech support, and through ChatGPT by unloading my error logs and step by step troubleshooting at the CLI/terminal level of my Ubuntu Server VM layer. Nothing worked.

Last night as a semi-regular part of my digital housecleaning and maintenance, I ran a disk permissions fix on my home NAS where the Ubuntu Server VM --> Cloudron resides and next thing I know, I received an email from @girish with a screenshot of my Cloudron Dashboard loading. 🧐

Are there any particular Cloudron or Ubuntu Server error logs that I might be able to throw into ChatGPT to figure out what happened so I can report back here?

[girish]

@coniunctio off. all quite strange, hard to guess what goes this working again! But from the logs you sent us on support@, the box code , nginx, unbound were all running fine. This means most likely it is some internal network issue .

[marylou]

@girish In our case, it is a Contabo side issue. Thanks!

[coniunctio]

@girish What is the location of the Cloudron log that would have observed any changes that were observed when I was able to use Cloudron again? Or is this an error log located at the Ubuntu Server (Virtual Machine, v24.04) level?

I will update this post with that information if I can find what changed for Cloudron to be available again, as the only change I can think of was doing a disk permissions fix to the "shared folder" that the VM is installed on the RAID configuration on my home NAS hardware. That seems like a very imprecise and not very helpful "resolution" to the issue related to this thread for archival (support) purposes.

[joseph]

@coniunctio the support tool collects logs and status from various tools.

• systemctl status mysql - status of the database used by cloudron dashboard
• systemctl status box - status of cloudron dashboard
• systemctl status nginx - status of nginx
• systemctl status docker - status of docker
• host my.domain.com - what you domain is pointing to

If the above look correct, it's likely everything is alright. This can be gather from the output of cloudron-support --send-diagnostics or cloudron-support --troubleshoot .

[coniunctio]

@joseph Thank you and yes, did all those, and was in communication with tech support. The issue is actually mysteriously resolved and I'm just trying to figure out what happened so I can share that in this thread and hopefully avoid repeating this issue in the future.