21 days ago
Project: orbit (production), project ID f2827cf0-39ad-4e47-bb35-3274515ed912, service "orbit"
Domain: orbit.college, purchased through Railway, target port 8080. The dashboard shows a green check.
Problem:
- HTTPS fails: the TLS handshake closes with no certificate (Firefox: PR_END_OF_FILE_ERROR; openssl: "no peer certificate available").
- Plain HTTP on port 80 also gets an empty reply, including /.well-known/acme-challenge/.
DNS (Railway-managed):
- The A record was 69.46.46.35. I deleted and re-added the domain today (2026-09-14), and it's now 69.46.46.127.
- Neither address serves orbit.college, and neither serves the service's orbit-production-a171.up.railway.app hostname.
The service itself is healthy: orbit-production-a171.up.railway.app (resolves to 69.46.46.77) returns 200 on /healthz.
Certificates: Let's Encrypt issued valid certificates for orbit.college on 2026-07-01, 2026-08-30 and 2026-09-03 (valid to 2026-12-02). None has been issued since the re-add, and still no certificate is served as of 20:06 UTC.
Railway status page: fully operational.
Could you re-provision edge routing and the certificate for orbit.college? Thanks!
2 Replies
21 days ago
Our edge logs show that TLS is completing successfully and the domain is returning 200 responses as of 20:13 UTC today, with a valid certificate in place. If you are still seeing TLS handshake failures, the connection is likely reaching a different address than the one currently serving the domain (69.46.46.127). Flushing your local DNS cache and retesting, or testing from a different network, should confirm whether the domain is reachable from your location.
Status changed to Awaiting User Response Railway • 21 days ago
21 days ago
As the bot said, your website is working just fine on my end with a valid certificate.
Status changed to Awaiting Railway Response Railway • 21 days ago
Status changed to Solved medim • 21 days ago