⌘K
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. https://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.
It 4491 Found it, thanks for the pointer. The issue was the Framework Preset in Project Settings → Build and Deployment — it was stuck on "Other" instead of "Next.js," because the project was first imported when the repo only had a README, before any Next.js code existed. That setting doesn't auto-correct once real code is pushed, so Vercel kept serving the app as a static/generic project instead of running Next.js routing — explaining the universal 404 across every URL type and the empty Logs tab. Fix: switch Framework Preset to Next.js, save, redeploy. Resolved immediately. Leaving this here in case others hit the same thing after importing a repo before its framework code was pushed.
Amy Egan Thanks for sharing the solution!
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. https://vercel.com/docs/domains/troubleshooting
Romatours Update: I found additional evidence that may help identify the cause. The official Roskomnadzor restriction-checking service returns: No results for my domain: xn----htbdko2afjj.xn--p1ai (тур-лидер.рф). A restriction record when searching for 216.198.79.1, the IP used by my apex A record. The displayed date is March 4, 2024. Both screenshots are attached. This suggests a possible shared-IP restriction, although it does not establish the exact cause of the connection failures. The issue now also affects home Wi-Fi, and using a VPN has not resolved it in my recent tests. The browser reports: net::ERR_CONNECTION_CLOSED 200 (OK) The same deployment works through tour-leader.online and tourleader.vercel.app. Both the apex and www versions of the .рф domain fail for me. Connecting www directly to Production instead of redirecting it to the apex did not help. I have now changed the apex A record from 216.198.79.1 to 76.76.21.21 as a temporary workaround. I am waiting for DNS propagation and have not yet confirmed whether this resolves the issue. Could the Vercel team please confirm: Is 76.76.21.21 still a supported address for this project? Is there another supported DNS target or routing option if this address is also unreachable? Can you investigate the connection failures affecting these custom domains? Project: tourleader Deployment domain: tourleader.vercel.app Thank you.
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. https://vercel.com/docs/domains/troubleshooting
jedgard70@gmail.com muito simples me mandar uma pagina que nao resolve nada sobre meu caso
Amy Egan Domains owned by your team through purchase or transfer can be seen on your team's Domains page. You should also have an email notification where you can review and approve the transfer. Please keep in mind that this is a public space. You should not share private account info, particularly for other people's accounts, in public threads. I've removed email addresses from your original post
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. https://vercel.com/docs/domains/troubleshooting
Newthiery 5459 Additional evidence: - The deployment works immediately when I use WARP/VPN. - The same issue occurs from both my PC and phone on the normal MTN Rwanda connection. - vercel.com itself is reachable from the same MTN connection. - Traceroutes to the affected Vercel edge IPs reach MTN/upstream network hops and then time out. - Direct HTTPS testing times out before TLS on the newer edge IPs. - The legacy Vercel IPs 76.76.21.21 and 66.33.60.130 successfully return HTTP 200 for the same deployment. This appears to be a network routing / Anycast / BGP / peering issue affecting connectivity from MTN Rwanda (AS36890) to Vercel's newer edge ranges. Could someone from Vercel Network/Infrastructure investigate the connectivity from AS36890 to 64.29.17.0/24 and 216.198.79.0/24? I can provide the full Vercel Network Debug output and traceroutes if required.
Mattoney93 7295 I’m seeing the same failure from T-Mobile 5G Business Internet in the United States. Affected deployment: https://five-circa-dashboard.vercel.app/ Evidence from the affected connection: - DNS resolves normally to Vercel edge addresses in 64.29.17.0/24 and 216.198.79.0/24. - TCP/443 fails before TLS. curl reports connection failure and the browser reports ERR_ADDRESS_UNREACHABLE. - ping and traceroute to 64.29.17.3 return ‘No route to host’ immediately. - An unrelated vercel.app deployment and vercel.com are also unreachable from the same connection. - Google and other non-Vercel destinations remain reachable. - The deployment loads immediately after switching the same Mac to a phone hotspot. This appears to be an outbound routing/peering issue between T-Mobile Business Internet and Vercel’s newer 64.29.17.0/24 and 216.198.79.0/24 edge ranges, rather than a deployment or DNS problem. Could Vercel Network/Infrastructure investigate and coordinate with T-Mobile? I can provide further traceroute or network-debug output if useful.
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. https://vercel.com/docs/domains/troubleshooting
Zedmode 5150 Update after approximately 24 hours: The issue still persists from the same remote monitoring environment. - https://kidzo.ru/ times out - https://kidzo.ru/catalog times out - No HTTP response is received - The Vercel domain configuration remains valid - No DNS, domain, deployment, or application changes have been made Could a Vercel team member please check the certificate and edge routing for kidzo.ru across regions?
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. https://vercel.com/docs/domains/troubleshooting
Wiseprinting I have also checked the DNS propagation using Google Public DNS (8.8.8.8). The _vercel TXT record for the apex domain is publicly resolving correctly, including the exact verification value provided by Vercel. The domain is still showing “Verification Required” and “linked to another Vercel account” in the Vercel dashboard. The previous Vercel account owner has confirmed that the domain was removed from their account. Could the Vercel team please check and release the remaining account association?
Wiseprinting anyone can help please?
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. https://vercel.com/docs/domains/troubleshooting
Rmjabor Thanks. I’ve already gone through the standard domain troubleshooting steps. This does not appear to be a DNS, ownership, SSL, or propagation issue. The inconsistency is internal to Vercel: - `vercel domains inspect` reports the domains on `cifrei-app`; - the project-domain API by project ID reports both domains attached and verified on `cifrei-dre`; - adding them to `cifrei-dre` returns `alias_conflict`; - removing them from `cifrei-app` says they are not assigned there. Vercel’s own diagnostic also indicated stale historical alias references on the production deployment target of `cifrei-app`. Could someone from Vercel please review/reconcile the internal alias/domain attachment state?
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. https://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.
Seongsu0306 1361 Additional diagnostic information: I tested the current Production deployment directly with authenticated `vercel curl`, which generated a Deployment Protection bypass token successfully. Current Production deployment: reveries-campaign-b4wkpa1e9-seongsu0306-1361s-projects.vercel.app `vercel ls` reports: Status: Ready Environment: Production `vercel inspect` reports: Deployment ID: dpl_BmybYWXNn3XrNYR9caS1zc6nHQaN Target: production Status: Ready Aliases: - campaign.reveries.kr - reveries-campaign.vercel.app - reveries-campaign-seongsu0306-1361s-projects.vercel.app However, authenticated: vercel curl https://reveries-campaign-b4wkpa1e9-seongsu0306-1361s-projects.vercel.app/ -I still returns: HTTP/1.1 404 Not Found X-Vercel-Error: NOT_FOUND The build logs also confirm that the application built successfully: - Next.js 16.3.4 compiled successfully - TypeScript completed successfully - `/` route exists - all application routes were generated - Build Completed in /vercel/output - Deploying outputs... - Deployment completed - final status: Ready So the generated Deployment URL itself returns a platform-level NOT_FOUND even though the deployment is Ready and the build output contains `/`. This now appears to be a deployment serving / edge routing registration issue rather than a DNS or application routing problem. Could a Vercel engineer inspect the deployment-to-edge routing registration for: Project: reveries-campaign Deployment: dpl_BmybYWXNn3XrNYR9caS1zc6nHQaN Domain: campaign.reveries.kr
Amy Egan It looks like it's working now. Are you still having trouble with your domain?
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. https://vercel.com/docs/domains/troubleshooting
Yuvraj2002 Yuvi I have already checked the DNS configuration. The apex domain uses: A @ → 216.198.79.1 The www domain uses: CNAME www → 779e5f4c88a8acd0.vercel-dns-017.com www.legaldocsmaker.in has a valid SSL certificate, but the apex legaldocsmaker.in remains stuck on "Generating SSL Certificate". Google Search Console reports "Invalid server SSL certificate". Could you please check the SSL provisioning for the apex domain?
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. https://vercel.com/docs/domains/troubleshooting
Jjuunnii98 4598 I also tried the account recovery form but it errors out repeatedly — is there another way to reach a human?
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. https://vercel.com/docs/domains/troubleshooting
Ryan Owens The Vercel Agent suggested I post here for resolution
Ryan Owens after looking at some other posts, it looks like other folks have had similar issues stemming from the deletion of an account (which is my situation as well) - I deleted a pro account that the domain must have been linked to that didn't transfer when i transferred the project. Here is some info about the domain: Paid January 16, 2026 Receipt number 2718-4286 Invoice number E90A26EE-0069
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. https://vercel.com/docs/domains/troubleshooting
Lauraborgenicht Dotcom @moderators Could you please delete this entire topic? It's my own post but it publicly ties my production domain to SSL details I'd rather not have indexed, and I'm past the window to edit or delete it myself. Much appreciated.
