Current behavior
I have a Vercel project where the deployment URL works correctly, but the custom domain does not fully load.
Affected custom domains:
Working deployment URL:
On the custom domain:
- browser shows net::ERR_CONNECTION_CLOSED
- HTML/CSS/JS do not finish loading
- the page becomes blank/gray
Expected behavior
The custom domain should fully load the same content as the working deployment URL.
Code, configuration, and steps to reproduce
Project:
- Next.js static site on Vercel
DNS:
- crm-ammoi.ru A → 76.76.21.21
- www.crm-ammoi.ru CNAME → cname.vercel-dns.com
Vercel dashboard shows:
- crm-ammoi.ru → Valid Configuration / Production
- www.crm-ammoi.ru → Valid Configuration / Production
What works:
- DNS resolves correctly
- TLS works
- HEAD requests succeed
- crm-ammoi.ru redirects to www.crm-ammoi.ru
- deployment URL works correctly
What fails:
- full body transfers on the custom domain stall or close
- browser shows net::ERR_CONNECTION_CLOSED
Important evidence:
- Range requests work
- Compressed responses work
- Full normal GET on the custom domain hangs
- The deployment URL for the same build works correctly
This suggests a custom-domain edge delivery / response streaming issue rather than DNS, TLS, or app code.
I can attach:
- vercel-debug.txt
- browser screenshot with ERR_CONNECTION_CLOSED
If needed, please escalate this to the infrastructure / edge team.