Supabase project hostname returns NXDOMAIN

[praiseosazee2013-ctrl]

Hi Supabase community!

I'm building a GCSE revision website called FuturePath using GitHub Pages and Supabase.

My project reference is yhtulfticjdfnmtgsex, in the West EU (Ireland) region.

The hostname yhtulfticjdfnmtgsex.supabase.co returns NXDOMAIN when I run nslookup using both Virgin Media DNS and Google DNS (8.8.8.8). The main supabase.co domain resolves normally.

My website's sign-up request fails with net::ERR_NAME_NOT_RESOLVED. I've checked that the project ID matches my dashboard and corrected the base URL in config.js.

Could someone help me check why my project hostname isn't resolving?

Thank you!

[aashish254]

nxdomain on the project subdomain while supabase.co resolves means dns has no record for that hostname. supabase only creates that record for a real project ref, so the ref in your config.js is almost certainly wrong.

the giveaway is the length. a valid supabase project ref is exactly 20 lowercase characters, and yours is 19. looks like one character got dropped when you copied it.

open dashboard → project settings → api and copy the project url from there, then compare it character by character with what is in config.js. paste the full url instead of typing the ref by hand.

if the dashboard url still does not resolve after fixing that, the project itself may be paused or deleted, which also removes the hostname. but with a 19 character ref, the typo is the far more likely cause.

[ganiya-sudo]

An NXDOMAIN and ERR_NAME_NOT_RESOLVED error on your project endpoint means the internet's Domain Name System (DNS) cannot map your unique project ID to a live server routing path.

To resolve this infrastructure block, please run through these quick checks:

1. Verify Project Status (Wake/Resume): Log into your main Supabase Dashboard. Check if your project instance (yhtulfticjdfnmtgsex) has been automatically paused due to inactivity. If it is paused, simply click the "Restore Project" button. This will spin the engine back up and broadcast your hostname to global DNS servers within a few minutes.

2. Execute an Infrastructure Toggle: If the dashboard states the project is actively running, the routing layer may be out of sync. Navigate to your project Settings ➡️ General, and perform a brief Pause and Resume cycle. This would configure the network and force the backend cluster to re-register your domain.

3. Database State Audit: If the issue persists after a toggle, this is the part where you might provide your project's registration email to the Supabase team, so they can audit the regional West EU (Ireland) hosting infrastructure logs to ensure your cluster container didn't hit a provisioning stasis.

Hope this helps