Hello Vercel team and community,
I have a production deployment issue where the Vercel deployment URL works correctly, but the custom domain does not deliver the HTML response body.
Project:
therapist-site
Working deployment:
https://therapist-site-q7gr.vercel.app/
Affected custom domains:
https://mariakuprina.ru/
https://www.mariakuprina.ru/
The same deployment works correctly through the vercel.app domain.
Issue
When accessing the custom domains, the server returns HTTP 200 with normal response headers, but the HTML response body is not delivered.
Example response:
HTTP/1.1 200 OKContent-Length: 43094Content-Type: text/html; charset=utf-8X-Nextjs-Prerender: 1X-Vercel-Cache: HITHowever, curl receives the response headers but the HTML body does not arrive.
Tests performed
- DNS resolution verified
- SSL certificate verified
- Custom domains removed and added again
- Cache bypass tested using: * Cache-Control: no-cache * Pragma: no-cache
- Query parameters tested
- Deployment works correctly through vercel.app
- Static files are delivered successfully:
https://www.mariakuprina.ru/favicon.ico
Additional observations
- The issue only occurs with custom domains.
- The deployment itself is healthy.
- Static assets are delivered.
- HTML responses appear to fail during delivery through the custom domain.
- The same application deployment works normally through the Vercel-provided domain.
This looks like a possible custom domain Edge routing or response delivery issue.
Could someone help investigate the custom domain routing or Edge response delivery for this project?
Thank you.
