Common Dokploy issues and how to fix them

The commands in this guide run on your VPS over SSH as root (how to access it).

The panel does not load

If you have just ordered it, Dokploy finishes installing a few minutes after the first email. Wait for the "Your Dokploy is ready" email or for the "Your application" section in your panel to show the details. If nothing has changed after an hour, open a ticket.
If it used to work, check the Dokploy services and its proxy:

docker service ls
docker ps | grep traefik

dokploy, dokploy-postgres and dokploy-redis should show 1/1. The reason for a failure is usually in docker service logs --tail 80 dokploy.

Check with ufw status that ports 80 and 443 are still open.

The panel answers on `http://IP:3000`

If the HTTPS certificate was not ready when the installation finished, the panel is reachable for a while on port 3000. It is temporary: that access closes on its own as soon as HTTPS works. Switch to the HTTPS address as soon as you can.

I forgot the password

Find the panel container (the one named dokploy. followed by an identifier, not traefik, postgres or redis):

docker ps --format '{{.ID}}  {{.Names}}' | grep 'dokploy\.'

And generate a new password with its identifier:

docker exec -it CONTAINER_ID bash -c "pnpm run reset-password"

The command shows the new password. Change it to one of your own when you log in.

I lost two-factor authentication

With the same container:

docker exec -it CONTAINER_ID bash -c "pnpm run reset-2fa"

My application returns a 502 error or does not start

It is the most common issue at the beginning. Check the deployment logs and the application logs in Dokploy. The most frequent cause is that the domain's internal port does not match the port your application listens on. We do not debug your code, but we do help if it is the server that fails.

A port is open even though it is not in the firewall

That is normal Docker behaviour: ports published from Docker or Dokploy bypass ufw. Publish only the essential ones and serve your applications through a domain via Dokploy.

The disk fills up

Docker images and builds take a lot of space. Enable automatic cleanup under Settings → Web Server and see what uses the most with:

docker system df
df -h /

It runs out of memory during builds

Builds are the usage peak. Build less often, stop applications you do not use, or build elsewhere (for example in your CI system) and deploy the ready-made image. If the usage comes from your normal use, upgrade your plan without losing anything.

What support covers

We help you with the VPS and the Dokploy installation: keeping the server and the panel running, the initial access and the steps in these guides. The code and deployments of your applications are yours; for that you have the official Dokploy documentation. If something on the server is not working, open a ticket and, for security, do not paste passwords.

Order: Dokploy VPS in Frankfurt · in Miami

Was this article helpful?

Need more help?

Open a ticket and the support team goes through it with you.

Open a ticket