high severityRender.com deployments
Deploy shows as successful and healthy in Render dashboard (internal health checks pass), but public access to the service (onrender.com URL or custom domain) returns 502 Bad Gateway errors. Happens especially after initial failed deploys or around deployment times; users can shell in and confirm app runs, but external requests fail.
Root cause
When the first build/deploy of a new service fails (even if subsequent deploys succeed), Render fails to create necessary networking components like the load balancer, leading to misconfigured routing even for healthy instances. Internal health checks pass, but public traffic gets 502 errors.
Render.comdeployment502 errorzero-downtimeload balancerhealth checknetworking