Vercel 403 error Issue on preview

Help
1

image
image1557Ă—666 57.4 KB

I am facing this issue on Preview dashboard , even when eveything is working fine on production or custom domains but preview domains are not working which leads to 403 error , Tried everything which available on forums or discussions

2

same issue here

3

same issue! no answer yet from vercel

4

Same, not sure what happened but even after adding OpenGraph metadata, it’s still throwing the error. Same on the deployment screen.

5

Hello,

I am experiencing the same issue shown in the screenshot.

In the Vercel dashboard, the deployment preview screenshot appears blank or shows a 403 Forbidden error. However, the website works correctly on the production domain and custom domain.

Project: events-banquet-hall
Account: ErnestoLlanes’ projects
Plan: Hobby
Production domain: https://eventsbanquethall.com

Example deployment URL:

Screenshot 2026-05-08 064225
Screenshot 2026-05-08 0642252871Ă—891 147 KB

The build completes successfully and the deployment status is Ready. The website loads correctly in production, but the dashboard preview screenshot is not generated correctly.

I checked Deployment Protection. I previously had Vercel Authentication enabled, but I disabled it and redeployed without using the build cache. After disabling it, the deployment URL appears to be publicly accessible and returns 200 OK, but the preview screenshot in the dashboard still shows the old 403 Forbidden / Authentication Required state, as if the thumbnail is cached.

I have already tried the solutions available in forums and discussions, including:

  • Disabling Vercel Authentication
  • Redeploying without build cache
  • Confirming the custom production domain loads correctly
  • Confirming the deployment URL is accessible
  • Verifying the build has no errors
  • Reviewing the Next.js middleware/proxy configuration

Could you please check whether the dashboard thumbnail / preview screenshot is cached, or whether there is an issue with the automatic screenshot generation for my project?

Thank you.

6

me too!

I even deleted my account and recreated it, but the problem still exists for me.

I currently only have one deployment, which is empty, but I still get a 403 error when it should be a 404.

7

what the FUCK is this shit?? i can’t use my fucking website because of this retarded bug that vercel refuses to fucking address. FUCK this company

8

Hi Divyanshu,

Since the production/custom domain works but the Vercel preview/deployment URL shows 403: Forbidden, this may not be a build problem. It looks more like the request to the *.vercel.app deployment URL is being blocked before or at the edge.

A few things I would check:

  1. Go to Project Settings → Deployment Protection and confirm whether Vercel Authentication, Password Protection, or any protection setting is enabled for preview/deployment URLs.

  2. Check Project Settings → Firewall and the Firewall/Observability logs around the time you opened the preview URL. A Vercel 403 can happen if a firewall rule or mitigation blocks the request before it reaches the app.

  3. Check whether your app code blocks unknown hosts. Since your custom domain works but the *.vercel.app URL does not, middleware or host-based logic may be allowing www.bappaartstudio.com but rejecting the deployment domain.

  4. Test the deployment URL directly in an incognito window, not only from the dashboard preview screenshot.

  5. If the actual site works but only the dashboard thumbnail shows 403, mention that clearly, because that may be Vercel’s screenshot/preview bot being blocked rather than users being blocked.

The most useful next detail would be whether the 403 happens when opening the *.vercel.app URL directly, or only inside the Vercel dashboard preview thumbnail.

9

I noticed that this happens when I activate the “Protection Bot”

10

This issue should be resolved now. Are you still facing this?