Reroute socket.io | Cloudflare

[Kowlin]

I'm not experienced with nxing, but what I do know is that the subdomain you're trying to use for the websockets cannot be CloudFlare enabled

[bitspook]

Can I use CloudFlare with WebSockets?

As of August 5, 2014, CloudFlare supports WebSockets for Enterprise customers only. (Announcement). WebSockets are currently only available for Enterprise customers, but will be available for other plan levels in the future.

All other customers -- Business, Pro, and Free -- should create a subdomain for Websockets in their CloudFlare DNS and disable the CloudFlare proxy ("grey cloud" the record in CloudFlare DNS Settings).

---

there was some code on a tut that allowed for exactly that, unfortunately i cannot find that tut at this time.

[Andi]

@Kowlin said:

I'm not experienced with nxing, but what I do know is that the subdomain you're trying to use for the websockets cannot be CloudFlare enabled

Yes I know that. But I still have to reroute the WebSocket Traffic to a subdomain.

[markkus]

Perhaps this post can help?
https://community.nodebb.org/topic/4645/websocket-domain/4

[Andi]

@markkus

I've tried that already. But this configuration cause that nodebb will not start.

[Andi]

No ideas?

[lenovouser]

@Andi My configuration definitely works. I use it myself with CF. Maybe you could tell us a bit more what doesn't work? You're just saying that it doesn't start, but in general this has nothing to do with subdomains / proxying etc. If it really doesn't start it has something to do with NodeBB / your config. Might be helpful if you posted the errors in that case.

[Andi]

@lenovouser

^ This happens when I insert this:

to my config.json file.

NodeBB v0.9.3

[lenovouser]

Yep, there is a missing comma after the } which is before "socket.io". After you fixed it paste the config in the JSON validator just to be sure there is nothing else left.

[Andi]

@lenovouser you're awesome!

Thanks alot

#caseclosed

[lenovouser]

@Andi no problem, happy to help