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 Solomon, The Functions tab only showing /api/auth/[...nextauth] is not necessarily a problem by itself. Static App Router pages will not always show up there as functions. The more important signal is the exact 404 type and which URL is returning it. I’d separate three cases: Can you test the unique deployment URL from the deployment details page, not just the project alias? If the unique deployment URL works but study-hub-phi-sand.vercel.app returns DEPLOYMENT_NOT_FOUND, that points to an alias/routing association issue. If the unique deployment URL also returns Vercel’s platform DEPLOYMEN
Codex 5427 Yeah I know
ADALIGO 😄 Haha... imagine creating a brand new account just to write: "Yeah I know." But anyway... let me tell you something maybe you don't know yet: Even if someone knows a lot, nobody knows everything. Real builders stay humble. Real engineers keep learning. 🚀 Knowledge is not about acting bigger than others. It's about helping, encouraging, building, and evolving together. So whether you're senior, junior, beginner, or expert: keep learning 📚 keep building ⚡ keep improving 🧠 Because technology moves fast... and the moment someone thinks they know everything, they already stopped growing. Still bui
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. vercel.com/docs/projects/domains/troubleshooting You can also use v0 to narrow down the possibilities.
Ryu Hi Hero, I’d first separate “Safari is slow to get the document” from “Safari gets the document quickly but renders a blank page for a while.” A quick way to check is to run this in Safari’s console after a slow load, then compare it with Chrome on the same iPhone: If dns, connect, tls, or ttfb is much higher only in Safari, I’d test Safari with iCloud Private Relay/content blockers disabled, and compare Wi-Fi vs mobile data. I’d also compare the custom domain against the *.vercel.app URL. If the Vercel URL is fast but the custom domain is slow, then I’d look at DNS, SSL, or anything proxying
Tianen Pang check this one github.com/vercel/next.js/issues/89764#issuecomment-3928272828 for temp fix
ADALIGO The error comes from tooling mismatch not from you Luknuts56, just downgrade ESLint and you’re good 👍
Ryu Hi Luknuts56, This one looks like a tooling-version mismatch, not a problem with your loading.tsx file. Your package.json has: and the stack trace is failing inside eslint-plugin-react while loading the react/display-name rule. There’s an open Next.js issue for this same ESLint 10 error: github.com/vercel/next.js/issues/89764 For now I’d pin ESLint back to v9 instead of using ESLint 10: If it still keeps ESLint 10 because of the lockfile, do a clean install: One more thing: since you’re following a course, I’d avoid using "latest" for next, react, and react-dom. The tutorial may have been writ
Pauline P. Narvas Thank you for your contribution, Michele! Welcome to the Vercel Community 🙂 I've passed this onto the CICD team to review!
Michele Bertoli Gentle nudge on this one It's a 2-line change that brings @vercel/react-router in line with how Next.js, SvelteKit, and Qwik already set __vdpl and it unblocks Skew Protection for deep URLs Happy to add a changeset or any tweaks that'd help, just let me know