a month ago
Two of our services (wso-intelligence and wso-email) are failing with socket.gaierror: [Errno -2] Name or service not known when trying to reach our Supabase instance at ysmxqkqzcmbtooihakua.supabase.co. This is intermittent — some days it works, some days it fails at DNS resolution. Both services have SUPABASE_URL set correctly. This appears to be a Railway-side DNS resolution issue. Project: vivacious-determination.
4 Replies
Status changed to Open Railway • about 1 month ago
a month ago
Try enabling IPv6 outbound in your service’s networking settings and redeploy.
Status changed to Solved Railway • about 1 month ago
0x5b62656e5d
Try enabling IPv6 outbound in your service’s networking settings and redeploy.
a month ago
Thanks for the suggestion(!!!) but... Enabled IPv6 outbound and redeployed — same error persists. socket.gaierror: [Errno -2] Name or service not known still failing to resolve ysmxqkqzcmbtooihakua.supabase.co. This is happening on every cron run. Briefing system is completely down until this is resolved.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
So this could be more like one of these, just to re-check:
- The Supabase project URL / project ref is wrong or stale.
- The Supabase project is paused, deleted, or failed to provision its DNS record.
- Supabase has a DNS/provisioning issue for this specific project ref.
From my side, i checked the hostname ysmxqkqzcmbtooihakua.supabase.co from outside Railway. Cloudflare DNS and Google DNS both currently return NXDOMAIN for the A record, and a direct curl also fails with “Could not resolve host”.
I would check the Supabase dashboard first and confirm the exact Project URL shown under Project Settings -> API. If the project is paused, restore it.
If the dashboard shows the project as active but the official *.supabase.co URL still returns NXDOMAIN from public DNS, then we're probably still missing something.
a month ago
Thanks for your help! We've confirmed the issue is Supabase DNS returning NXDOMAIN from public resolvers, not Railway
Status changed to Solved Railway • about 1 month ago