Colin Law

Following retest you are correct, with the latest NR and dashboard the symptom is repeatable on NR restart. I have amended the description. > The very first message does not...

> All of these are behind a reverse proxy that maps hostnames to internal IP addresses Can the reverse proxy map, for example, the domain root to `:1880/dashboard`?

In D2 ui-template the class field is not a typed input, so I can't do that.  There is a workaround, by adding a node in front of the template...

Thanks. For the record, for typed inputs, setting it as Env Var type works, though the syntax is 

The problem is that with npm v7 the peer dependency on the dashboard ^2.23.3 specified in package.json is now treated as an error rather than a warning. A workaround is...

Unfortunately no, it hasn't fixed it. package.json still (in version 0.4.10) includes the lines ``` "peerDependencies": { "node-red-dashboard": "^2.23.3" }, ``` The PR fixes it in devDependencies but not in...

For anyone finding this issue, the workaround till it is fixed is to install using `npm install --legacy-peer-deps node-red-contrib-ui-led`

> How to resolve the issue? Wait for swapi.dev to renew their certificate, or remove that example from the flow.

> we manually attempt to recover dashboard connection using fixed times Can you point to that code please?

There is a subtlety to that code that is not entirely obvious. It actually uses a retry count to determine when to retry. This is important, particularly in the case...