@robi I'm not really sure where you're going with that so I can't comment.

As for the continued troubleshooting, I was able to get postgresql up manually with extensive help of ChatGPT. We ran into a DNS issue trying to do an APT reinstall of docker even after adjusting the resolv.conf. If anyone is interested I can give a full writeup, but i'll summarize here:

🧩 Cloudron 8.3.1 Upgrade – PostgreSQL & DNS Issues Summary

1. PostgreSQL Socket Failure

After updating to Cloudron 8.3.1, the PostgreSQL service showed as down in the Cloudron dashboard.
However, logs showed the database was running fine and accepting connections over TCP.
Cloudron healthchecks (and dependent services) failed due to the absence of the expected Unix socket at /var/run/postgresql/.s.PGSQL.5432.
Investigation showed:
- The actual socket was created in /run/postgresql/
- The symlink /var/run/postgresql → /run/postgresql was missing inside the PostgreSQL container

Fix: Re-created the symlink inside the container:

ln -s /run/postgresql /var/run/postgresql

Followed by:

supervisorctl restart postgresql

After this, PostgreSQL healthcheck passed, and dependent services began recovering.

2. APT Repository DNS/TLS Failure

While attempting to reinstall the Cloudron CLI to recover from a broken docker recreate, the APT repo at https://apt.cloudron.io was unreachable.
DNS (dig apt.cloudron.io) returned SOA records but no A records — even after:
- Disabling systemd-resolved
- Stopping unbound
- Overriding /etc/resolv.conf to use 8.8.8.8
- Confirming DNS worked for other domains (cloudron.io, google.com)
Attempts to work around with /etc/hosts resulted in a TLS handshake failure:
```
error:0A000410:SSL routines::sslv3 alert handshake failure
```
Root cause appears to be Cloudflare (which fronts apt.cloudron.io) rejecting connections when:
- DNS is bypassed via /etc/hosts, or
- Something in the server environment breaks SNI or TLS negotiation
Result: Unable to reinstall cloudron CLI using APT despite proper DNS config and working CA certs.

🧠 Context

This all occurred during/after a failed cloudron docker recreate attempt (as suggested on the forums).
That left the system partially repaired, with missing CLI tools and broken DNS.

So that's pretty much it. At this point i'm going to just set up a restore either through VM backup or Cloudron backup. I haven't decided yet. I won't do it until tomorrow though in case there's anything you'd like me to provide for future maintenance or research.

Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.

Cloudron Forum

stratus41298