# Node red dashboard accessing from internet

**URL:** <https://discourse.nodered.org/t/node-red-dashboard-accessing-from-internet/58637>\
**Category:** Dashboard\
**Tags:** security\
**Created:** [19 February 2022 08:07 UTC](https://discourse.nodered.org/t/node-red-dashboard-accessing-from-internet/58637 "2022-02-19T08:07:00Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [19 February 2022 11:31 UTC](https://discourse.nodered.org/t/node-red-dashboard-accessing-from-internet/58637/6 "2022-02-19T11:31:23Z")

</div>

Have you searched the Forum? There is also something in the Cookbook and an FAQ here on the Forum.

You need a reverse proxy to do what you are asking for.

> [@alda](#):
>
> special software for this ? It's crazy

No it isn't. Node-RED is a "microservice". It includes a limited web server that exposes a single port. You might have many instances of Node-RED plus other node.js, Python, Rust, Go, ... web servers all running either on the same device or across your internal network.

Proxying them to the outside world is a specialist task that requires a specialist service.

There are also security considerations to be taken into account when you expose a web service to the 7 billion human beings and untold automated bots in the world. Again, this is best dealt with using specialist tools.

So no, not crazy at all.

---

_[View the full topic](https://discourse.nodered.org/t/node-red-dashboard-accessing-from-internet/58637)._