Production Domain Down (ERR_CONNECTION_REFUSED) - adawatai.dev - Help

My production site, www.adawatai.dev, is showing an ERR_CONNECTION_REFUSED error and is completely down.

The site works perfectly on the Vercel deployment URL.
The issue is ONLY on the custom domain (www.adawatai.dev).
My Vercel dashboard shows a "Valid Configuration" for the domain with green/blue checkmarks after I updated my nameservers.
I have already tried all standard troubleshooting: redeploying, clearing browser cache, flushing my system's DNS, and testing on completely different networks and devices (including mobile 4G/5G). The problem persists everywhere.

Since all configurations appear correct on my end and the issue is specific to the custom domain routing across all networks, this strongly suggests a server-side or network-level issue on Vercel's end.

Could anyone from the Vercel team please investigate the routing for this domain? This is a production site and it's currently inaccessible to all users.

Thank you,

Hi, ! Welcome to the Vercel Community

I can see that your site is working now.

What did you end up doing to make it to work?

Hi Pauline,

Thank you for reaching out! Yes, the site is working now.

The issue was a complex DNS configuration problem. The Vercel dashboard was showing "Invalid Configuration" for my domain. Here are the exact steps I took to solve it:

Diagnosis: I confirmed the site was working on the .vercel.app URL but not on the custom domain, which isolated the problem to DNS.
The Fix: I logged into my domain registrar (Namecheap) and changed the nameservers from the default ones to Vercel's nameservers (ns1.vercel-dns.com and ns2.vercel-dns.com).
Propagation: After making the change, it took several hours for the DNS changes to propagate globally. During this time, the Invalid Configuration error remained in the Vercel dashboard.
Confirmation: Eventually, the configuration in the Vercel dashboard turned to "Valid," and after clearing my local DNS cache, the site started working everywhere.

The key solution was switching to Vercel's nameservers instead of using A/CNAME records. I hope this information helps others who might face the same issue.

Thanks again for your help!

This is super helpful! Thank you,