Overview
When GitHub webhook not working, slow down and isolate the failure: build, runtime, networking, DNS, credentials, or resources. Better-PaaS gives you logs, deployment history, server tools, and configuration screens to work through the problem systematically.
Start here
First, confirm webhook URL, branch, delivery status, and secret validation. Then check the most recent deployment logs and confirm whether the app failed during build, startup, health check, or routing.
Step-by-step checks
Work from the app outward: source code, build output, runtime command, env vars, container health, router, DNS, then external services.
- Read the latest logs
- Confirm the app listens on the expected port
- Verify required environment variables
- Check database or service containers
- Retry after fixing one variable at a time
Prevent it next time
Keep build scripts explicit, document env vars, set backups for stateful apps, and verify a staging deployment before switching a production domain.
GitHub webhook delivery debugging
Open GitHub → Repository → Settings → Webhooks → Recent Deliveries. A 404 or connection refused means URL or firewall; 401/403 means secret mismatch.
- Webhook URL must be reachable from the public internet
- Branch filter must match your configured deploy branch
- Rotate webhook secret in both GitHub and Better-PaaS if unsure
- Test with a manual "Redeliver" on a recent push event
FAQ
Can Better-PaaS show logs for GitHub webhook not working?
Yes. Better-PaaS streams container logs in the dashboard and stores logs on disk for troubleshooting.
Should I redeploy immediately?
Only after changing one likely cause. Repeated redeploys without reading logs usually hide the real issue.