search

techpines / express.io

Realtime Micro Framework for Nodejs
express-io.org
1.59k stars 234 forks source link

Unexpected response code: 502 #45

Open GeoffreyPlitt opened 11 years ago

GeoffreyPlitt commented 11 years ago

Testing this locally, works fine.

Once deployed on dotcloud, I get the following error in the browser:

WebSocket connection to 'ws://adtool-dev.makerin.com/socket.io/1/websocket/riwIRJrJmwCd2gJ64wyg' failed: Unexpected response code: 502

But I don't see anything in the server logs. Any advice?

GeoffreyPlitt commented 11 years ago

I'm doing "app.io.set 'log level', 1", is that the right way to get debug logs?

techpines commented 11 years ago

I think you want to leave the log level alone, I think it defaults to "debug: 3".

You might open up a javascript console and see there is any other clues in there. If you look 502 is listed in some cirumstances as being a bad gateway so maybe it's the load balancer? And if you're on dotcloud you will be behind a load balancer i believe.

http://en.wikipedia.org/wiki/List_of_HTTP_status_codes#5xx_Server_Error

techpines commented 11 years ago

Yea, that's what I'm saying. I don't think the request is ever making it to your application code. I think it might be getting stopped by dotcloud's load balancer. So the 502 is coming from the load balancer not your nodejs app.

techpines commented 11 years ago

Yea, I just checked out your url and it looks to be nginx, which I don't think support websockets on dotcloud.

Hope that helps!