HTTP in Node Red from external network

Third party integrations Node-RED
1

I’m trying to reach a HTTP in node from an external IP address, but the connection always times out.

My setup:
My Home Assistance Supervisor is installed in an virtual environment on a QNAP NAS. The instance is reachable from outside my network through a secured duckdns domain. Internally I use my local IP address. This is accomplished with a reverse proxy (NGINX). I have no problems with that.

The node red dashboard is reachable with my duckdns domain without any problems.
The HTTP in node is reachable with my local IP address. The only thing that doesn’t work is to reach the HTTP in node with my duckdns domain. No matter what combination I try, it doesn’t work. I think it has something to with ports, but I can’t figure out the solution.

I have tried these addresses:

  • http[s]://myinstance.duckdns.org:1880/endpoint/test
  • http[s]://myinstance.duckdns.org:8123/endpoint/test
  • http[s]://myinstance.duckdns.org:8123/a0d7b954_nodered/endpoint/test

I would appreciate any input.

2

There are some warnings in the NodeRed addon documentation, but if they do not apply to your setup, then it should work.

If you can reach it from the local network, then you should have the IP and port there.
Then it should just be a matter of opening the port in the firewall and make a port forwarding rule in the router.

3

Yeah but port 443 is already opened for the reverse proxy to work, so every traffic that comes in on the duckdns domain is forwarded to this port. I don’t see a possibility to do that with port 1880 too.

4

Then you have to look into if Node Red can handle the SSL encryption itself and if it can then copy the certificate to its server configuration path.