A small health-check application helps separate runtime problems from domain and proxy problems. This self-built Vibe Hosting teaching example provides a homepage, a JSON health endpoint and a deliberate 404 response.
Download and run
Download the Node.js example ZIP, extract it, and open a terminal in that directory. Use a currently supported Node.js LTS release compatible with your environment. No package installation or database is required.
node server.mjsThe example listens on 127.0.0.1:3187 by default. Open http://127.0.0.1:3187/health in a browser on the same machine. Expect HTTP 200 with JSON containing ok: true. The root path returns a short text response; an unknown path returns HTTP 404. Stop the example with Ctrl+C.
Verify one layer at a time
First verify the loopback endpoint. Then, for a production deployment, configure your chosen reverse proxy and HTTPS and repeat the request through the intended public hostname. The example binds to loopback deliberately; it is not an instruction to expose an unprotected application port to the internet.
- Local health fails: investigate the process, chosen port and startup error.
- Local health succeeds but the public request fails: inspect proxy destination, routing and TLS.
- Health succeeds but a business action fails: inspect the application's own dependencies and logs.
Know what the result proves
The health response proves this process can answer an HTTP request. It does not verify a database, a payment integration or resource capacity. An application-specific readiness check should exercise the dependencies needed for its real work without returning credentials or private data.
The archive includes an example-only usage note. Keep production process supervision and access configuration separate. For assistance, use the VPS deployment brief and state which of the local and public checks passed. This gives support a concrete starting point instead of a generic “site is down” report.