The API backend at api.rpow2.com is unreachable. The frontend at
rpow2.com loads fine, but every request from the SPA to the API
fails with ERR_CONNECTION_CLOSED in the browser.
Reproduced from two different machines / networks:
$ curl -v https://api.rpow2.com/
* Trying 15.204.254.192:443...
* Connected to api.rpow2.com (15.204.254.192) port 443
* schannel: failed to receive handshake, SSL/TLS connection failed
curl: (35) schannel: failed to receive handshake, SSL/TLS connection failed
TCP connection establishes, but the TLS handshake is aborted by
the server before it completes. Same symptom for /me, /auth/request,
/ledger — i.e. it's not endpoint-specific, the TLS layer is down.
The IP (15.204.254.192) resolves to OVH; given the recent fly-to-vps
migration plan in the repo, this looks like a TLS cert / nginx
config issue on the new VPS rather than an application bug.
Date observed: 2026-05-08 ~10:27 UTC.
The API backend at api.rpow2.com is unreachable. The frontend at
rpow2.com loads fine, but every request from the SPA to the API
fails with ERR_CONNECTION_CLOSED in the browser.
Reproduced from two different machines / networks:
TCP connection establishes, but the TLS handshake is aborted by
the server before it completes. Same symptom for
/me,/auth/request,/ledger— i.e. it's not endpoint-specific, the TLS layer is down.The IP (15.204.254.192) resolves to OVH; given the recent fly-to-vps
migration plan in the repo, this looks like a TLS cert / nginx
config issue on the new VPS rather than an application bug.
Date observed: 2026-05-08 ~10:27 UTC.