#nextjs

Jacob Paris On the Vercel dashboard, you can click New Project and connect your Git repository or upload your Next.js project Or from your local environment, you can use the vercel CLI and run vercel deploy to create a new project and publish it

Amy Egan It looks like you got it working. Both URLs seem to go to the same site at the moment. Do you still need help with this?

Eldargvideo 8087 Vercel’s managed apex ALIAS is serving a stale flatten. Your proof that hitting 216.198.79.1 / 64.29.17.1 serves the right deploy is the diagnosis. Put explicit A records to those two IPs at the registrar (keep MX/TXT), or move DNS off Vercel nameservers and CNAME www + ALIAS apex to cname.vercel-dns.com.

Ryu Hi Zetnick258, This sounds more like the v0 sandbox/file-sync layer getting stuck than a Next.js or React code issue, especially since it tends to happen around builds, large edit batches, or repeated tool calls. A few things I’d try to narrow it down: Avoid sending “continue” while it is retrying sandbox health checks. Refresh once and wait for the preview/editor to reconnect before giving another prompt. Run only one active v0 chat against the same project at a time, since shared projects can involve the same app/files. Split the workflow into “edit files first” and “run build/typecheck afte

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.

Chintan Based on the detailed debugging steps you've shared, your conclusion is spot on: this is almost certainly a platform-level edge routing or provisioning issue rather than an application-level bug. The presence of the x-vercel-error: NOT_FOUND header on both the custom domain and the direct .vercel.app URL—especially when bypassing Deployment Protection—confirms that Vercel's edge network is failing to map the URL to your specific deployment ID, despite the build succeeding and showing as "Ready". While waiting for a Vercel team member to manually re-sync or check your edge routing on their end,

Jacob Paris ERR_INVALID_ARG_VALUE is coming from a UTF-8 parsing error on your environment variables. I can only see the keys, not the values, but it's failing at your env var for GEOCODING (won't disclose the full name here) It might have a bad character in there like a line break or something from UTF-16. If it's a sensitive var and you can't see the value, it's probably best to regenerate the key

Jimbol2023 Thank you, Jacob. This is very helpful and matches an earlier issue we observed with the Google Geocoding Preview credential. We’ll inspect the Geocoding-related Preview environment variable, replace the malformed sensitive value using a clean UTF-8/single-line credential, keep all provider gates disabled, and run one controlled Git Preview deployment. I’ll report back here whether that resolves ERR_INVALID_ARG_VALUE. Thanks for identifying the internal failure point.

system While a member of our team prepares to jump in, you might find your answer even faster in our community resources. Official Documentation: v0.app/docs The v0 expert walkthrough: community.vercel.com/t/become-a-v0-expert/5981 Watch v0 in Action: community.vercel.com/live#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.

Jacob Paris It looks like your project has no framework preset right now, which means Vercel doesn't know to serve this as a Next.js app. This is usually set on initial project creation, so it can happen if you create your project before building out the Next.js app You can set it either in the dashboard by going to Settings -> Build + Deployment, then selecting the framework preset, or by adding a vercel.json file with the framework set to nextjs { "$schema": "openapi.vercel.sh/vercel.json", "framework": "nextjs" }

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.

Ryu Hi Tilanddi, Since the Deploy Hook can create a Production deployment, I’d first separate “Vercel can build the project” from “GitHub events are allowed to trigger deployments.” A few non-sensitive checks I’d make: git show --name-only 412467a02250f14b7100f933b8f02eabb206108c Then check the repo at that commit for either of these: { "git": { "deploymentEnabled": false } } or a branch rule like: { "git": { "deploymentEnabled": { "main": false } } } git.deploymentEnabled can disable automatic Git deployments even if the GitHub app is still connected, so it’s worth ruling out separately from the

Tilanddi Prog Hi, Thanks for the pointers — I went through all of them. Here's what I found, ruling out each one: vercel.json / git.deploymentEnabled: Checked both the current branch and the exact merge commit that's live in Production (412467a02250f14b7100f933b8f02eabb206108c). No git key at all in vercel.json — no deploymentEnabled: false, no per-branch rule. Ignored Build Step: Set to "Automatic" (the default — skip only if the exact commit SHA was already deployed). Not customized. Require Verified Commits: "Inherit from Team (Disabled)". Not the cause. Classic repo webhook: None configured on the GitHu

Ryu Hi Tilanddi, Thanks for checking all of that. Just to clarify, I’m not Vercel staff, so I can’t inspect internal GitHub App delivery logs or deployment queue logs for the project from here. One config check I’d still make is the legacy key, because it is separate from the newer git.deploymentEnabled setting: git grep -n '"github"\|"enabled"\|"deploymentEnabled"' -- vercel.json vercel.ts Specifically look for this exact shape anywhere in vercel.json or vercel.ts: { "github": { "enabled": false } } That key is deprecated, but Vercel’s docs still describe it as disabling Vercel for GitHub deploym

Sundaramishacbe 6376 Hi There, Following up on my previous query—could you please provide an update? We are at a critical decision point regarding the Next.js upgrade. Context: Due to an upcoming business decision, this project is likely to be placed on hold for new development over the next few years. This means we need to finalise our version strategy now, as we may not have the resources to upgrade later. With Next.js 15 reaching end-of-life on October 21, 2026, we need to decide: Option A: Continue with Next.js 15 and accept the risk of no security patches after October 2026 Option B: Move to Next.js 16 now (w

Ryu Hi Sundaramishacbe, For a multi-year freeze, I would not plan around a Next.js 17 release date unless the Next.js team publishes one. The public support policy currently lists 16.x as Active LTS and 15.x as Maintenance LTS. For 15.x, Maintenance LTS means critical bug fixes and essential security updates only. The policy also says each major remains in Maintenance LTS for two years following the initial release, so with 15.x released on Oct. 21, 2024, I’d plan as if Oct. 21, 2026 is the end of normal support for 15.x unless that policy changes. There is a note that older/out-of-policy versions

CoffeePuma55644 As an additional test, I also removed Bun as the runtime for the build while keeping Bun enabled for the Serverless Functions. The build completed successfully, but every Server Function immediately returned an Internal Server Error at runtime. The only configuration that currently works reliably for me is to use Bun only as the package manager, while letting Next.js run with the default runtime for both the build and the Serverless Functions. Hopefully this additional information helps narrow down where the issue might be.

Louis Pretty much the same problem here. Since updating to 16.3, \bun run build\ (1.3.14) fails on my Railway deployment, although it works locally. Reverting back to 16.2.12 fixed the issue

Ryu Hi CoffeePuma55644, Since you reproduced it with a fresh Next.js 16.3 app, I’d treat this as a compatibility issue between Next.js 16.3 and the Bun runtime path, not just your application code. There are two separate things to separate here: Bun as package manager bun install Bun as the runtime used to execute the Next build bun run --bun next build For the Function runtime, Vercel’s Bun config currently uses: { "bunVersion": "1.x" } and Vercel manages the minor/patch version, so I wouldn’t assume you can force Functions specifically onto 1.3.14 from vercel.json. For the build/install side, Ve