Is this expected behaviour? Running script installed node-RED on a Raspberry Pi, and serving a public page via HTTPS using LetsEncrypt certificates. When I'm generally working in node-RED, I access NR by https://mydomain.co.uk:8443, but if I access via it's local IP address instead - http://192.16…

Paul, considering your requirements, I think a proxy like nginx or haproxy would better suit your needs. You'd set-up node-red as default (http) and use the proxy as a gateway (Https on the wan side, http on the LAN side) That way, when you are on the LAN side, you can connect to the LAN IP on htt…

HTTP and HTTPS use two different ports, 80 and 443 respectively. Do you have a proxy setup or using Node-Red setting for ssl?

External traffic is accessed via Cloudflare using full (strict) end to end encryption proxy. But I am using node-RED to setup SSL. The certificates are stored in .node-red/certs and are loaded in the settings.js file.

Try accessing the http address with port 8080 instead of 8443. 8443 is reserved for HTTPS and won’t autoforward your HTTP to 8080 without a proxy.

[image] Paul-Reed: In node-RED settings I have requireHttps: false, so I expected that I would be able to connect using http://192.168.0.8:8443 ?? In the commented out section of the settings.js file // The following property can be used to cause insecure HTTP connections to // be redire…

[image] UnborN: what i understand from the comment is that if requireHttps its set to true and you try to visit http://192.168.0.8:8443 and you have https enabled, you should be redirected to the secure https://192.168.0.8:8443 Yes, that's my understanding, but is this normal that node-RED i…

so we put Cloudflare to the side if you setup Node-red to be secure then its the only way to connect. no ? which you said you can with https://192.168.0.8:8443 (local) sorry i didnt undestand what you expected to happen :wink: you wanted to just type the ip and the port without prefixing https a…

It seems something else is going on here, maybe on the Cloudflare side since it is accessible through the standard 8443 (HTTPS) port. If access via HTTPS is available on 8443 then HTTP should be accessible via 8080 unless there is another process redirecting / blocking traffic. I'm not sure how No…

Thanks Steve I'm going to rebuild the system in the near future, so that's something that I'll read into, and try & implement.

Some great info in this post... [image] Node-red server with nginx reverse proxy howto guide FAQs Navigatable version on github https://github.com/meeki007/node-red-server-howto-guide/blob/master/README.md Ubuntu 20.04 - nigix - https - ssl - security - Fail2ban 403 ban…

Paul, Indeed like Steve said, a proxy is better and much secure. But if - for some reason you don't have that yet - you can cheat a bit, like I do: First I had added the mapping from myDomain to myRaspberryIp in the hosts file of my Windows portable (in order to be able to experiment with Letsen…

Node-RED

Node-RED Forum

Accessing node-RED using local IP

General

Steve-Mcl 23 January 2022 23:28 11

Some great info in this post...

Topic		Replies	Views
Enable https, but still access with local IP General	14	2167	10 May 2021
Cannot connect to Node red instance outside local network General http-request , security	3	300	9 November 2022
Node red x509 ssl home network not working General	6	1101	5 March 2021
Node-red with security padlock General security , httpstatic	14	166	11 February 2025
Https configuration General	9	306	31 January 2024

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Accessing node-RED using local IP

Related topics