Dude, this DNS_PROBE_FINISHED_BAD_CONFIG issue is super annoying! From what u described, ur app is running fine (logs OK, webhooks working), but the public domains aren't resolving. Classic Metal Edge or Railway DNS problem.Here's what usually fixes it:First, double-check if port 8080 is actually being used - sometimes Railway expects u to use the $PORT variable they inject. In ur code, try using process.env.PORT || 8080 (if Node) or equivalent in ur language.Check if there's any HTTP → HTTPS redirect happening that might be confusing the Metal Edge.Force a complete redeploy - not just redeploy, but change something in the code (like a comment) to force a total rebuild.Test the internal domain - curl lunch_app.railway.internal:8080 from inside another service to see if the issue is only with the public edge.If nothing works, hit up Railway's Discord - they're pretty active there and DNS/Metal Edge issues usually need manual intervention from their team.The fact that u created a new project and the problem persisted suggests it might be a bug on their end. On Discord, send them the Project ID and they can investigate the backend stuff.