Summary

Both Railway services in our project are returning SSL_ERROR_SYSCALL / no peer certificate available on HTTPS, and 404 Denied — This URL has been blocked on HTTP. The services show as Online in the dashboard and respond correctly internally (via railway run), but are completely inaccessible from the public internet.

Affected services

• app-review-production.up.railway.app (Node.js / Next.js 15)
• content-strategy-production-0e91.up.railway.app (Python)

Both resolve to the same edge IP: 203.96.208.40 (IPv6: 2407:7000:2100:80ff:bd9d::1)

Symptoms

# HTTPS — TLS handshake never completes
$ openssl s_client -connect app-review-production.up.railway.app:443
SSL handshake has read 0 bytes and written 1574 bytes
no peer certificate available   ← server closes connection without sending cert

# HTTP — Railway proxy responds but blocks
$ curl http://app-review-production.up.railway.app/
HTTP/1.1 404 Denied
This URL has been blocked

# Internal (railway run) — works perfectly
$ railway run -- curl http://localhost:3000/api/health
{"ok":true,"auth_configured":true,"anthropic_configured":true}

What we tried (all failed)

• Regenerated the domain (new domain app-review-production.up.railway.app, same IP assigned)
• Redeployed via dashboard and CLI (railway redeploy)
• Changed PORT variable and triggered redeploy
• Confirmed the container starts and is ready (✓ Ready in 127ms, listening on 0.0.0.0)

Root cause hypothesis

The edge node at 203.96.208.40 is not completing TLS handshakes or routing traffic to backend containers. This started during or after the "Builds are queuing" incident (May 8). The incident was marked resolved but this networking issue persists.