Question

Websocket no longer works after clearing build cache

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


Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hi there,

The error that you are getting in Firefox indicates that the WebSockets service might not be running.

Do you see any errors in your App logs?

https://docs.digitalocean.com/products/app-platform/how-to/view-logs/

Regards,

Bobby