Docker logging says Node-Red 'server now running at ...' but i cannot reach it with browser

General
1

Hey all,
II've been trying to get Node-Red to work via Docker on my Synology NAS for a while now. I use Docker composer for this. My lines in the docker compose file are:

nodered:
container_name: nodered
image: nodered/node-red:latest
restart: unless-stopped
ports:
- 1880:1880
volumes:
- ./volumes/nodered/data:/data

In the log of portainer i see the following:

15 Oct 14:40:26 - [info]
Welcome to Node-RED

===================
15 Oct 14:40:26 - [info] Node-RED version: v3.0.2
15 Oct 14:40:26 - [info] Node.js version: v16.16.0
15 Oct 14:40:26 - [info] Linux 4.4.180+ x64 LE
15 Oct 14:40:31 - [info] Loading palette nodes
15 Oct 14:40:32 - [info] Settings file : /data/settings.js
15 Oct 14:40:32 - [info] Context store : 'default' [module=memory]
15 Oct 14:40:32 - [info] User directory : /data
15 Oct 14:40:32 - [warn] Projects disabled : editorTheme.projects.enabled=false
15 Oct 14:40:32 - [info] Flows file : /data/flows.json
15 Oct 14:40:32 - [info] Creating new flow file
15 Oct 14:40:32 - [warn]

================================
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.

===========================
15 Oct 14:40:32 - [warn] Encrypted credentials not found
15 Oct 14:40:32 - [info] Starting flows
15 Oct 14:40:32 - [info] Started flows
15 Oct 14:40:32 - [info] Server now running at http://127.0.0.1:1880/

My server gets an IP number in a subnet for all other the docker compose servers. Grafana works for as always on the same subnet and can I reach.

I cannot make it work to connect to the Node Red server with my browser but I can connect to the servers console. I'm not familiar enough to find out what is happening wrong.
Can anyone help me to get it working? Can I somehow test the status of the NodeRed Docker? In particlular the Apache webserver?

2

I don't use compose but I have "--network=host" in all my Docker commands that start a container, any container. I suggest you look for the equivalent in your compose files.

3
  1. Can you reach the host machine where node-red docker container is running from the machine where your browser client is running ?
  2. Did you use the following URL: http://<ip address host machine>:1880 to access your node-red editor ?
4

Hello Jan,

1 Yes, I can reach my synology host with various protocols?
2 No, I cannot reach the host over port 1880. That is the problem.
Regards

5

  1. What do you exactly get when trying to open following page in your browser:

    • http://<ip address host machine>:1880

  2. Can you run following command on the docker host machine to check if it is effective listening at port 1880. ?

 sudo lsof -i -P -n | grep LISTEN | grep 1880
6

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