Problem
When vix health public fails or points to the wrong server, the output does not provide enough information to quickly understand the issue.
For example, if the domain resolves to Vercel instead of the expected VPS, Vix should make that visible immediately.
Expected behavior
vix health public should display DNS and server information.
Example output:
resolved IP : 64.29.17.65
server : Vercel
expected IP : 62.171.131.80
This would make it easier to detect:
- wrong DNS records
- domain still pointing to another provider
- proxy misconfiguration
- CDN or hosting mismatch
- public health check hitting the wrong machine
What to add
vix health public should show:
- resolved IP address for the public domain
- expected IP address if configured or detected from production doctor
- HTTP
Server header if available
- maybe the final URL being checked
Goal
Make public health debugging faster by showing where the request is actually going.
Problem
When
vix health publicfails or points to the wrong server, the output does not provide enough information to quickly understand the issue.For example, if the domain resolves to Vercel instead of the expected VPS, Vix should make that visible immediately.
Expected behavior
vix health publicshould display DNS and server information.Example output:
This would make it easier to detect:
What to add
vix health publicshould show:Serverheader if availableGoal
Make public health debugging faster by showing where the request is actually going.