Redis public proxy (shuttle.proxy.rlwy.net:23717) is rejecting all SSL connections with "Connection reset by peer"
davidmooreuk
HOBBYOP

21 days ago

Service: Redis (ID: 746bbfb8-45eb-40d3-863e-af40c1cfb25a)

Environment: production (eloquent-cat project)

Issue: Public Redis proxy rejects SSL connections immediately after TCP handshake succeeds

Error: SSL_connect failed: Connection reset by peer

Tested: Both locally with redis-cli and from app containers

TCP connection works (0.3-0.4ms latency), but SSL handshake fails

Restarted Redis service — no change

Internal Redis (redis.railway.internal) also times out

Evidence:

redis-cli -u "rediss://default:PASSWORD@shuttle.proxy.rlwy.net:23717" PING

Could not connect to Redis at shuttle.proxy.rlwy.net:23717: SSL_connect failed: Connection reset by peer

Solved

3 Replies

Railway
BOT

21 days ago

Your Redis service's last deployment is from 2026-05-02 and the symptoms (both public proxy SSL failures and internal network timeouts) match a known pattern where platform networking changes make existing database services unreachable despite appearing healthy. The fix is to redeploy the Redis service (not just restart it) - you can do this from the service's three-dot menu or via the command palette (Cmd/Ctrl+K) and selecting "Redeploy source image."


Status changed to Awaiting User Response Railway 21 days ago


Status changed to Solved davidmooreuk 21 days ago


Railway

Your Redis service's last deployment is from 2026-05-02 and the symptoms (both public proxy SSL failures and internal network timeouts) match a known pattern where platform networking changes make existing database services unreachable despite appearing healthy. The fix is to redeploy the Redis service (not just restart it) - you can do this from the service's three-dot menu or via the command palette (Cmd/Ctrl+K) and selecting "Redeploy source image."

davidmooreuk
HOBBYOP

21 days ago

Public proxy still isn't reachable, but can reach internally so good enough for now.


Status changed to Awaiting Railway Response Railway 21 days ago


Railway
BOT

21 days ago

If you need public access later, removing and re-adding the TCP proxy in the service's Networking settings will re-provision the proxy endpoint.


Status changed to Awaiting User Response Railway 21 days ago


Status changed to Solved Railway 21 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...