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.

I have an app with 2 components (Client + server) that had a working wss connection.
I forced a Rebuild and Deploy and chose to “Clear Build Cache” (This is the first time that I have used this option.
The websocket connection no longer works, and I am too far to rollback to a working version (Says Firefox can’t establish a connection to the server at wss://foo.com/ws/.) I did yesterday rollback to a working version, and that saved me, but now I am beyond that limit that I did not realize exist.
I reset both the server and client code to days before to test if any reset changes had caused this, and it still fails.
Could there have been any routing or other information in the build cache that could have been causing the websocket secure to work, or is that not a place I should look for this issue?
Thanks
6a2e133a62fe4859920f9233303d8c
PowerAdSpy
phosphide
lking
santoshpatil
Rory McEwan
crisdan
kdcarter17
garantieheld
7c31733a76c942f69d6186090a3787
36d56192d3114513857618b22686be