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.
- 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.
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Similar Threads
Was this page helpful?
