# NodeRED on SSL https://

**URL:** <https://discourse.nodered.org/t/nodered-on-ssl-https/25483>\
**Category:** General\
**Created:** [25 April 2020 12:04 UTC](https://discourse.nodered.org/t/nodered-on-ssl-https/25483 "2020-04-25T12:04:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jithinsisaac](https://avatars.discourse-cdn.com/v4/letter/j/3ec8ea/32.png) [@jithinsisaac](https://discourse.nodered.org/u/jithinsisaac)\
**Post date:** [25 April 2020 12:04 UTC](https://discourse.nodered.org/t/nodered-on-ssl-https/25483/1 "2020-04-25T12:04:39Z")

</div>

Hey.. I have my Node-Red setup on a VPS by Digital Ocean.

I can access it via **http:// IP:1880**  
I am logging in via admin and password, that i have already generated.

I bought a domain a few days back. (Eg. example. com)

I now want to link a subdomain to the NodeRed installation. So i created a subdomain **nodered. example. com** and linked it to **http:// IP:1880** via Reverse Proxy using Apache. I installed SSL certificates by Lets encrypt.

I now can successfully access the NodeRed dashboard securely using **https:// nodered. example. com**

Trouble is that after logging in, I get a error saying **Lost connection to Server, reconnecting.**

I can still access Nodered without any issues via http:// IP:1880, but not via the Domain name.

Is there some other setup for https to be done for NodeRed?  
Any help would be highly appreciated!

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [25 April 2020 12:07 UTC](https://discourse.nodered.org/t/nodered-on-ssl-https/25483/2 "2020-04-25T12:07:31Z")

</div>

The "Lost connection" message is due to the editor being unable to establish its websockets connection back to the run time.

You must make sure your reverse proxy is configured to pass through websockets - they don't by default.

---

<div class="post-metadata">

**Author:** ![jithinsisaac](https://avatars.discourse-cdn.com/v4/letter/j/3ec8ea/32.png) [@jithinsisaac](https://discourse.nodered.org/u/jithinsisaac)\
**Post date:** [25 April 2020 14:14 UTC](https://discourse.nodered.org/t/nodered-on-ssl-https/25483/3 "2020-04-25T14:14:09Z")

</div>

Thanks Nick.. I will check it out.. If by chance you have any links for the same, do send it..

---

<div class="post-metadata">

**Author:** ![jithinsisaac](https://avatars.discourse-cdn.com/v4/letter/j/3ec8ea/32.png) [@jithinsisaac](https://discourse.nodered.org/u/jithinsisaac)\
**Post date:** [1 May 2020 18:51 UTC](https://discourse.nodered.org/t/nodered-on-ssl-https/25483/4 "2020-05-01T18:51:33Z")

</div>

While using NodeRed at **https:// nodered.example. com** URL using Apache Reverse proxy, on Inspecting the page, the following websocket error is obtained.

> WebSocket connection to 'wss://nodered.example. com/comms' failed: Error during WebSocket handshake: Unexpected response code: 404

Does using https always defaults to using wss i.e. secure websockets. Is there any way in which i can still use ws:// ?

Have been cracking my head over this for quite a few days now.. Not getting any significant help on enabling websockets over Apache reverse proxy..

Btw, i have not done any changes in the settings.js file to use https, i am still using http itself.

---

<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 June 2020 18:51 UTC](https://discourse.nodered.org/t/nodered-on-ssl-https/25483/5 "2020-06-30T18:51:34Z")

</div>

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