Emergency maintenance migration - why does my node.js socket.io socket server no longer work?
Today I had emergency maintenance done on my Linode host and they migrated my Linode onto new hardware.
After the migration was complete, I had to spin up my node.js apps, and they all seem to run fine - EXCEPT for my node.js socket server app.
My socket server app uses socket.io, and there are no errors when I start the app up, but it doesn't seem like anything can connect to it.
I have a console log in there that is telling me that it is listening on the proper port - so it should be working. All other apps, including a web server/website all work fine.
Any ideas?
3 Replies
Faster help via https://cloud.linode.com/support/tickets
jackley
Linode Staff
@freeseus hard to say, though if your network connectivity is otherwise normal, that strongly suggests our hardware/network/infra aren't the root cause. From the perspective of your Linode, any emergency maintenance cycle is just a reboot (we aren't messing with the bits inside your Linode). Have you taken a look at socket's docs?
https://socket.io/docs/v4/troubleshooting-connection-issues/
Their website also links two other community resources that might be a good place to start: Stack Overflow and Slack:
https://stackoverflow.com/questions/tagged/socket.io
https://socketio-slackin.herokuapp.com/
I'd give those a try if you're still having trouble. I wouldn't recommend opening a ticket as this sounds like something outside our scope of support.
Hope this helps!
My socket server app uses socket.io, and there are no errors when I start the app up, but it doesn't seem like anything can connect to it.
Are you sure the server is listening to the proper IP address and not one of the Linode's a private IP addresses? Are you sure the server is listening on the correct address (i.e., an IPv6 address when it’s supposed to listen on an IPv4 address)? Are you sure that the server is not listening only on localhost?
Have you tried
telnet ipaddr port
From some remote system to see if the server responds?
— sw