OffVPSOFFSHORE VPSSupport

First VPS manual

Where to look when an app is unreachable

Trace DNS, TLS, proxy and process in observable order.

manual reference · Reviewed · 2 min read

Use this reference with the current value

Start from the value shown by OffVPS or the observation from your own server. Do not substitute a remembered default.

Capture the exact failure

Record hostname, timestamp, client network and the browser, TLS or HTTP error. Keep the last known-good release and recent changes.

Scroll horizontally to read every column on a small screen.

Layer-by-layer triage
LayerObservable checkWhat a failure narrows
DNSResolve the exact hostname from a representative clientWrong or stale address
TLSInspect certificate name, validity and handshake resultListener or certificate handling
Public listenerCheck whether the expected port accepts a connectionNetwork exposure or service listener
Reverse proxyInspect request-time proxy log and upstream statusRouting or upstream connection
ApplicationMake the same request locally and inspect service status/logsProcess, dependency or application error
Data dependencyCheck database or queue from the application pathDownstream failure

Change one layer

If local application response works but the proxy reports an upstream error, inspect proxy destination before touching DNS. If the process is restarting, preserve its first useful log and restart count.

Record recovery evidence

Keep the observed failing layer, the single change made and the request proving recovery.

Keep the next check reproducible

Record the selected field or observed layer, the time, and the result that would confirm the next step.

Documentation used

Primary references for this page. Check the documentation for the version installed in your own environment.