cloudron hangs up needing a restart at least every few days

[scooke]

@Captain-Kirk Ah, I understand now. Sorry about that. What company will you choose? I'm also looking for an EU-based host.

[A Former User]

@scooke I wait until Cloudron Version 6 is released, where Ubuntu 20.04 is supported. Then I will move to Contabo. A lot of the memebers here trust in them.
https://contabo.de/?show=vps

[scooke]

@Captain-Kirk Pretty good prices actually. Thanks.

[msbt]

Sorry to hijack this topic for contabo related questions, but there seem to be a lot of customers here that could maybe shed some light on my issue. I ordered a VPS 1400 and setting it up worked fine (although being slower than anything I have from hetzner, from connecting via ssh - this takes a few seconds sometimes - to installing things), but after 2-3 days I wanted to reinstall Nextcloud and realized that it couldn't resolve any domain names. I've already contacted support, but maybe this is a known issue and there's already a solution for it.

Basically the name resolution stopped working, so Cloudron can't download the docker images or get a read from api/appstore. Restart didn't solve it and I didn't change anything. Any thoughts?

Cheers, M

[girish]

@msbt I would start by debugging at the server level.

• Check /etc/resolv.conf . This gives the DNS server the system uses. In Cloudron, this should be set to 127.0.0.1. This is where unbound is listening.
• systemctl status unbound to see if unbound is running
• host www.cloudron.io 127.0.0.1 this queries unbound to resolve the domain name
• host www.cloudron.io 8.8.8.8 this queries google DNS to resolve the domain name

Do all the above look good?

[subven]

@msbt I had this exact issue while installing Cloudron an a Contabo VPS lately. The installer was unable to pull docker containers because of errors like this:

Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.65.1:53: no such host

The problem was that Contabos Ubuntu image uses Contabos own nameservers and enforces DNSSEC. I can post you my configuration changes if you need them.

PS: I have also set host entries for docker.io (before I found the real issue) but that should only be a temporary fix because their IPs can change.

[msbt]

@subven that would be nice, I just "solved" the issue with a complete shutdown and reboot, for whatever reason it started working again. If you have a more permanent solution, would appreciate if you could share it.

thanks @girish, I'll try that the next time, at the moment it's working again.

[subven]

@msbt SSH into your server and check if systemd-resolved is running