Custom domain returns 401 despite project visibility set to Public

Support
1

My site returns a 401 Unauthorized error when accessed via my custom domain, even though I’ve set both:

  • The project’s “Project visibility” (Access & security) to “Public”
  • My team’s default visibility to “Public” as well

DNS is correctly configured (A record to 75.2.60.5 for the apex domain, CNAME for www pointing to the Netlify subdomain), and the domain shows as verified in Domain management. The latest deploy shows status “Published”.

The site was working correctly under the custom domain a few days ago. The 401 started appearing after I made some project visibility changes while troubleshooting an unrelated issue, and toggling it back to “Public” hasn’t resolved it.

Could someone check if there’s another access restriction on my account/team I might be missing? I’m happy to share the site name/ID privately if needed.

Thanks in advance!

2

I’m hitting this exact same issue — wanted to add my case since the original report never got a response.

Site: salinelocal.com (Netlify project name shiny-sundae-68fd35)

Anonymous/public requests to the custom domain return 401 Unauthorized on every page (homepage and inner pages), while shiny-sundae-68fd35.netlify.app for the same deploy loads fine publicly. So the deploy itself is healthy — this looks scoped specifically to the custom domain.

What I’ve already ruled out:

  • Project visibility set to Public for both Production and Deploy Preview
  • salinelocal.com confirmed as the Primary domain, with a valid SSL cert covering both salinelocal.com and www.salinelocal.com
  • Triggered a fresh deploy (including a full clear-cache rebuild) — no change
  • Firewall Traffic Rules set to “Allow all traffic,” no geo/IP restrictions, for both Published and Unpublished deploys
  • Web Application Firewall confirmed Disabled
  • No OAuth providers installed on the project
  • DNS confirmed correct: apex A record → 75.2.60.5 (Netlify’s IP), www A record also → 75.2.60.5

Everything on my end points to a platform-side issue with how the custom domain is being served versus the .netlify.app subdomain, not a config problem in my project. Would appreciate a look from the Netlify team — happy to share the site/project details privately if that helps investigate.