@julian thanks for the hint~
Not sure why, but after update NodeBB source code, it works fine, thanks~!!
Is it only me or did just Cloudflare screw up?
They just activated free SSL for all plans.
But this new feature seems to break websockets for non-CDN domains. Which means NodeBB downgrades to xhr-polling.
@hek Mines fine. Hosted in Amsterdam.
Strange... The NodeBB forum also downgrades to xhr-polling for me now. Guess they also use DO for hosting?
@hek Do indeed.
@hek Digital Ocean didn't offer free SSL, you might be thinking of Cloudflare?
I certainly hope they didn't activate it for this forum, we already have SSL, I don't want to be using theirs.
Yes, of course.. your right. head-mixup .. changed title.
In any case, I've disabled the SSL setting in Cloudflare for nodebb.org. Not sure if that was actually causing problems, but you should still be able to access nodebb via SSL.
Do you get xhr-polling or regular websockets here on the NodeBB-forum?
So is now a bad time for me to have signed up for Cloudflare and move my DNS over to them?
Hopefully I've set this up right.
@hek I have the same issue with cloudflare and I changed back to my domain provider's nameservers.
@hek No, I'm not dropping back to xhr polling That's an odd side effect..... can you clear cache and try again?
Gah.. It might be a chrome-thing? My chrome recently updated. The inspect/dev-console looks different.
I "clicked-around" a bit and now the browser shows a websocket connection again!