Troubleshooting

The installer says port 80 or 443 is in use

Another program (Apache, Nginx, another panel) is using the port. Stop it or install Depanel on a clean machine. To see who is using it: sudo ss -ltnp | grep -E ':(80|443) '.

The panel does not open after installing

1. Check that the containers are up: cd /opt/depanel && docker compose ps.
2. Look at the API logs: docker compose logs api --tail 100.
3. If you used your own domain, check that the A record points to the server’s IP.

The domain stays at “Waiting for DNS” (Aguardando DNS)

The record does not point to the right machine yet, or the DNS change has not spread yet (it can take from minutes to a few hours). Check with dig +short shop.yourcompany.com: the result should be the machine’s IP.

The domain stays at “Waiting for HTTPS” (Aguardando HTTPS)

Let’s Encrypt needs to reach the machine’s port 80. Check the provider’s firewall and make sure no proxy (such as Cloudflare’s, the orange cloud) is blocking the challenge. With Cloudflare, leave the record as “DNS only” until the certificate is issued.

The deployment failed

Open the deployment in Deployments (Implantações): the log shows the step that failed. The most common ones:

• build: an app compile error — the same error shows up if you run the build on your computer;
• health check: the app did not respond on the given port — check the port and the start command;
• image not found: wrong image name or version, or a private registry without login.

The machine shows as “down”

The agent stopped responding. On the server: systemctl status depanel-agente and journalctl -u depanel-agente -n 50. The agent reconnects on its own when the network comes back.

The update was not applied

The panel is still on the old version and nothing changed. Usually the new image could not be downloaded (server internet or registry down). See the reason with docker logs depanel-atualizador and try again later.