10 days ago
Summary
Project: charming-enthusiasm / web service (nemc.up.railway.app)
Problem: Starting on July 23, 2025, my service container has been consistently failing to make outbound API calls (to Google OAuth, Supabase, etc.) due to a NameResolutionError (DNS lookup failure).
Analysis: A timeline analysis of deployment logs strongly suggests the root cause is a change in the server's network environment, as this issue began after I had fixed all application-level code bugs.
Request: I am requesting assistance in verifying my service's network environment (specifically if it's on "Metal Edge") and helping me restore it to the previously stable network (presumably GCP).
https://gist.github.com/truth0530/b52c7840c015bb61040bd1bc7516f167
0 Replies
10 days ago
The Metal migration started and finished significantly earlier based on the timestamps you provided. [Metal Edge]() serves only as a proxy to your services (inbound traffic), so it cannot affect any outbound traffic.
Thank you for clarifying that Metal Edge is not the cause.
However, my application logs consistently show that outbound DNS resolution from my container started failing around July 23rd with a NameResolutionError.
Since the cause is not Metal Edge, could you please help investigate what other part of the underlying network infrastructure could be causing this persistent outbound DNS failure? The problem is still blocking my service's core functionality. Thank y
9 days ago
Closing in favour of your latest thread, going forward, please do not create duplicate threads.