WebSockets on StackBlaze
5 min readUpdated August 2026
A public web app already accepts WebSocket upgrades on its HTTPS URL. Use wss:// on the *.stackblaze.app host or your custom domain. There is no WebSockets switch and no Sticky Sessions control in the dashboard.
Step by step
01
Deploy a long-running web app
WebSockets need a process that stays up. Use a normal app with Expose to the internet on — not a Knative function.
02
Connect with wss://
In the client, use the same host as HTTPS, path and all. Example: wss://your-app-xxxx.stackblaze.app/socket. Custom domains work the same after they verify.
03
Plan for more than one replica
There is no session-affinity toggle. If you scale web replicas above 1, keep connection state in Valkey (or another store) so any replica can serve the next request.