This morning I started running into an issue with accessing my dashboard on Vercel.
I’m even unable to load the Vercel.com main website and I am just greeted with a blank screen.
I can initially see some of the header components of the website loading, like the skeleton, but then that goes away after half a second or something.
This issue extends to other Vercel hosted sites like Cursor.com and openrouter, I can however access my own vercel hosted application directly. When I run firefox in troubleshoot mode it does work.
Seeing these errors on the console:
SES_UNCAUGHT_EXCEPTION: Error: Connection closed.
t NextJS
lockdown-install.js:1:135422
<anonymous> moz-extension://5157804c-30f0-4aa5-9e1d-2fb836742a78/scripts/lockdown-install.js:1
NextJS 12
c
a7
callback
rF
rD
ot
u3
u0
uU
uI
sy
S
Uncaught (in promise) Error: Connection closed.
t NextJS
73110-198076db0893b09b.js:3:55146
Also seeing a bunch of these messages:
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self' 'unsafe-eval' 'unsafe-inline' https://www.google.com https://www.google-analytics.com https://www.googleadservices.com https://www.gstatic.com https://*.youtube.com https://*.youtube-nocookie.com https://*.ytimg.com https://*.twimg.com https://cdn.ampproject.org https://www.googletagmanager.com https://*.googleapis.com https://*.heapanalytics.com https://heapanalytics.com https://*.fides-cdn.ethyca.com https://*.ethyca.com https://cdn.ethyca.com https://cdn.vercel-insights.com https://va.vercel-scripts.com https://vercel.com https://*.vercel.com https://*.vercel.sh https://vercel.live https://*.stripe.com https://twitter.com https://*.twitter.com https://*.github.com https://*.codesandbox.io https://risk.clearbit.com wss://*.vercel.com https://localhost:* chrome-extension://* 'nonce-bW96LWV4dGVuc2lvbjovLzUxNTc4MDRjLTMwZjAtNGFhNS05ZTFkLTJmYjgzNjc0MmE3OC8='” preload.js:139:16
I’ve tried using NordVPN to connect to different proxies but it’s still not working with my Firefox.
Using FF version: 136.0.2
And like I said, it’s working fine in Safari, as well as FF in troubleshoot mode.