App inaccessible (502 Bad Gateway) after domain mapping — works only after restart
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
I’m facing a consistent issue where a newly deployed Python + Vite app on Dokploy shows a 502 Bad Gateway error immediately after deployment. Once I restart the Dokploy server or redeploy the service, the app starts working correctly.
Describe the solution you'd like
It looks like the service or proxy doesn’t start routing properly right after deployment.
Reproduction:
1.Deploy any Python + Vite app.
2.Map a domain via Dokploy.
3.Access the domain — returns 502.
4.Restart server — app works.
Describe alternatives you've considered
App should be accessible right after deployment.
Additional context
Actual Behavior:
App is unavailable (502) until restart.
Notes:
Could be related to container startup timing, proxy routing refresh, or DNS propagation handling within Dokploy.
Will you send a PR to implement it?
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with a Python + Vite app: deploy it in Dokploy, map a domain, and record the proxy and service logs while the first request returns 502. Compare the startup and routing state before and after a server restart; done means the mapped domain serves the app immediately after deployment without manual restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, vite
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100