Solvulator surface reportlive status, browser-side probe

The reports server that ran on nabla:8091 is offline. Until it comes back, this page does its job inline: it asks your browser to probe each public surface of the solvulator constellation and tells you what answers.

nabla :8091 is not bound. If you bring it back up, point report.solvulator.com back at it and this static page retires. The Caddy stanza on nabla currently routes here.

probing…

What this is and isn't

This is a browser-side probe. It runs in your tab. It tells you what your browser sees right now from your network. It does not replace server-side monitoring (fleet/bin/observe on hub2 runs every 15 minutes and has a longer memory), but it answers the immediate question: is the surface up for me now?

Surfaces flagged "degraded" returned a non-OK code that the server may consider intentional (3xx redirect, 401 auth, 503 service-unavail). Surfaces flagged "down" failed to connect or timed out.

To restore the proper report service

Bring a process up on nabla:8091 that produces report output (the original solvulator reports). Then have nabla's /etc/caddy/Caddyfile re-route:

report.solvulator.com {
    reverse_proxy 127.0.0.1:8091
}

And reload via curl -X POST … :2019/load if you want to avoid a sudo round-trip; otherwise sudo systemctl reload caddy.