Vercel net::ERR_CERT_AUTHORITY_INVALID error on .vercel.app domains

I’m experiencing SSL certificate errors across all my Vercel projects that use .vercel.app domains. This started happening a few hours ago and affects:

  • Multiple projects (university-client-theta.vercel.app, university-server-fawn.vercel.app, and others)
  • Multiple devices (different laptops and PCs)
  • All browsers

Current Behavior

I see the following error:

Error: NET::ERR_CERT_AUTHORITY_INVALID - “Your connection is not private”

What I’ve Tried

  • Redeploying projects
  • Removing and re-adding domains
  • Testing on different devices and networks
  • Changing DNS servers
  • Flushing DNS cache

Additional Context

Workaround: Using VPN allows me to access the sites, but without VPN, all .vercel.app domains show SSL errors.

Expected behavior: Sites should load normally with valid SSL certificates like they did yesterday.

Is this a known issue? Are others experiencing this? Any ETA on a fix?

1 Like

All of the sudden, my Vercel projects is having a net::ERR_CERT_AUTHORITY_INVALID errors.

Error: net::ERR_CERT_AUTHORITY_INVALID

Can someone assist me on this issue? Thanks!

1 Like

Do you have a specific subdomain I can check?

1 Like

This is also happening to all my deployments on .vercel.app domains.

1 Like

Same issue with mine.

1 Like

same for me as well. churchservicemanagementui.vercel.app

I am having the same error as well. It just also restarted yesterday

Looks like it’s related to this?

UPDATE: Saw a related thread, I’ll merge this.

Your domains are working for me (I’m in the UK), I wonder if this is related to this incident. Where are you all trying to connect from?

1 Like

I think I figured out the problem. I’m based in the Philippines, and the government has recently been cracking down on some illegal gambling websites. It seems that Vercel domains may have been mistakenly flagged or affected by this block (not entirely sure, but that’s what it looks like).

What worked on my end was changing the DNS on my local machine to 8.8.8.8 (Google DNS), which fixed the issue. It also appears that some network providers here in the Philippines are not blocking Vercel domains, while others are. Related reddit thread (Reddit - The heart of the internet).

Would it be possible for Vercel to do something about this in case the domain was mistakenly flagged or affected by the block?

Thanks for sharing this, @stiffynavales!

I’ll share with our team internally to see what we can do. In the meantime, if everyone else could try what worked for @stiffynavales that’d be great:

1 Like