Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
I would guess that in development your code is run over http and so the websocket runs over websocket (no tls).
When you deploy to app engine you get tls between your client and server, this causes the websocket to use wss(ws over tls).
Your server isn’t configured to use tls, (it needs the location of your cert and key) so it fails.
As for how to solve this - that is what I am attempting to do - so far with little success but if I figure out the cause I will post here a solution.
The way I see it though there are three options:
force the websocket connection over ws (no tls).
App Engine provides a way to reference the location of the certs and key (perhaps through environment variables, not unlike the way i have seen it provide values for dev database).
Don’t use App engine, configure droplets where one is a nginx proxy that provides tls termination.
Me personally? Well I would settle for 1, 3 would make me re-evaluate my choice in PaaS and 2 would be the golden ticket.
Which one of these options are viable? Are there other options? No idea at the moment but I will report back with what I did to get past this.
How can fix this problem with the sockets? I have the same problem with Node.js project and socket.