Automatic GitHub Deployment Not Triggering – Manual Deploy Required

[SwartZCoding]

To Reproduce

1. Push a new commit to the connected GitHub repository on the target branch (e.g., main or production).
2. Verify that the commit appears in the GitHub repository history.
3. Wait for the automatic deployment to be triggered in Dokploy.
4. Observe that no deployment is triggered automatically despite the webhook being configured and auto-deploy enabled.
5. Manually trigger a deployment from the Dokploy dashboard.
6. After the manual deploy, the latest commit is correctly associated with the deployment.

Current vs. Expected behavior

Current behavior:
GitHub commits are pushed and detected in the repository, but no automatic deployment
is triggered in Dokploy. The only way to deploy is manually via the dashboard.
After a manual deployment, the commit is correctly reflected.

Expected behavior:
Each push to the configured branch should automatically trigger a new deployment
via the GitHub webhook without requiring manual intervention.

Provide environment information

- Dokploy version: [0.27.1]
- Deployment type: Docker
- Git provider: GitHub
- Trigger method: GitHub webhook (auto-deploy enabled)
- Server setup: 1 core 2 workers
- OS: [Ubuntu 24.04]

Which area(s) are affected? (Select all that apply)

Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Both

Additional context

I've already checked the webhook delivery logs on GitHub's side, and the payloads are being sent successfully with a 200 response status. However, nothing happens on the Dokploy side no deployment is triggered despite the webhook being acknowledged.

Many people seem to have the same issue on Discord, but no fix has been found or applied so far. It's really unfortunate. Sorry I don't have more leads to help you out :).

https://discord.com/channels/1234073262418563112/1462592986557972727/1462592986557972727
https://discord.com/channels/1234073262418563112/1473971071622578318/1473971071622578318
https://discord.com/channels/1234073262418563112/1234073263584575511/1447386919594889216

Will you send a PR to fix it?

Maybe, need help

[Siumauricio]

Can you check the dokploy logs?

run the following command

docker logs -f $(docker ps --filter "name=dokploy.1" --format "{{.ID}}")

[vytenisstaugaitis]

I had this issue for a while. For me the issue was that the GitHub App URLs were still pointing to the server’s IP address instead of the domain which was added later.

Auto deploy started to work after updating the URLs in the GitHub App settings.

[EliasBorrajo]

Same issue here after migrating VPS1 → VPS2 using Dokploy's built-in backup/restore (Settings > WebServer > Backups → S3).

All projects, services and settings were restored correctly on VPS2, but GitHub autodeploy stopped working, pushes to main no longer triggered deployments.

Root cause: the GitHub App restored from backup still pointed to VPS1's URLs (homepage, callback, webhook). GitHub was sending push events to the old server.

Fix we're trying: create a separate GitHub App per VPS instance, each with its own domain. Will update once confirmed.

Hope this helps others hitting the same issue after a migration

[Siumauricio]

Closing — the root cause was identified in the comments (GitHub App URLs pointing to IP instead of domain). If the issue persists after updating the URLs, please open a new issue.

[VexoaXYZ]

This is an ongoing issue with my deployments too