Websocket connection failed (nginx websocket passthrough)
Have you ever encountered this?


11 Replies
Humph, no I have not. Are you running through a proxy of any kind?
I think I have seen this before, as kyle said, are you using a reverse-proxy?
Oh yeah, sollution was adding a couple headers in the nginx conf file
yup, could you send them here just for the record?

alright, marking this as resolved
actually can't do it because i'm on mobile but in a bit
btw, @kyle can you pin this?
Sure!
thank you
Done 🙂
is this what you guys use in nginx?
We don't currently proxy via nginx in our dogfood deployment (it lives at dev.coder.com).