cloudron hangs up needing a restart at least every few days
-
@scooke That's right. But the company is based in CA. American companies are subject to the Freedom Act (formerly: Patriot Act) and are therefore obliged to allow US authorities potential access to the (cloud) data of their customers.
I am leaving my comfortable G-Suite and will fully comply with data protection regulations with my hosted solutions. Do it once, do it right
-
@Captain-Kirk Ah, I understand now. Sorry about that. What company will you choose? I'm also looking for an EU-based host.
@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 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 -
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
-
@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 unboundto see if unbound is runninghost www.cloudron.io 127.0.0.1this queries unbound to resolve the domain namehost www.cloudron.io 8.8.8.8this queries google DNS to resolve the domain name
Do all the above look good?
-
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
@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 hostThe 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 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 hostThe 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.
-
