⌘K
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Debugmyai 1042 That error on the domain while the deployment URL works almost always means the alias points somewhere other than your current deployment, not that the build is broken. Three things to check: 1. In Settings → Domains, click Edit on ba4varov-weather.vercel.app. If a Git branch is filled in (even "main" with a typo or an old branch), clear it so it follows Production. A domain tied to a branch with no live deployment gives exactly this 404. 2. Check whether another project in your account (an older "weather" project, for example) also lists this domain. Remove it there. 3. Force a fresh alias from the CLI: `vercel alias set <your-working-deployment-url> ba4varov-weather.vercel.app`, then run `vercel alias ls` to confirm it points at the right deployment. If none of that sticks, removing the domain from the project and adding it back usually clears a stale alias.
Amy Egan Are you sure that's the correct subdomain? I also wasn't able to find any record of that domain in use for any current project. Make sure you have an existing project with a production deployment. The deployment info includes a link to the production domain, so you can use that to rule out any typo that would cause a "deployment not found" error.
Mykepanama 5445 Hello, I’m experiencing a similar 403 error with the ChatGPT Vercel connector. My project is heartgate-private-beta, under team mykepanama-5445. I can access it in the Vercel dashboard, but requests through ChatGPT targeting this team fail with: “Not authorized: Trying to access resource under scope ‘mykepanama-5445’. You must re-authenticate to this scope or use a token with access to this scope.” I have reconnected several times, deleted all active ChatGPT tokens in Vercel, and removed and reinstalled the connector. The error persists. In my case, reconnecting returns me directly to ChatGPT without showing a consent screen or team selection. Request ID: fra1:sfo1::288s4-1792596156063-a58f043c30ed Could your team investigate? The recommended reconnection and token deletion steps have already been tried without success.
joshsoup investigating now. in the meantime could you try revoking and then granting access to the selected team and see if that works?
Ciadamodavrb 4295 Update on 20 Oct 2026: the same DETRAN-ES phishing is still being deployed on vercel.app, now with new project names. Seen today (the names are in code format on purpose, the pages are live): - `cfcconde.vercel.app` : a driving-school facade whose first lines run location.href to the next one. - `portais-onlines-veiculares-esp.vercel.app` : the fake "Servicos DETRAN-ES Veiculos" page with a plate + Renavam form. Reported on 19 Oct, still online. Its response headers include X-Render-Origin-Server: Render. - `autoescolaauecfc.vercel.app` : a 233-byte page that is only a script redirecting to a gate on another domain. Reports so far: the public abuse form (TNS_01CpK5ull2PyvRp9 on 19 Oct and a new one today) and Pro support cases CSE_01zLc3pGwxWAVDes (closed on 19 Oct with a message that the details were handed to the abuse team) and CSE_01LwnZVYhe3Xxpum (open today). The operator recreates the same pair of projects every few days, so each takedown lasts only until the next deploy. Could someone from Trust & Safety suspend the accounts behind these projects, not only the deployments? Thank you.
Amy Egan I'm checking with the abuse investigation team now. Thanks for sharing the case numbers
system Thank you for bringing this to our attention. To ensure this is investigated with the necessary priority and privacy, please report all security-related concerns, potential exploits, or abuse directly to the Vercel Security Team. Please submit your report here: vercel.com/abuse Reporting via this official channel is the fastest way to reach our security engineers and ensures that sensitive information is handled in a secure environment rather than a public forum.
Brian 7926 Thank you for the response. To clarify, I'm not reporting a vulnerability, exploit, abuse incident, or security concern involving an existing Vercel deployment. This is a technical architecture and platform-capability question about whether Vercel supports independently verifiable Function artifact attestation beyond the identity claims available through OIDC Federation. Vercel Support specifically directed me to the Community for this type of architectural inquiry. Could a Vercel engineer or knowledgeable community member clarify whether this capability is supported, unsupported, or requires an alternative architecture? Documentation or technical guidance would be greatly appreciated. Thank you!
Debugmyai 1042 Since your custom bypass rule didn't change anything, the managed rule seems to be inspecting the binary body no matter what. Two things worth trying: 1. Keep the PDF out of your function entirely. Upload it straight from the browser to storage (Vercel Blob client uploads with `upload()` from `@vercel/blob/client` plus a small `handleUpload` route, or a presigned S3/R2 URL), then send your API only the file URL. This also gets you around the 4.5 MB request body limit on Vercel Functions, which bigger past papers would hit anyway. 2. If the file has to go through your API, test sending it as `multipart/form-data` instead of a raw binary body and see if the block still happens. Either way, post the `x-vercel-id` value from one of the blocked 403 responses here so Vercel can look up exactly which rule fired for that path.
Iamcaleb3rw @debugmyai-1042 The first recommendation of uploading straight from a broswer with a presigned url worked perfectly. Thank you
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/domains/troubleshooting
Sushikakilima 3388 Same issue on my domain kaiten.ai.id. Domain kaiten.ai.id (project kaiten-ai-id, account sushikakilima-3388, Hobby) is stuck unverified: the dashboard asks for a TXT record at _vercel.ai.id, which is impossible — ai.id is a public suffix and I only control the kaiten.ai.id zone. I have placed the verification TXT records at _vercel.kaiten.ai.id and they resolve publicly: - vc-domain-verify=kaiten.ai.id,58f9110a142e49354df8 - vc-domain-verify=www.kaiten.ai.id,eb44db99c8750ef5d0c4 DNS (Cloudflare zone kaiten.ai.id): A @ -> 76.76.21.21 (DNS only), CNAME www -> cname.vercel-dns.com (DNS only), nameservers jarred.ns.cloudflare.com and sara.ns.cloudflare.com. The records have been in place since 20 Oct 2026 evening (WIB) and the domain still shows verified: false — HTTPS connections are closed with no response (no certificate issued) and HTTP returns 404 DEPLOYMENT_NOT_FOUND. Per publicsuffix/list PR #2922, ai.id is in the PSL ICANN section, so kaiten.ai.id should be treated as a registrable domain. I tried opening a support case first, but the case form blocks Hobby accounts for the Domains topic and directs me here. Please refresh the PSL snapshot used by domain parsing, or manually verify ownership. Thank you.
