Great vid, thanks for the help! I could be wrong but I think you need to update the server name in your nginx config. I was trying to set up a connection using the 'ws' library and the connection kept failing when I was addressing the server using the domain name that I configured the VM with but worked with the ip address. The reason being I hadn't updated the server name to my domain in the nginx. Maybe the fact that your client and host scripts are hosted on the same server means that the client behaves properly here but in general for anyone looking to set up a websocket connection you need to update the server name in the nginx or your socket.io connection will fall back to long polling or worse in my case my ws connection simply did not connect
@@zenon84 sorry Jonathan I don't :( I made this comment >2 years ago now. I can only vaguely remember the project I was working on. The specific change I made here is long since forgotten I am afraid
Google's Cloud Run DOES support WebSocket applications. Here is a link to their tutorial on how to set it up: cloud.google.com/run/docs/tutorials/websockets. Despite that this tutorial was still informative.
