I cannot access ANY website hosted in Vercel, except Vercel itself

Help
1

I cannot access any websites hosted in Vercel from my PC. I’ve tried all the tests that I can come up with. I’ve combined VPN, different browsers (webkit, chromium, firefox, etc.)… I thought maybe my ISP was banned, but no, it works just fine in my other devices. Not my IP, because VPN doesn’t do the trick. Also, my Mac works just fine.

The websites load all blank. No errors, no network calls. Nothing.

Weirdest part, if I ping the IP it’s all good, and if I go to vercel.com itself, it’s working just fine. But, if I go to cursor.com for example, which is hosted in Vercel, it won’t work. Neither will any other. If I ping the domain directly, it works aswell.

My guess is I’m blocked on a hardware level by Vercel’s CDN service for whatever reason? I do zero weird activity on this computer, so I would be surprised. But I really can’t think of anything else now.

Anyway, I have a bunch of websites hosted in Vercel and I cannot test production lmao, anyone has had this issue before? I cannot find a lot about it online.

I also tried turning my firewall off, didn’t work either.

Network response with SSR website is blank.

image
image2077×1267 17.6 KB

image
image1142×1251 22.8 KB

2

Hi @beatlz-too, welcome to the Vercel Community!

Sorry that you’re facing this issue. Can you try opening: https://www.theanshuman.dev/ or https://anshuman-can-ship.vercel.app/ to see if it persists here?

Also, please share what the network request headers look like. And the browser console.

1 Like
3

Hello and thanks for the quick response.

https://www.theanshuman.dev/ ==> works
https://anshuman-can-ship.vercel.app/ ==> fails

Headers as cURL

curl ^"https://anshuman-can-ship.vercel.app/^" ^
  -H ^"accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8^" ^
  -H ^"accept-language: en-US,en;q=0.8^" ^
  -H ^"cache-control: max-age=0^" ^
  -H ^"priority: u=0, i^" ^
  -H ^"referer: https://vercel.community/^" ^
  -H ^"sec-ch-ua: ^\^"Not(A:Brand^\^";v=^\^"99^\^", ^\^"Brave^\^";v=^\^"133^\^", ^\^"Chromium^\^";v=^\^"133^\^"^" ^
  -H ^"sec-ch-ua-mobile: ?0^" ^
  -H ^"sec-ch-ua-platform: ^\^"Windows^\^"^" ^
  -H ^"sec-fetch-dest: document^" ^
  -H ^"sec-fetch-mode: navigate^" ^
  -H ^"sec-fetch-site: cross-site^" ^
  -H ^"sec-fetch-user: ?1^" ^
  -H ^"sec-gpc: 1^" ^
  -H ^"upgrade-insecure-requests: 1^" ^
  -H ^"user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36^"
1 Like
4

I’m not the only one with this issue apparently. I think it’s not common, but must be a pattern.

5

Could you go through this post? It may be related!

1 Like
6

Nope, this isn’t working. I had already tried different VPNs. I think it’s at OS level.

7

Extra findings:

All browsers are failing. If I go to the networks tab, there’s not even a content fetch. However, if I call websites from postman, I get the normal response.

So it’s only failing on browsers.

8

What DNS provider are you using on the device where this fails? Strange that it still fails in a VPN…

9

I tried both Google’s and Cloudflare’s. But still, wouldn’t this affect the Postman call if it was because of DNS?

When I fetch the content using postman, it works. It seems to be browser-only.

1 Like
10

That’s very strange. I’d think it’s more likely for Vercel to block a request from Postman than from a browser…

11

Just to be clear, this isn’t IP related, I’m 100% now : )

1 Like
12

The thing is, I don’t get blocked. Or at least it doesn’t seem like I am. But the response’s body is empty. just get headers.

access-control-allow-origin:

*

age:

65914

cache-control:

no-cache, no-store, must-revalidate

content-disposition:

inline

content-encoding:

br

content-length:

1

content-type:

text/html; charset=utf-8

date:

Sat, 08 Mar 2025 16:11:44 GMT

etag:

W/"674fe66552b985d0f05ad4ca9b82539f"

expires:

0

pragma:

no-cache

server:

Vercel

strict-transport-security:

max-age=63072000

vary:

RSC, Next-Router-State-Tree, Next-Router-Prefetch, Next-Router-Segment-Prefetch

x-frame-options:

SAMEORIGIN

x-matched-path:

/research/crossing_the_uncanny_valley_of_voice

x-vercel-cache:

HIT

x-vercel-id:

cdg1::fnjrk-1741450304006-8dbaefd66818
1 Like
13

New fun update. I installed wsl and ran a chromium instance in wsl. I’m able to run vercel sites here. It’s only on Windows that’s not letting me.

14

Here I’m running everything in the same variables, except for the OS. The right is an Ubuntu distro using WSL, while the left is just windows. So I think it’s gotta do with Windows (as usual…)

image
image1920×768 61.8 KB

1 Like
15

Hi @beatlz-too, thanks for sharing your findings here.

2 Likes
16

No problem, I wish I had a solution too.

I tried making a new session for Windows, all blank. Vercel sites work there. So it’s not the OS.

So far I can rule out:

  • OS
  • Specific browser (tried all)
  • DNS (I flushed and changed to Google’s and Cloudflare’s, same result)
  • Firewall (I turned it off, no luck)
  • IP (tried VPN)
  • My session being banned (If I request the site on postman or even on a fetch() function, I get the proper response)

I’m just stunned, I don’t know what else to try.

Any ideas are welcome @anshumanb

17

I finally solved it. There was something corrupt affecting my session.

I ran sfc /scannow as admin and it did the trick. I have no clue why, but something there was messing with the specific combination of using any browser on this Windows session.

3 Likes
18

Thank you for sharing what worked for you! :smiley:

1 Like
19

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.