# Websocket with Node-RED and reverse proxy

**URL:** <https://discourse.nodered.org/t/websocket-with-node-red-and-reverse-proxy/85062>\
**Category:** General\
**Created:** [31 January 2024 10:17 UTC](https://discourse.nodered.org/t/websocket-with-node-red-and-reverse-proxy/85062 "2024-01-31T10:17:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dcaccount](https://avatars.discourse-cdn.com/v4/letter/d/e36b37/32.png) [@dcaccount](https://discourse.nodered.org/u/dcaccount)\
**Post date:** [31 January 2024 10:17 UTC](https://discourse.nodered.org/t/websocket-with-node-red-and-reverse-proxy/85062/1 "2024-01-31T10:17:22Z")

</div>

Hello,  
following the indication that I got in this great forum, I installed in my Raspberry a reverse proxy, NGINX Proxy Manager to act as a SSL termination.

In NGINX Proxy Manager I have created a new proxy host and to "connect" with the Lighttpd webserver.

In my network then I have a Lighttpd Webserver that talks to Node-RED via Websocket and everything works well from within the LAN.

The problem I have is if I try to access via the hostname from the outside, Safari warns about the fact that it cannot open an insecure Websocket connection.

I cannot understand it as all traffic in the LAN is insecure.

I know this issue is not 100% pertaining to Node-RED but I cannot find a solution so maybe some can help me.

Thanks,  
Daniele

---

<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:** [31 January 2024 11:17 UTC](https://discourse.nodered.org/t/websocket-with-node-red-and-reverse-proxy/85062/2 "2024-01-31T11:17:24Z")

</div>

You need to think about the path that people are taking through to node-red.

Ideally, you should only use a single web server as it makes things a lot simpler. NGINX can do everything that lighttpd can do and more - though I recognise it might be a bit of a pain to transfer. Similarly, lighttpd can proxy as well via its addin.

---

<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:** [30 April 2024 11:17 UTC](https://discourse.nodered.org/t/websocket-with-node-red-and-reverse-proxy/85062/3 "2024-04-30T11:17:58Z")

</div>

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