Websockets with Workers
Howdy y'all! I have a worker that is functioning as a websocket server. Everything works fantastically:
- locally / in dev
- in production if I use a CLI to interact
The second I wire up a browser to it, things start failing though. And what's worse, the failing has almost no details anywhere that I can find. The connection succeeds and then immediately closes. No logs on the backend, and logs on the frontend are code 1006 ("i dunno what happened").
Has anyone seen this before? Any ideas where to dig in? It feels like either browser security (no luck on making CORS permissive) or something strange Cloudflare is doing.
8 Replies
Hello, are you using Hono in the worker?
Indeed! I ended up chasing it down - there was some error handling code that was firing at the wrong time and closing the connection in my frontend 😐 Yeah, I want those hours back haha
bro can you tell me how do i use websockets with workers? or any guide that you used? please
Cloudflare Docs
Build a WebSocket server with WebSocket Hibernation · Cloudflare Du...
Build a WebSocket server using WebSocket Hibernation on Durable Objects and Workers.
I did things a little differently than that article hunt references.
Hope it helps!
https://www.analogous.dev/blog/websockets-and-cloudflare-workers
Websockets and Cloudflare Workers - analogous.dev
Websockets and Workers! A match made in heaven! Or not. Stateful, persistent communication? With ephemeral, floaty web workers that have almost no state? How in the world can those interoperate!? Leave it to the talented folks at Cloudflare to build a fantastic integration. This is ...
bro, I already said, do you know what the prices are for websockets without durable objects?
Sorry, didn't see that message, and don't know yet. I should be able to tell you in about a month though haha. 🤣
jajajaj lmao