Cloudron 9.0.8 Backup to site sshfs rsync hetzner storagebox

[avatar1024]

Also without doing anything, now re running "backup now" completed just fine . Anyway, should I just remove the specific DNS config in the broken instance?

By the way, both instances have ipv6 disabled, and normally should be exactly the same network wise.

[james]

Hello @avatar1024

@avatar1024 said:

Also without doing anything, now re running "backup now" completed just fine

This does point to either a temporary DNS issue or the Hetzner fail2ban expired.

With:

sshfs -p 23 u273486@u273486.your-storagebox.de:/home $WHERE_YOU_WANT_IT_MOUNTED

You can always test a mount from either your local computer or any cloudron server.

Also, keep in mind, Hetzner Storage Boxes have a concurrent connections limit of 10.
So if you re-use the same Hetzner Storage Box for multiple Cloudron servers or even other things, this limit can be hit.
Each sshfs mount from a Cloudron Backup Site is 1x connection that stays active.

[avatar1024]

@james said:

You can always test a mount from either your local computer

Local sshfs mount work just fine.

@james said:

Also, keep in mind, Hetzner Storage Boxes have a concurrent connections limit of 10.

There are only 3 concurrent connections on the box, two Cloudron instances (one mount in each) and one local.

But the specific DNS config on the broken instance might be the source of the issue?

[Resolve]
DNS=46.38.225.230 46.38.252.230 2a03:4000:8000::fce6 2a03:4000:0:1::e1e6
#FallbackDNS=
#Domains=
LLMNR=no
MulticastDNS=no
DNSSEC=allow-downgrade
Cache=yes
DNSStubListener=yes

[nebulon]

I am not sure if resolvd correctly dismisses the ipv6 DNS resolver while you have ipv6 apparently disabled as you mentioned that. So maybe try to copy that DNS=46.38.225.230 46.38.252.230 2a03:4000:8000::fce6 2a03:4000:0:1::e1e6 line and comment it out then add a new one with just ipv4 DNS=46.38.225.230

[avatar1024]

For now I've commented everything line in the working instance and rebooted the server. If there is an issue I'll re-add the ipv4 DNS. Many thanks to you two for looking into this and helping. I'll report tomorrow to let you if it's resolved.

[avatar1024]

All good. A few backups have happened since the change and it all went smoothly. What has created the issue for the past few days is a mystery (since instance has been running like this for years) but thanks to you it's all back on track.