Cannot back up apps and update to the new Cloudron version

[zonzonzon]

Cloudron version
9.0.15 (latest)

Summary

Web login (OIDC) fails with 500 Internal Server Error when geolocation.cloudron.io is unreachable (timeout or DNS failure). The error message returned is:

{"status":"Internal Server Error","message":"getaddrinfo EAI_AGAIN geolocation.cloudron.io"}

or

AggregateError [ETIMEDOUT]: connect ETIMEDOUT 167.99.137.196:443

Login is completely blocked — users cannot access the Cloudron dashboard or any apps.

[joseph]

165.227.67.76 is cloudron.io 's IP . It looks like the server cannot connect to cloudron.io ? Can you ping 165.227.67.76 on the server?

$ ping cloudron.io
PING cloudron.io (165.227.67.76) 56(84) bytes of data.
64 bytes from prod.cloudron.io (165.227.67.76): icmp_seq=1 ttl=53 time=114 ms
64 bytes from prod.cloudron.io (165.227.67.76): icmp_seq=2 ttl=53 time=127 ms
64 bytes from prod.cloudron.io (165.227.67.76): icmp_seq=3 ttl=53 time=310 ms

[joseph]

gelocation also works. But I am surprised that it blocks login. Let me check this internally.

$ ping geolocation.cloudron.io
PING geolocation.cloudron.io (167.99.137.196) 56(84) bytes of data.
64 bytes from my.public.cloudron.io (167.99.137.196): icmp_seq=1 ttl=56 time=18.3 ms
64 bytes from my.public.cloudron.io (167.99.137.196): icmp_seq=2 ttl=56 time=31.3 ms
64 bytes from my.public.cloudron.io (167.99.137.196): icmp_seq=3 ttl=56 time=17.2 ms

[zonzonzon]

I followed this guide and was able to log in, but I couldn’t update Cloudron to the latest version or back up the apps.

Edit src/oidcserver.js line 472 and wrap with safe(), then restart the box service:

# Backup
cp /home/yellowtent/box/src/oidcserver.js /home/yellowtent/box/src/oidcserver.js.bak

# Fix
sed -i 's/await users.notifyLoginLocation(user, ip, userAgent, auditSource);/await safe(users.notifyLoginLocation(user, ip, userAgent, auditSource));/' /home/yellowtent/box/src/oidcserver.js

# Restart
systemctl restart box

[girish]

@zonzonzon indeed! I applied the exact change just minutes ago when I was investigating your issue - https://git.cloudron.io/platform/box/-/commit/91b8f1a4574c3b30e6fd6f996fca23a6365388dc

But regardless, do investigate why cloudron.io and geolocation.cloudron.io cannot be reached .

[girish]

https://status.cloudron.io/status/cloudron

[zonzonzon]

Is it possible that my Cloudron is stuck on Cloudron version 9.0.15 (latest)? I also cannot update to the newest version through the UI. In Cloudron version 9.0.17 (latest), it seems this issue does not occur.

[zonzonzon]

Backup Sites
Schedule: Every day @ 23:00
Retention Policy: 1 week
Last run: Feb 5, 2026, 04:07 PM
Backup endpoint is not active: Error listing objects. code: undefined message: getaddrinfo EAI_AGAIN name.sgp1.digitaloceanspaces.com HTTP: undefined

[girish]

Have you tried running cloudron-support --troubleshoot already? It looks like DNS is not working on the server.

[zonzonzon]

Disk: /dev/vda1 38G
[OK] node version is correct
[OK] IPv6 is enabled in kernel. No public IPv6 address
[OK] docker is running
[OK] docker version is correct
[OK] MySQL is running
[OK] nginx is running
[OK] dashboard cert is valid
[OK] dashboard is reachable via loopback
[OK] No pending database migrations
[OK] Service 'mysql' is running and healthy
[OK] Service 'postgresql' is running and healthy
[OK] Service 'mongodb' is running and healthy
[OK] Service 'mail' is running and healthy
[OK] Service 'graphite' is running and healthy
[OK] Service 'sftp' is running and healthy
[OK] box v9.0.15 is running
[OK] netplan is good
[OK] DNS is resolving via systemd-resolved
[OK] Dashboard is reachable via domain name
[OK] unbound is running

Symptoms:

• TCP connection succeeds, but TLS handshake times out
• Both IPv4 (port 443) and IPv6 connections fail
• Outbound HTTPS to all other destinations works fine (e.g. Google, GitHub)
• All Cloudron services are running and healthy
• Error from box.log: "connect ETIMEDOUT ...prod.cloudron.io:443, connect ENETUNREACH ...IPv6 - Local (:::0)"

I've verified there are no local firewall rules blocking outbound traffic to your server. The issue appears to be on the prod.cloudron.io side — possibly our server IP is being rate-limited or blocked.