# Web Server - for my customers?

**URL:** <https://discourse.nodered.org/t/web-server-for-my-customers/95828>\
**Category:** General\
**Created:** [6 March 2025 14:39 UTC](https://discourse.nodered.org/t/web-server-for-my-customers/95828 "2025-03-06T14:39:54Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![damica51](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@damica51](https://discourse.nodered.org/u/damica51)\
**Post date:** [6 March 2025 14:39 UTC](https://discourse.nodered.org/t/web-server-for-my-customers/95828/1 "2025-03-06T14:39:54Z")

</div>

Hello: I'm looking for suggestion on how I need to get this done.

I have a new project and this is what I need to make happen.

I'm using Mqtt as my communication protocol.

So this is what I'm doing.

I have a job that only runs for 36 hours, during that job I want to collect (to a database - every 2 minutes) and display 2 variables (Pressure, Flow Rate). I can do all this now with my Ignition SCADA Server. BUT I would like to have a web page that my customers can log into and see this live data and I want some type of a TREND for the data being recorded.

Does anybody have any recommendations?  
Thanks

---

<div class="post-metadata">

**Author:** ![thebaldgeek](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/thebaldgeek/32/93523_2.png) [@thebaldgeek](https://discourse.nodered.org/u/thebaldgeek)\
**Post date:** [6 March 2025 17:21 UTC](https://discourse.nodered.org/t/web-server-for-my-customers/95828/2 "2025-03-06T17:21:31Z")

</div>

MQTT does not really have anything to do with a website.  
As far as Node-RED goes, you can tweak settings.js and put a user/pass on the dashboard.  
I think most here would recommend a VPN only access for your customers.  
If the number of customers is very low, and the dashboard is very simple (caution with the trends), then it should be a pretty quick build using either dash 1 or dash 2 nodes. (Depends on if you need responsive pages or not).

What PLC is behind this?

---

<div class="post-metadata">

**Author:** ![damica51](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@damica51](https://discourse.nodered.org/u/damica51)\
**Post date:** [6 March 2025 19:09 UTC](https://discourse.nodered.org/t/web-server-for-my-customers/95828/3 "2025-03-06T19:09:54Z")

</div>

Thanks for the Info.

Allen Bradley Micro-820 plc.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [6 March 2025 19:46 UTC](https://discourse.nodered.org/t/web-server-for-my-customers/95828/4 "2025-03-06T19:46:21Z")

</div>

> [@thebaldgeek](#):
>
> I think most here would recommend a VPN only access for your customers

👆

Always!!!

Node RED - is a target for hackers, so please use the strongest/safest methods possible.

If you search these forums - you will find many (unfortunate) stories of Node RED being hacked, and by extension - the systems it is attached to.

Its not a weakness of Node RED - more so the user implementing it, and foolishly exposing it to the public, without implementing the correct security measures.

See : [Safely accessing Node-RED over the Internet](https://discourse.nodered.org/t/safely-accessing-node-red-over-the-internet/45024)

In essence - Don't open Port 1880, and instead create a tunnel for specific source connections.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [6 March 2025 20:02 UTC](https://discourse.nodered.org/t/web-server-for-my-customers/95828/5 "2025-03-06T20:02:40Z")

</div>

> [@damica51](#):
>
> Does anybody have any recommendations?

You could go with a Node-RED provider that has spent the last 3 years developing a secure by default way of hosting node-red. like, for example [FlowFuse](http://www.flowfuse.com). Everything is done for you.

---

<div class="post-metadata">

**Author:** ![damica51](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@damica51](https://discourse.nodered.org/u/damica51)\
**Post date:** [7 March 2025 11:28 UTC](https://discourse.nodered.org/t/web-server-for-my-customers/95828/6 "2025-03-07T11:28:43Z")

</div>

Thanks, I will look into this. This is what I was hoping for. Sounds like this might work for my needs. Will keep you posted.

---

<div class="post-metadata">

**Author:** ![shubhamnodered](https://avatars.discourse-cdn.com/v4/letter/s/e8c25b/32.png) [@shubhamnodered](https://discourse.nodered.org/u/shubhamnodered)\
**Post date:** [8 March 2025 10:17 UTC](https://discourse.nodered.org/t/web-server-for-my-customers/95828/7 "2025-03-08T10:17:31Z")

</div>

What about using "reverse proxy" service like "Ngrok" or "LocaltoNet" as VPN tends to be slower?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [22 March 2025 10:17 UTC](https://discourse.nodered.org/t/web-server-for-my-customers/95828/8 "2025-03-22T10:17:59Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.