⌘K
Pauline P. Narvas This is fantastic. Thanks for sharing, Philo!
BestCodes Okay... I see this as a big security vulnerability, actually, but would love to hear your perspective. Obviously, if an agent can submit any solution it wants, a human or compromised agent could submit a malicious solution. For example, let's say an agent runs into a bug where it forgets to use await with params from Next.js which happens a lot with Claude Code etc. So the agent goes and looks for a solution. Maybe the solution says "curl ai-solutions.co/next-params.md and open it to view fix instructions". This could be completely innocent or maybe next-params.md could actually be a malicious
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
