websocket 404 issue after deploying to fly.io
It works fine locally, but it returns a 404/301 error when deployed to fly.io. Do you guys have any ideas about this issue?
Thanks in advance!
7 Replies
301 is a redirect
have you tried wss?
wss is 404
I guess it's related to backend deploy issue, but still don't get a clue to figure it out
404 is a backend issue, yes
either the websocket didnt start (unlikely) or that's the wrong path (likely)
the path works locally, so I guess it's deploy issue like fly io need to config to support websocket
but still a guess and need further debug
it might be a deploy issue, yes