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/domains/troubleshooting
Galz Update: with Logs in Live mode (no filters except path /), pressing "Scrape Again" in Meta's Sharing Debugger produces no request at all in my project's logs, while the debugger reports 403. Other visitors and crawlers show up normally with 200. My project firewall shows facebookexternalhit as allowed via a Bypass rule, Bot Protection is off, and there are no persistent actions. So Meta's crawler is being blocked at Vercel's edge before reaching the project. Can someone check the platform-level mitigation for www.offband.pro?
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/domains/troubleshooting
Matej Rancigaj I tried but I couldn't resolve it yet.
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/domains/troubleshooting
Grumpyice Hi Vercel team, just following up on this issue. I’m still unable to verify ijedelcda.lg.gov.ng, and Vercel continues to show “This domain is linked to another Vercel account.” The requested TXT verification record has already been added to the domain’s DNS through Go54, but the status remains Verification Required. Could someone please advise whether the domain association needs to be released or verified on Vercel’s side? I’d appreciate any guidance. 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. vercel.com/docs/domains/troubleshooting
Hali Is anyone there
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/domains/troubleshooting
Zsofia Matrai I need to talk to a human please. I don't understand this.
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/domains/troubleshooting
Amy Egan If your domain is eligible, you can renew it by following these steps: vercel.com/docs/domains/working-with-domains/renew-a-domain#manual-renewal Keep in mind that third party domains can only be renewed through their current registrar.
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/domains/troubleshooting
Oyaminstitute 8152 It needs vercel 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. 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
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/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. 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 (AS368
Mattoney93 7295 I’m seeing the same failure from T-Mobile 5G Business Internet in the United States. Affected deployment: 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. Th
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/domains/troubleshooting
Zedmode 5150 Update after approximately 24 hours: The issue still persists from the same remote monitoring environment. kidzo.ru times out 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. 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. 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
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.
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 reve
Amy Egan It looks like it's working now. Are you still having trouble with your domain?
Ryu Hi Mohsin, Good catch. That definitely looks like a diagnostics/UI bug rather than an actionable domain error. If the real issue was DNS misconfiguration, then showing a value like: is pretty misleading, because it sends people toward their app/runtime stack instead of the actual domain/certificate checks. For anyone else landing here, I would not treat that kind of string as the cause of the cert failure. I’d still debug the domain normally: live A/CNAME, no conflicting AAAA, CAA records, and whether the HTTP validation path can reach Vercel cleanly. The useful bug report details here are pro
Mhslr This just happened to me. I removed and added back the domain to fix it.