#nextjs

Amy Egan I love seeing so many awesome things people have build with shadcn/ui! Thanks for sharing this dashboard toolkit

Vaibhav Gupta Glad to see you liked it!!

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.

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.