So with the new quick editor, on its first day, a CF acknowledge and no (by may 24 or earlier fixed) custom domains were not supported, and the editor’s right side request generator was broken/failed/crashed/UI frozen unless you reenable ..workers.dev
Things look better, and I can use my custom domains now. But I started seeing that some of my workers/domains, the lower right CFW devtools box is always broken.
Debugging connection was closed. Reason: WebSocket disconnected
Reconnect when ready by reopening DevTools.
Reconnect DevTools
and chrome network view shows
Connections.ts:87 WebSocket connection to 'wss://my.domain.com/cdn-cgi/workers/preview/inspector?cf_workers_preview_token=ADU-syj2zDktl6PV_yvXeINb' failed:
(all URL details fuzzed)
I was thinking and thinking, tried different years of edge, chrome, FF, and Iron chromium. Tried Android 3rd party Chromium from my phone also. same CFW dev tools crash.
WebSockets
Allow WebSockets connections to your origin server.
Concurrent connection guidelines for your plan: low. Learn more.
This setting was last changed a few seconds ago
So previously I had this set to “Off”, my origins are static file hosters, or IPV4 multi-tenant edge proxies. I dont use it so I naturally turned it off. I changed this toggle to “on”, now CFW devtools works and prints my console.log() messages no problems when i do test preview requests.
I really don’t know why the CF WAF/Edge proxies do NOT allowlist “wss://my.domain.com/cdn-cgi/”, from user controlled settings toggle. This is a bug with the new quick editor, and maybe its a bad idea, to run the Quick Editor to “https://my.domain.com/cdn-cgi/” instead of “https://funny-monkey-c7ed7e86ede76.dev.cloudflaredevs.net/cdn-cgi/” 1 time use throwaway internal domains. Something needs to be rethought, atleast allowlist “wss://my.domain.com/cdn-cgi/” so even if WSS is formally off for the domain, Quick Edit dev tools console always works. Or devtools needs a proper error message telling the CF dev “check WSS settings for your domain”, not “Debugging connection was closed. Reason: WebSocket disconnected”. I’d rather see something like GET wss://inspect.cloudflare.com/56account2c/cczone81/84revisionb1/inspector Upgrade: websocket Authorization: bearer ef4b43e7517116354f34086a52eccabf30d2ecce instead of looping to my official DNS name/real public side WAF entry point.
I know the old editor was running “workersd” independent on google cloud VPSes, with KV/Secrets/Cache API/edge proxy/WAF-ish features missing. But how many more new Quick Edit vs CF WAF/Edge Proxy bugs will there be? Should Quick Edit be subject to a zone’s WAF/anti-bot rules/custom FW rules? How close should Quick Edit be to a “real eyeball” with Chrome/FF/Safari or a M2M REST “bot” request?