Failed deployment
- Open the project → Logs tab.
- Identify the failing step:
- clone: repository inaccessible, wrong Git permissions, repository too large.
- dockerfile: technology not detected — check the repository structure.
- upload: not enough disk space on the server.
- build: compilation error, missing dependency, image not found on Docker Hub.
- deploy: port already in use, missing variable, container conflict.
- healthcheck: the app did not respond within 60 seconds.
- Paylood shows an automatic diagnostic based on the logs (last lines).
Tip
Retry with the no-cache option if the problem looks like a corrupted Docker cache.
The app runs but returns an error
| Symptom | Likely cause | Check |
|---|---|---|
| 502 / 504 | Healthcheck passed but app is slow | Open the console (top, logs) |
| Database not connected | Wrong variables | Check the Variables tab then redeploy |
| Blank frontend page | Build without injected VITE_* | Check the build variables |
| Invalid certificate | Domain not yet verified | Check the domain status |
The Git webhook triggers nothing
- Is auto-deploy enabled? (project Settings)
- Is the webhook present at the provider? (repository settings → Webhooks)
- Does the push branch match the environment?
- Does the webhook point to a public URL?
SSH connection impossible
- Timeout: port 22 closed, wrong IP, firewall.
- Permission denied: wrong user or password.
- Host key rejected: reset the server in Paylood.
A service does not start
- Check the image version (name + tag).
- Check that the port is not already in use on the server.
- Check the container logs via the Console (
docker ps,docker logs <id>). - Check the service’s environment variables.
DNS / domain verification failed
- Does the A record point to your VPS IP?
- Is propagation complete? (use
digor an online tool) - Paylood must be reachable on the domain (no external CNAME).
Failed backup
- Is the database container running on the server?
- Is there enough disk space?
- Are the database access variables correct?
Console not responding
- Is the server active?
- Has the project been deployed at least once?
- Is the network connection stable? Reload the page.
Reporting a bug
Open an issue on the GitHub repository with:
- The steps to reproduce.
- The relevant logs.
- The installation version / commit.
Most problems are fixed by a redeploy after correcting variables or the repository. Feel free to use the Console to diagnose live.