# Dashboard Error "Connection Lost"

**URL:** <https://discourse.nodered.org/t/dashboard-error-connection-lost/7965>\
**Category:** General\
**Created:** [14 February 2019 16:00 UTC](https://discourse.nodered.org/t/dashboard-error-connection-lost/7965 "2019-02-14T16:00:04Z")\
**Posts on this page:** 11\
**Page:** 3

<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:** [22 March 2019 17:05 UTC](https://discourse.nodered.org/t/dashboard-error-connection-lost/7965/41 "2019-03-22T17:05:45Z")

</div>

> [@tonylane26](#):
>
> Enabled HTTPS

How is this configured? Using https for Note-RED changes ws into wss connections. Could there be a certificate issue or something blocking wss?

I am using:

```
Vivaldi	2.3.1440.61 (Stable channel) (64-bit)

```

and I'm not seeing any issues like this which makes me think that it is something environmental. e.g local to your configuration.

What extensions do you have installed? Is an ad-blocker or some other security extension causing issues? Try from an in-private browsing session or try restarting the browser without extensions loaded.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [22 March 2019 17:10 UTC](https://discourse.nodered.org/t/dashboard-error-connection-lost/7965/42 "2019-03-22T17:10:27Z")

</div>

I saw it after I had imported a flow from the forum. It think it started when I deleted the visible nodes. I then fiddled about and it went away, but I wasn't certain exactly what made it stop.

---

<div class="post-metadata">

**Author:** ![tonylane26](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tonylane26/32/9272_2.png) [@tonylane26](https://discourse.nodered.org/u/tonylane26)\
**Post date:** [23 March 2019 19:26 UTC](https://discourse.nodered.org/t/dashboard-error-connection-lost/7965/43 "2019-03-23T19:26:39Z")

</div>

I used this technique to create the self-certified HTTPS. It could be part of the problem since my PC is subject to corporate admin, and I don't have access to security settings. It did work for at least 3 weeks though, and now it still does if I use the MS Edge browser.

> **[Increasing NodeRED security: 5 min guide - Not Enough TECH](https://notenoughtech.com/home-automation/nodered-home-automation/nodered-security/)**
>
> The moment you'll take things outside of your local network you should start paying attention to the security of your connections. NodeRED security.

---

<div class="post-metadata">

**Author:** ![tonylane26](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tonylane26/32/9272_2.png) [@tonylane26](https://discourse.nodered.org/u/tonylane26)\
**Post date:** [23 March 2019 19:31 UTC](https://discourse.nodered.org/t/dashboard-error-connection-lost/7965/44 "2019-03-23T19:31:02Z")

</div>

I did a cleanup but there was nothing obviously wrong. Restarted both Node-red and even a full Pi reboot.  
Based on other comments I am beginning to see it as an issue with my work PC that somehow only materializes with Chrome and not Edge. My iPhone (also corporate) now doesn't work either, but my iPad does. I am reluctant to drop the HTTPS requirement as I do still want it available on the Web. Maybe I will look into an alternative secure socket strategy.  
Thanks for your help.

---

<div class="post-metadata">

**Author:** ![Creeps](https://avatars.discourse-cdn.com/v4/letter/c/e19b73/32.png) [@Creeps](https://discourse.nodered.org/u/Creeps)\
**Post date:** [3 May 2019 15:09 UTC](https://discourse.nodered.org/t/dashboard-error-connection-lost/7965/45 "2019-05-03T15:09:42Z")

</div>

I have a similar issue on my Samsung Galaxy Tab A with Chrome.  
When I unlock the tablet, I get this "connection lost" notification coming up every second or so.  
The only way to get rid of it is to reload the page manually, which is not really comfortable.

---

<div class="post-metadata">

**Author:** ![wongnam](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/wongnam/32/8531_2.png) [@wongnam](https://discourse.nodered.org/u/wongnam)\
**Post date:** [22 May 2019 11:26 UTC](https://discourse.nodered.org/t/dashboard-error-connection-lost/7965/46 "2019-05-22T11:26:30Z")

</div>

Update.  
Today I tried deleting the webcache in browser setting and running the dashboard without having the same disconnection situation as before. I also didn't fix or change it, but just upgrade something like the environment below.

### about my environment:

- Node-RED-Dashboard version: 2.15.2 (Github latest version)
- Node-RED version: 0.20.4
- node.js version: v8.12.0
- npm version: 6.9.0
- Platform/OS: Raspberry Pi 3B+ / Raspbian Stretch 9.6
- Browser: MS Edge, Google Chrome on PC and Android

---

<div class="post-metadata">

**Author:** ![igrowing](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/igrowing/32/663_2.png) [@igrowing](https://discourse.nodered.org/u/igrowing)\
**Post date:** [28 September 2019 10:06 UTC](https://discourse.nodered.org/t/dashboard-error-connection-lost/7965/47 "2019-09-28T10:06:40Z")

</div>

Sorry for raising this topic again. This thread is closest to what I experience among all "Connection Lost" threads in this forum.

The setup:

```auto
              /--- Cellphone
RPi --- Proxy --- PC
     \ \-- Tablet
       \
        +-- Cellphone
        +-- PC
        +-- Tablet  

```

As presented in the chart above, Node-RED Dashboard can be accessed from devices inside the LAN, or from the Internet via reverse proxy.  
Connecting with PC works always both ways.  
Connecting with Android based cellphone (samsung) works always from LAN, and almost always via the Proxy.  
Connecting with cheap Android tablet works always from LAN, and rarely via the Proxy.  
When not connecting, the "Connection lost" pop up appears on the screen, and repeating endlessly.

Proposed here solution with Chrome flags doesn't work: in modern Chrome there are not such flags on all types of devices.  
In parallel thread it was recommended to reduce number of charts, controls, and data in the dashboard. This makes no sense to me: the Dashboard exists for rich content to be presented.  
Maybe the "Connection lost" pop up appears due to some kind of timeout?  
If so, how the timeout can be prolonged, letting the page more time to load?

Thank you.

---

<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:** [28 September 2019 14:48 UTC](https://discourse.nodered.org/t/dashboard-error-connection-lost/7965/48 "2019-09-28T14:48:04Z")

</div>

> [@igrowing](#):
>
> This makes no sense to me: the Dashboard exists for rich content to be presented.

Actually, the Dashboard exists to make a really simple to enter web ui possible for non-programmers. Under the skin, it is extremely complex and bulky. In the beginning it rarely even worked with mobile browsers but Dave has done a sterling job of speeding it up.

> [@igrowing](#):
>
> Maybe the "Connection lost" pop up appears due to some kind of timeout?

Most probably.

> [@igrowing](#):
>
> If so, how the timeout can be prolonged, letting the page more time to load?

From what I've seen, this is a mobile browser/network issue rather than a setting in Dashboard or Angular - though I'm not expert in that area so I may be wrong.

---

<div class="post-metadata">

**Author:** ![wb666greene](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/wb666greene/32/6534_2.png) [@wb666greene](https://discourse.nodered.org/u/wb666greene)\
**Post date:** [16 September 2021 21:48 UTC](https://discourse.nodered.org/t/dashboard-error-connection-lost/7965/50 "2021-09-16T21:48:53Z")

</div>

I have Version 92.0.4515.131 (Official Build) (64-bit) and neither of these flags are available.

I'm having this issue daily now, a few upgrade cycles ago it was rare.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [17 September 2021 13:28 UTC](https://discourse.nodered.org/t/dashboard-error-connection-lost/7965/51 "2021-09-17T13:28:36Z")

</div>

Since this thread is two years old and so horribly out of date, I suggest you start a new thread explaining your problem.

If you are using charts on the dashboard make sure that you have not got a vast amount of data in the chart (that the browser needs to shuffle down at each sample). Divide the chart timespan in seconds by the interval between samples in seconds to see how many points there are across the chart for each line. It usually doesn't make sense to have more than a few hundred.

I will close this thread as it is out of date.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [17 September 2021 13:28 UTC](https://discourse.nodered.org/t/dashboard-error-connection-lost/7965/52 "2021-09-17T13:28:53Z")

</div>

Closed on 17 September 2021 13:28 UTC



[Previous page](https://discourse.nodered.org/t/dashboard-error-connection-lost/7965.md?page=2)