Get unstuck, fast.
Search the docs for step-by-step fixes. If something still behaves unexpectedly, raise a ticket — we reply on the ticket.
Top troubleshooting guides
- Fix a failed build on DployHubYour deploy failed during the build? Learn what the common build errors on DployHub mean and how to fix detection, start command, clone and timeout issues.
- App not answering on its port: fix health check failsSeeing "didn't answer on port within 90 seconds"? Learn why the health check fails and how to listen on PORT and 0.0.0.0 in Express, Flask and FastAPI.
- App crashed out of memory (exit code 137)Exit code 137 means your app ran out of memory. Learn how to confirm it in metrics, add more RAM, and tune Node.js heap size or gunicorn workers to fit.
- Custom domain not working or HTTPS not issuedCustom domain not loading or no HTTPS certificate yet? Check your CNAME with dig or nslookup, fix Cloudflare proxy and root domain issues, step by step.
- Staging paused or stopped: how to start it againStaging stopped after a week without deploys? Learn why free staging pauses on DployHub, how to start it in one click, and what it means for going live.
- Can't log in to DployHub? Reset your passwordLocked out of DployHub? Reset your password with an email link, fix common sign-in problems, and raise a ticket without logging in if you still need help.
Is it just me?
Check live platform status before raising a ticket.
Still stuck? Raise a ticket.
Tickets are the one way to reach the DployHub team — for unexpected results, problems the docs don’t solve, or when you can’t get into your account.
- • Include the app name and environment (staging or live)
- • Say when it happened and what you expected
- • List what you’ve already tried
- • Never send passwords or secrets
About support.
How do I get help with DployHub?
Search the docs first — most questions about deploys, domains, billing and errors are answered there step by step. If something still behaves unexpectedly, raise a ticket. Logged-in customers raise tickets from Help & tickets in the dashboard; if you can’t sign in, use the form on this page.
What should I include in a ticket?
The app name, whether it is staging or live, roughly when it happened, what you expected and what you saw instead, and what you have already tried. Never include passwords, API keys or other secrets.
How will I hear back?
We reply on the ticket. Logged-in customers see replies in the dashboard and get a notification; if you raised the ticket from this page, we email you a private link to follow it and reply.
I forgot my password. Do I need a ticket?
No — use “Forgot password” on the log-in page to get a reset link by email. It is valid for one hour. Raise a ticket only if the email never arrives or you no longer have access to that inbox.