Node-red & Cloudflare

[Paul Reed]

Just added Cloudflare to my server, and I'm now having problems accessing node-red via my domain.

I can access NR via my private IP, ie 192.168.1.10:2052 and everything is fine. However accessing it via my domain (http) results in the screenshot below.

I've opened port 2052 in my router, and checked that it's actually open. Also checked with Cloudflare that port 2052 can be used.

Any ideas please.

[Julian Knight]

So you can reach NR correctly from outside your router without Cloudflare? e.g. you are sure this isn't a router issue? It isn't just about having the port open.

Also, why that port instead of port 443 (wss)?

There is some information on Cloudflare support of websockets here: https://blog.cloudflare.com/cloudflare-now-supports-websockets/

I haven't had time to read it fully but there may be some clues there.

[Julian Knight]

Ah, and some more possible issues:

http://thenewstack.io/cloudflare-now-supports-websockets-but-not-without-challenges/

http://stackoverflow.com/questions/26395881/websocket-over-ssl-cloudflare

[Paul Reed]

Thanks Julian, I am using port 443 for http traffic, but have set port 2052 in settings.js for nodered (instead of the default 1880).

The links that you have provided are very helpful though, and do appear to be the cause of the problem, because everything worked fine before installing Cloudflare.

I'll have a look at other options such as putting node-red on a subdomain, and not include it within Cloudflare, but first I'll message their help desk, and see how helpful they are!

Paul

[Paul Reed]

Sorry I meant I was using port 80 for http. I want to get it working on http first before enabling SSL.

Paul

[Julian Knight]

OK, no worries. Not sure if changing the Node-Red port also changes the websockets. Perhaps Nick or Dave know?

Please just remember that it takes around 30sec or so before a newly exposed standard port on the Internet starts getting probed - meaning that there are systems out there constantly looking for vulnerable hosts. Personally, I'd get HTTPS working first, make sure all my sockets were using wss: then connect to the Internet.

[Nicholas O'Leary]

> Not sure if changing the Node-Red port also changes the websockets. 

Err, yes... websockets is initiated by an HTTP request so it uses the same server instance.

Nick

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
For more options, visit https://groups.google.com/d/optout.