QuantumForgeAI Quick update: our protected deployment's route and lock checks now pass, and the temporary automation token was revoked with removal verified. We still need the configuration evidence before proceeding. What is the supported read-only way to verify the non-secret settings applied to a specific existing deployment, plus a complete credential-name inventory, without exposing secret values? The deployment-specific env pull returned HTTP 400. Current project settings do not establish that deployment's snapshot, and hidden or omitted Secret values do not establish absence. We also need to understan

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. 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.

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. 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.

Papyrustradedev 2448 Hi Vercel Community team, could a moderator please delete (or unlist) this topic? It contains our production domain and support case details, and we'd prefer it not to stay indexed in search results. We're handling the issue with AWS Support. Thanks!

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. 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.

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.

Cristovão A. da S. Neto We have already used vercel.com/abuse many times, and that is exactly why we are posting here. We ask that a member of the Vercel staff review the cases concerning berzerkclub[.]com[.]br and berzerkclub[.]com directly, or escalate them internally to Trust & Safety. Both domains serve the same deployment. Reports already filed through the official channel for this same deployment: Sep 28, 2026: phishing report for berzerkclub[.]com[.]br, case 01586466 Oct 2, 2026: phishing and brand impersonation report for berzerkclub[.]com[.]br, case 01597477 Oct 8, 2026: DMCA notice for berzerkclub[.]com[.]b

Amy Egan Hey Greg. The support team let me know they've been in contact through your support case. Please follow up with them if you have any more questions so they can help

Max I had a similar problem recently. Through Help / Vercel Agent, ask it to lift the suppression block on your email. It may have been suppressed because of an earlier email bounce. Most likely you've already solved the problem, but I'll leave this here in case others see it.

technaut Did you get any response to this? I have the same query/issue

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. 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.

Amy Egan If the Output doesn't have an index, that explains the 404. Now we need to figure out why the output doesn't match what you expected. Do you have a public repo or minimal reproducible example that you can share so we can help debug? Or a description of the project settings and framework used? The tips linked above can help if you prefer to DIY

Gokhandogan26 3070 Update: I tested both production and preview URLs on my iPhone. They fail on mobile data with ERR_CONNECTION_CLOSED, but the production URL opens successfully when I enable a VPN. Both URLs work on my PC and home Wi-Fi. Could you help investigate a possible ISP routing, DNS, IP filtering, or Vercel Edge connectivity issue? Production: godofi.vercel.app Preview: godofi-b19jcthll-go-do-fi.vercel.app

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. 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.

Rashidalyee 7215 A snapshot problem is unlikely. Vercel copies the env values into each deployment when it’s created, so a deployment made after your update has the new values. Redeploying with “Use existing Build Cache” unchecked fully rules this out. There’s no revision ID you can check, but you can compare fingerprints safely. Log crypto.createHash('sha256').update(id + ':' + secret).digest('hex').slice(0, 8) plus both lengths in the function, then run the same line locally. To tell a bad stored value from a runtime problem: run vercel env pull .env.prod --environment=production, then run your working Termi