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

**URL:** <https://discourse.nodered.org/t/docker-logging-says-node-red-server-now-running-at-but-i-cannot-reach-it-with-browser/69072>\
**Category:** General\
**Tags:** docker\
**Created:** [15 October 2022 16:23 UTC](https://discourse.nodered.org/t/docker-logging-says-node-red-server-now-running-at-but-i-cannot-reach-it-with-browser/69072 "2022-10-15T16:23:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vennis](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/vennis/32/69230_2.png) [@Vennis](https://discourse.nodered.org/u/Vennis)\
**Post date:** [15 October 2022 16:23 UTC](https://discourse.nodered.org/t/docker-logging-says-node-red-server-now-running-at-but-i-cannot-reach-it-with-browser/69072/1 "2022-10-15T16:23:08Z")

</div>

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/](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?

---

<div class="post-metadata">

**Author:** ![LosinIt](https://avatars.discourse-cdn.com/v4/letter/l/439d5e/32.png) [@LosinIt](https://discourse.nodered.org/u/LosinIt)\
**Post date:** [15 October 2022 20:02 UTC](https://discourse.nodered.org/t/docker-logging-says-node-red-server-now-running-at-but-i-cannot-reach-it-with-browser/69072/2 "2022-10-15T20:02:03Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![janvda](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/janvda/32/234_2.png) [@janvda](https://discourse.nodered.org/u/janvda)\
**Post date:** [16 October 2022 21:26 UTC](https://discourse.nodered.org/t/docker-logging-says-node-red-server-now-running-at-but-i-cannot-reach-it-with-browser/69072/3 "2022-10-16T21:26:19Z")

</div>

> [@Vennis](#):
>
> I cannot make it work to connect to the Node Red server with my browser but I can connect to the servers console.

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 ?

---

<div class="post-metadata">

**Author:** ![Vennis](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/vennis/32/69230_2.png) [@Vennis](https://discourse.nodered.org/u/Vennis)\
**Post date:** [17 October 2022 06:23 UTC](https://discourse.nodered.org/t/docker-logging-says-node-red-server-now-running-at-but-i-cannot-reach-it-with-browser/69072/4 "2022-10-17T06:23:28Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![janvda](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/janvda/32/234_2.png) [@janvda](https://discourse.nodered.org/u/janvda)\
**Post date:** [17 October 2022 06:48 UTC](https://discourse.nodered.org/t/docker-logging-says-node-red-server-now-running-at-but-i-cannot-reach-it-with-browser/69072/5 "2022-10-17T06:48:10Z")

</div>

> [@Vennis](#):
>
> No, I cannot reach the host over port 1880. That is the problem.  
> Regards

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

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

```auto
 sudo lsof -i -P -n | grep LISTEN | grep 1880

```

---

<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:** [16 December 2022 06:48 UTC](https://discourse.nodered.org/t/docker-logging-says-node-red-server-now-running-at-but-i-cannot-reach-it-with-browser/69072/6 "2022-12-16T06:48:27Z")

</div>

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