Cloudron Forum

Thanks, @nebulon—this worked! ♥

node.js has a "happy eyeballs" quirk. This causes premature network errors when there is no ipv6 and ipv4 is slow. I have fixed this in https://git.cloudron.io/cloudron/box/-/commit/aefa481c43603d284346d58497b6ff5b462efd88

As far as I understand those CVEs they are not relevant in that context. For the first, we don't use those affected configs and the second is for the ssh-agent.

Given that the Ubuntu team usually knows what they do and are working closely together with upstream projects, there seems no need here to go beyond their recommendations of versions they push out via security updates.

@joseph , Running 'cloudron-support --recreate-containers' fixed the issue. Thank you.

Happens a LOT 😄 I don't mind at all.

@nebulon a checklist of current apps will be ideal scenario

@Beardmancer said in Failed backups and email config issue since 8.0.3 upgrade:

I decided to go ahead and try adding this to /etc/systemd/resolved.conf since it's easy enough to comment out.

DNS=8.8.8.8 1.1.1.1

After doing that and restarting the service with systemctl restart systemd-resolved, things seem to be working correctly. The file /etc/resolv.conf lists nameservers now and a manually-initiated backup just completed successfully. Thanks for the hlep @nebulon !

In the future, is there anything I should look out for to avoid this? I don't know what caused it. Maybe it was the 8.0.3 upgrade, or maybe it was an Ubuntu update? I think I rebooted Cloudron for the latter recently. If there's a configuration I might have setup wrong, I'd love to correct it.

@imc67 8.0.3 is needed

Thank you!

It did turn out to be a DNC issue which Joseph at Clourdon support fixed and then created a backup.

Sorted out on support. This had to do with some efi package blocking apt updates and thus the update stopped mid way.

I guess that is solved via https://forum.cloudron.io/post/95877

@joseph Thanks, that was it! It's all working now.

Thank you, that is something.

The issue was that docker got stuck in removing the Cloudron network during the starting after the update. Not clear why and when this happens but stopping docker then running docker network rm -f cloudron manually (which will start docker due to socket activation) makes it work...

Thanks, it's working !

Turns out that Cloudron hit the same issue as https://forum.cloudron.io/topic/11276/cloudron-update-to-7-7-0-postgresql-does-not-start?_=1723244919333 and the fixed worked there also.

Can you check the update task logs for the error? You can find those in the Settings view in your Cloudron dashboard.

After some restart it looks like it's working again.
Thank you for your help