Cloudflare proxy stopped working
razzmatazzz
HOBBYOP

13 days ago

A couple days ago, the cloudflare proxy configuration for my project stopped working. I've quadruple-checked the settings and even re-created the custom domain setting in Railway. It just doesn't work. Accessing my app through the provided Metal Edge domain works fine, so the app is functioning as it should. We changed nothing in our configuration settings when this stopped working.

Solved

9 Replies

brody
EMPLOYEE

13 days ago

Hello,

Can you please define not working?

Status changed to Awaiting User Response Railway • 13 days ago

razzmatazzz
HOBBYOP

13 days ago

Requests sent to the proxied domain return a 502 status code.

Status changed to Awaiting Railway Response Railway • 13 days ago

brody
EMPLOYEE

13 days ago

I can open the domain just fine. Can you give me a path I can curl to see the error you mentioned?

Status changed to Awaiting User Response Railway • 13 days ago

razzmatazzz
HOBBYOP

13 days ago

It's a websocket server. Requests sent via wss (port 443) result in the 502 status code response.

Status changed to Awaiting Railway Response Railway • 13 days ago

ray-chen
EMPLOYEE

13 days ago

 ~ ツ websocat wss://<your_domain>
websocat: WebSocketError: WebSocketError: Received unexpected status code (401 Unauthorized)
websocat: error running

This appears to work fine. Can you give us a reproduction please?

Status changed to Awaiting User Response Railway • 13 days ago

razzmatazzz
HOBBYOP

13 days ago

Apologies; there's some minimal authentication done to filter out automated requests. Try sending a request to: wss://<domain>?sessionid=TEST

Without the sessionid search param, the request won't reach origin.

Status changed to Awaiting Railway Response Railway • 13 days ago

brody
EMPLOYEE

13 days ago

Ah, gotcha. Then that matches an open ticket we are investigating.

I'll link this thread to that ticket so we can follow up when this is solved.

If you want an immediate resolution, you can follow the instrcutuions I have provided in the following thread:

https://station.railway.com/questions/websockets-aren-t-getting-routed-properl-4c8eef63

Status changed to Awaiting User Response Railway • 13 days ago

razzmatazzz
HOBBYOP

13 days ago

Thanks. I've followed the steps to resolve the issue from that thread, but nothing has changed.

Status changed to Awaiting Railway Response Railway • 13 days ago

brody
EMPLOYEE

13 days ago

Hello,

Deeply sorry about the wait, this one was tricky to solve for, but it has been fixed and there's no further action needed on your end.

heart1

Status changed to Awaiting User Response Railway • 13 days ago

Railway
BOT

6 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 6 days ago

Loading...