Can I set up socket.io chat on heroku?

Question

I have a simple socket.io chat application which I\'ve uploaded to one of the new Heroku \'cedar\' stacks.

Now I almost have everything working but I\'ve hit one stumbli

Answer 1

I was also having this problem on heroku. I was able to make it work using the hostname "myapp.herokuapp.com" (or simply window.location.hostname, to work both local and in production) and setting the port to 80. I'm using SocketIO 0.6.0.

Answer 2

This has now changed as of Oct 2013, heroku have added websocket support:

https://devcenter.heroku.com/articles/node-websockets

Use:

heroku labs:enable websockets

To enable websockets and dont forget to remove:

io.configure(function () { 
  io.set("transports", ["xhr-polling"]); 
  io.set("polling duration", 10); 
}); 

Answer 3

2011-06-25T21:41:31+00:00 heroku[router]: Error H13 (Connection closed without response) -> GET appxxxx.herokuapp.com/socket.io/1/websocket/4fd434d5caad5028b1af690599f4ca8e dyno=web.1 queue= wait= service= status=503 bytes=

Does this maybe mean the heroku router infront of the app is not configured to handle web socket traffic?

[update] It would appear as of 6/22/2011 the answer is yes... heroku does not support socket.io see this post: http://blog.heroku.com/archives/2011/6/22/the_new_heroku_2_node_js_new_http_routing_capabilities/

Answer 4

After trying every combination under the sun I finally just left it blank. Lo and behold that works perfectly. You don't even need the port.

socket = new io.Socket();

Answer 5

The correct way according the article on heroku is:

io.configure(function () { 
  io.set("transports", ["xhr-polling"]); 
  io.set("polling duration", 10); 
});
socket = new io.Socket();

This ensures that io.Socket won't try to use WebSockets.

Answer 6

Wouldn't you just put your actual hostname?