Reference
Coolify on Lofenta
Coolify is a self-hosted PaaS for managing your own Docker apps. Lofenta ships it as a one-click template (Developer plan and up). It deploys cleanly and the dashboard loads normally, but one thing trips people up on first login: the built-in "localhost" server shows "Sentinel Out Of Sync" and refuses to validate. That is expected, and this page explains exactly why.
The short version
Coolify wants to manage the Docker host it runs on. On Lofenta it cannot, because Lofenta deliberately does not give any customer container control over the machine underneath it. So do not try to validate or use the "localhost" server.
Instead, use Coolify the way it is designed to scale: add your own remote server (a VPS you control) over SSH under Servers, and deploy your apps to that. Coolify on Lofenta is the control panel, and your remote servers are where things run.
Why the "localhost" server will not validate
To manage a server, Coolify needs two things on that server: SSH access and the Docker socket (/var/run/docker.sock). The socket is how Coolify starts, stops, inspects, and builds containers. When Coolify first boots it registers the host it is running on as a server named "localhost" and tries to reach that socket. Its background agent ("Sentinel") reports the connection as out of sync when it cannot.
On Lofenta it never can, on purpose. Every project on Lofenta runs as a sandboxed container: dropped Linux capabilities, no-new-privileges, and no access to the host's Docker socket. Mounting that socket into a container is equivalent to handing the container root on the underlying server. Anything holding the socket can launch a new privileged container, bind-mount the host filesystem, read every other customer's data, and walk straight out of its sandbox.
That is the one door a multi-tenant platform can never open. So Coolify's "localhost" server staying unvalidated is not a bug in the template or a missing setting: it is Lofenta correctly refusing to give a customer container control of the host. The same isolation is what stops every other tenant from touching your project.
How to actually use Coolify here
- Open your Coolify project and log in. The dashboard runs fine.
- Go to Servers and add a remote server: a VPS you own, reachable over SSH. Coolify installs its agent there and manages Docker on that box.
- Deploy your applications and databases to that server. Leave the "localhost" server alone.
In other words, Coolify on Lofenta is a control plane for infrastructure you own elsewhere. If what you actually want is to run an app or a database directly on Lofenta, you do not need Coolify at all: create a Lofenta project (from a git repo, a Docker image, or a one-click template) and let the platform build, run, and give it HTTPS for you.
What Lofenta provisions for Coolify
The dashboard
The Coolify web app itself, served on your project subdomain over HTTPS.
PostgreSQL + Redis
Coolify's own database and cache, auto-provisioned as linked services and wired via environment variables. You do not set these up by hand.
Soketi (realtime)
A WebSocket server with shared Pusher credentials so Coolify's live UI updates work out of the box.
All three are managed Lofenta services, created automatically when you deploy the template. They back Coolify itself, not the servers Coolify deploys your apps to.
Just want to deploy an app?
You do not need Coolify to deploy on Lofenta. Point a git repo or a Docker image at a Lofenta project, or pick a one-click template, and the platform builds it, runs it, and issues HTTPS automatically.