Subject: Urgent: Apex Domain yumrite.com Consistently Times Out (ERR_TIMED_OUT) Despite Correct Configuration
Dear Vercel Support Team,
I am writing to report a persistent and critical issue with my apex domain, https://yumrite.com, which is consistently resulting in an ERR_TIMED_OUT error for all users attempting to access it. This is occurring despite the Vercel dashboard indicating that the domain is “Configured Correctly” and set up to redirect to https://www.yumrite.com.
Notably, the www subdomain, https://www.yumrite.com, works perfectly fine and loads without any issues.
Here’s a summary of my configuration and the extensive troubleshooting steps I’ve undertaken:
- Vercel Configuration:
Project: [yumrite]
Apex Domain (yumrite.com): Shows as “Configured Correctly” in the Vercel dashboard. It is configured to perform a 307 redirect to www.yumrite.com.
Subdomain (www.yumrite.com): Shows as “Configured Correctly” and serves the Production environment.
2. DNS Configuration (Managed via cPanel - External DNS):
yumrite.com (Apex/Root):
Type: A
Name: yumrite.com. (or @)
Value/Record: 76.76.21.21 (as per Vercel’s instructions for apex domains)
TTL: 14400
Type: CNAME
Name: www.yumrite.com.
Value/Record: cname.vercel-dns.com
TTL: 14400
- Troubleshooting Performed & Findings:
DNS Propagation: Confirmed globally using tools like dnschecker.org. The A record for yumrite.com correctly and widely resolves to 76.76.21.21.
Local DNS Resolution: nslookup yumrite.com on affected devices (including my own) confirms that the domain resolves correctly to 76.76.21.21. The DNS server queried is typically the local router (e.g., 192.168.1.1), which then provides the correct Vercel IP.
Browser Testing: The ERR_TIMED_OUT for https://yumrite.com occurs consistently across:
Multiple browsers (Chrome, Firefox, Edge, Arc, etc.).
Incognito/Private browsing modes.
Newly downloaded browsers with fresh profiles.
Device Testing: The issue is present on multiple devices (desktops, mobile phones).
Network Testing:
The issue occurs on my local network.
Crucially, the issue is reproducible by multiple independent users on entirely different networks and ISPs when they attempt to access https://yumrite.com directly. This confirms it is not a localized issue with my setup.
Accessing https://yumrite.com via a VPN does allow the redirect to https://www.yumrite.com to occur successfully for me, suggesting the Vercel server at 76.76.21.21 can respond under certain network paths, but not for general public access.
Problem Summary:
Despite yumrite.com correctly resolving to Vercel’s IP (76.76.21.21) and Vercel’s dashboard indicating a correct redirect configuration, direct requests from various users and networks to https://yumrite.com are timing out before any redirect occurs. The www subdomain, which uses a CNAME, works flawlessly.
This leads me to suspect a potential issue with how Vercel’s infrastructure at 76.76.21.21 is handling incoming requests for the yumrite.com hostname, or an issue with the redirect mechanism itself for the apex domain at the edge, which is not apparent from the dashboard status.
Could you please investigate why requests to https://yumrite.com (which resolves to 76.76.21.21) are timing out for general public access?
Please let me know if you require any further information, logs, or specific tests from my end.
Thank you for your time and assistance in resolving this critical issue.
Sincerely,
[Your Name]
[collinsmecosy@gmail.com]
[collinsEzeokeke]