Installed Node-RED on an Ubuntu AWS instance, setup security groups (allow access to port 1880). Node-RED itself works fine and I can send data over the internet. But if I create a http in node and try open the page I'm getting a "This site can’t be reached" error. I'm accessing it over public IP …

I wont comment too much in security, I'm not qualified enough. BUT, you can use something like (I'm sure there are others): node-red-contrib-http-custom-port (node) - Node-RED (nodered.org) This will fire up its own express instance (therefore a custom port) So you can still restrict port 1880 t…

Welcome @steveh92 We are going to need more info. The HTTP IN node will use the same port, so with that in mind, are you setting a response in your flow to a request being made via the HTTP IN node? can you share the flow?

Hi Marcus! I've just realized my issue, I didn't put the port in the url :sleeping: I have a question regarding using a domain name in the future, will this need the port?

The HTTP IN node does not spawn a new express instance, it will use the same instance that Node RED is using, but with a different route (as configured in the configuration of the node). So using a domain or not - you will need to specify a port on client devices. That's not to say you can't use s…

[image] marcus-j-davies: you will need to specify a port on edge devices Thanks. I was going to ask what's to stop people access the node-red editor if they have the IP/Domain. Because I've locked port 1880 to my IP but that's now going to stop anyone from accessing not just the editor but …

I've tested the custom port node you posted. Does each instance of a HTTP IN node have to have a separate port? When the same port is used for multiple nodes only one of them works. My idea was to have within this flow, multiple web pages generated using the same port.

I'm not sure - I don't use it I'm afraid (some here may though) But... If it works the same way as the native HTTP IN node, you can add params to the route, allowing a sort of prefix to the URL if you will. /api/:method Then clients can go to: http://../api/somemethod1 http://../api/somemethod…

Thanks Marcus. Here is my example but it seems to want to go down both paths no matter? Would you use a change to load the different web pages? [ { "id": "d34068484ea2ded8", "type": "tab", "label": "Flow 3", "disabled": false, "info": "", "env": }, { "id": "e8af32c9f72d4719", "type": …

We can't import that :smile: can you use back ticks ``` JSON Here ```

[ { "id": "d34068484ea2ded8", "type": "tab", "label": "Flow 3", "disabled": false, "info": "", "env": [] }, { "id": "e8af32c9f72d4719", "type": "template", "z": "d34068484ea2ded8", "name": "page", "fi…

Ah! Use a switch Node. [image] Initially you were rendering 2 responses for both methods, they were not separated

Node-RED

Node-RED Forum

Node-RED AWS issue

General

E1cid 19 October 2023 14:30 18

May be this will help Need to basic auth only some http node - #2 by E1cid

Topic		Replies	Views
Issue accessing SSL version of node-red General security	19	556	23 October 2023
Can I secure http IN location and lock down 1880? General	8	512	4 May 2022
Point a domain to my node red General	7	352	21 August 2023
Local httpadmin access from http request node General	41	632	4 February 2024
How to 'whitelist' IP address's that can access Node RED FAQs security	28	1748	12 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.

Node-RED AWS issue

Related topics