stoiet
CDCloudflare Developers
•Created by si458 on 9/11/2023 in #general-help
websockets not working with dns proxied or tunnels
I am still waiting for them to respond to my support ticket.
14 replies
CDCloudflare Developers
•Created by si458 on 9/11/2023 in #general-help
websockets not working with dns proxied or tunnels
Just one addition, when I was able to reproduce it in production with this great tool (
https://websocketking.com/) from Microsoft Edge it was consistent. At the same time the connection worked perfectly in Chrome / Firefox / DuckDuckGo / Safari. Same tool, same time, same parameters. A few hours after, the same happened with Chrome, and in Edge it was working. And we repeated the same test several times. This is why I do not see any patterns.14 replies
CDCloudflare Developers
•Created by si458 on 9/11/2023 in #general-help
websockets not working with dns proxied or tunnels
Yes, sure, I quoted the
100% uptime from the official site:D (https://www.cloudflare.com/en-gb/plans/)
In production we reverted back to DNS only with Heroku let's encrypt integration. Now it works for everyone. In staging we do not use proxy server, basically we have the same setup as now in production. It was one of the mistakes, the difference between staging and production hid the issue during testing.
Locally we were never able to reproduce it even though we use the same command / environment variables / configs to start the server locally.
While we had the proxy setup, we also tried these things on cloudflare:
- custom rule which uses strict SSL (it was recommended that full may be not enough)
- extended custom response headers with Connection: upgrade and several things others recommended
No success. It was so random, we were unable to reproduce it for 2 weeks, it appeared only in the case of customers. No pattern, random browsers, devices. Also we tried to reproduce the issue with same os/browser + VPN. No success.
The comments in the github thread are really reflecting and similar to our problem. Nothing visible, but X% of the cases the websocket connection cannot even be initialised.
Now that the production is fixed, probably we will set up a test service where we can do experiments safely. And maybe together with the cloudflare support we can figure out something. The features of the proxy are necessary for us, so we do not want to let it go.14 replies
CDCloudflare Developers
•Created by si458 on 9/11/2023 in #general-help
websockets not working with dns proxied or tunnels
Other then the issues mentioned in the github thread I can think of that we have just a Pro plan, not Business plan, and it does not guarantee 100% uptime.
14 replies
CDCloudflare Developers
•Created by si458 on 9/11/2023 in #general-help
websockets not working with dns proxied or tunnels
Yes we use cloudflare for DNS records and as a proxy server. The problem is that it is random. The only thing we see is that the browser exception:
Websocket connection to XYZ failed Nothing in our logs, nothing in cloudflare. It is random which browser or when it happens. We use cloudfront as well, but for totally different purposes, the websocket traffix does not go through it.14 replies
CDCloudflare Developers
•Created by si458 on 9/11/2023 in #general-help
websockets not working with dns proxied or tunnels
Not same software, we have a Heroku application with uvicorn / websockets. CNAME with proxy on Cloudflare. DNS only works fine if the request goes immediately to the heroku router. We started the investigation 3 weeks ago, from the frontend to the backend. I think we excluded everything, package upgrades, configs, etc. The only thing left is cloudfront. Today we were able to confirm that it works with DNS only.
14 replies
CDCloudflare Developers
•Created by si458 on 9/11/2023 in #general-help
websockets not working with dns proxied or tunnels
Up. We've been experiencing the same issue since 9th of January. DNS only also works for us, but not with proxy. We opened a support ticket, but no answer yet.
14 replies