Waiting for missing types to be registered (Docker)

General
1

I have just loaded node-red this evening and the GUI has stil not loaded on the xxx.xxx.xxx.xxx:1880 page

image
image.png1913Ă—922 14.9 KB

20 Oct 19:46:31 - [info] Node-RED version: v1.0.2
20 Oct 19:46:31 - [info] Node.js version: v10.16.3
20 Oct 19:46:31 - [info] Linux 5.0.0-31-generic x64 LE
20 Oct 19:46:32 - [info] Loading palette nodes

the flows have now also stopped:

20 Oct 19:46:54 - [info] Server now running at http://127.0.0.1:1880/

20 Oct 19:50:45 - [info] Stopping flows
20 Oct 19:50:45 - [info] Stopped flows
20 Oct 19:50:45 - [info] Waiting for missing types to be registered:
20 Oct 19:50:45 - [info] - alexa-remote-sequence
20 Oct 19:50:45 - [info] - alexa-remote-get
20 Oct 19:50:45 - [info] - alexa-remote-set

i have tried restarting the docker container and still nothing

any ideas please?

2

Clear your browser cache.
try a other browser.

3

have tried that, and i get the same in FF, Chrome and even edge.

that was what i orignally assumed it was.

4

You are missing some nodes

20 Oct 19:50:45 - [info] Waiting for missing types to be registered:
20 Oct 19:50:45 - [info] - alexa-remote-sequence
20 Oct 19:50:45 - [info] - alexa-remote-get
20 Oct 19:50:45 - [info] - alexa-remote-set

you need to install the node that these come from.

Is this your flow or are you running a flow from someone else?

5

these are all mine and have been running fine for months, those are missing nodes from a dead flow i had forgotten about, where I did not change the nodes when Alexa palette I was using updated, have been searching through old JSON files - was an old version of node-red-contrib-alexa-remote2

6

If you start node-red from the command line, you can use the --safe option which will allow you to enter the editor and delete the nodes and then deploy and see if your dashboard appears

7

i am running this is docker, so not sure how to do that :flushed:

8

You could try the suggestion @bakman2 made in this thread Flows have disappeared!

9

edited title.

node-red in docker cannot easily run in safe mode.

I see a discussion that the safe mode will be exposed to the environment variables, should have been implemented.

If possible, run node-red natively, it simplifies certain things.

10

If you are using 1.0.2 then the necessary fix for safe mode in docker is there as per the node-red docker readme

1 Like
11

thanks all, the page has finally uploaded, i would like to day it was something i did, but it happened while i was cooking dinner.

However it isnow not holding a server setting for home assistant

20 Oct 21:21:51 - [info] Waiting for missing types to be registered:
20 Oct 21:21:51 - [info] - server
20 Oct 21:23:18 - [warn] Credential type 'server' is not registered
20 Oct 21:23:18 - [info] Stopping flows
20 Oct 21:23:18 - [info] Stopped flows
20 Oct 21:23:18 - [info] Waiting for missing types to be registered:
20 Oct 21:23:18 - [info] - server
20 Oct 21:26:15 - [warn] Credential type 'server' is not registered
20 Oct 21:26:15 - [info] Stopping flows
20 Oct 21:26:15 - [info] Stopped flows
20 Oct 21:26:15 - [info] Waiting for missing types to be registered:
20 Oct 21:26:15 - [info] - server

12

Start it in safe mode again and go to the 'config' tab on the sidebar. List what you are seeing.