SOLVED - Internal server unreachable after update to v4.0.0-beta.430 / Update to v4.0.0-beta.431 stuck

[NiMorama]

For anyone who might be having the same problem:

The update via the coolify view took forever for me and did not end. But the installation via the console worked, and then the internal coolify server was running again. It worked again after I both updated to .431 and manually changed the DB user from ‘coolify’ to ‘root’, what seemed to be the real problem.

https://coolify.io/docs/get-started/upgrade

curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash

##########################

Hello,

I updated my Coolify instance today to v4.0.0-beta.430.
Immediately afterwards the internal server (the default “localhost” entry) became “not reachable” in the Servers tab. Before the update, everything worked fine.

What happens

• Coolify UI is reachable, I can log in.
• My containers (e.g. Supabase, n8n) are still running and reachable.
• But the internal server (id=0) is shown as not reachable in the Servers tab, so I cannot manage deployments from within Coolify.

What I tried

• Verified that the SSH key Coolify uses is present and correct in /root/.ssh/authorized_keys.
• Verified permissions: /root and .ssh are 700, authorized_keys is 600.
• Verified SSH works manually:
  ssh -i /data/coolify/ssh/keys/ssh_key@… [email protected]

→ Works fine, login succeeds.

• Checked the database (servers table):
• After the update, the entry had user=coolify (which doesn’t exist on my server).
• I changed it to user=root.
• Result: Still “not reachable”.
• Logs (docker logs coolify) show jobs ServerConnectionCheckJob and ServerCheckJob running, but no errors — and validation_logs for the server is empty.

Follow-up

• A few hours after v4.0.0-beta.430, a new release v4.0.0-beta.431 was published.
• I tried to update to .431, but the update process runs endlessly and never finishes.

Expected

• The internal server should remain reachable after an update.
• The update process to .431 should complete successfully.

Current state

• My Coolify installation is accessible, and existing containers keep running.
• But the internal server is unreachable in Coolify, so no deployments or changes can be managed.
• Update to .431 doesn’t finish, still run and run and run

---

Could you please confirm if this is a known bug in beta.430 / 431 and advise whether there is a workaround or if we should wait for the next patch?

Thanks in advance!

[peaklabs-dev]

Yes, an external dependency broke SSH on v430, so if you are using v430 you need to upgrade manually to v431, which resolves the dependency issue.