# Cannot connect to Node-Red interface via port 1880 - CC100 **URL:** \ **Category:** Node-RED\ **Created:** [September 15, 2023, 8:40pm UTC](https://www.wago.community/t/cannot-connect-to-node-red-interface-via-port-1880-cc100/600 "2023-09-15T20:40:41Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![bobber\_c](https://avatars.discourse-cdn.com/v4/letter/b/3d9bf3/32.png) [@bobber\_c](https://www.wago.community/u/bobber_c)\ **Post date:** [September 15, 2023, 8:40pm UTC](https://www.wago.community/t/cannot-connect-to-node-red-interface-via-port-1880-cc100/600/1 "2023-09-15T20:40:42Z")
I am trying to use Node-red on my CC100 for a scheduled API trigger, but I simply cannot reach the Node-red interface. - Docker is installed, functional, and running. - FTP and HTTP are both enabled - Routing → IP forwarding is enabled - Ensured correct clock zone and local time settings - DNS 8.8.8.8 and 8.8.4.4 are added The static ip address is set to 192.168.0.153 and pointed to our private server. I used the code ``` docker run -d --name wago-node-red \ -d --privileged=true --user=root \ -p 1880:1880 \ -v node_red_user_data:/data \ nodered/node-red ``` to install Node-red, and it seemed to be successful, because I can run ‘docker container ls’ and see the nodered container information “CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 648c0e8cf4fd nodered/node-red “./entrypoint.sh” 2 hours ago Up 2 hours (healthy) 1880/tcp elastic\_sanderson” But when I go to my browser and enter 192.168.0.153:1880, the connection can’t be established. Running ifconfig returns that 59 packets are being dropped consistently, and when I run ‘docker run nodered/node-red’, it says “15 Sep 20:22:24 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/)” This issue is one a couple other forums online, but I haven’t seen an answer yet. I’m pretty new to programming, so I understand keystrokes and debugging tools better than top-level concepts. ---
**Author:** ![bjornidar](https://avatars.discourse-cdn.com/v4/letter/b/5fc32e/32.png) [@bjornidar](https://www.wago.community/u/bjornidar)\ **Post date:** [September 18, 2023, 7:07am UTC](https://www.wago.community/t/cannot-connect-to-node-red-interface-via-port-1880-cc100/600/2 "2023-09-18T07:07:05Z")
Hi, there are probably neater ways to do it, but I’ve added ```auto --network host ``` to my docker run command ```auto docker run -d --name wago-node-red \ -d --privileged=true --user=root \ -p 1880:1880 \ --network host \ -v node_red_user_data:/data \ nodered/node-red ``` ---
**Author:** ![bobber\_c](https://avatars.discourse-cdn.com/v4/letter/b/3d9bf3/32.png) [@bobber\_c](https://www.wago.community/u/bobber_c)\ **Post date:** [September 18, 2023, 12:33pm UTC](https://www.wago.community/t/cannot-connect-to-node-red-interface-via-port-1880-cc100/600/3 "2023-09-18T12:33:59Z")
Thank you, Bjorn! To make this work, I first used the command docker container prune to remove all of my open non-running docker containers. Then I found and copied the container ID by running ‘docker container ls’ , then ran ‘docker start (paste container id here)’ Now, I am able to access the Nodered interface. ---
**Author:** ![bjornidar](https://avatars.discourse-cdn.com/v4/letter/b/5fc32e/32.png) [@bjornidar](https://www.wago.community/u/bjornidar)\ **Post date:** [September 19, 2023, 7:55am UTC](https://www.wago.community/t/cannot-connect-to-node-red-interface-via-port-1880-cc100/600/4 "2023-09-19T07:55:44Z")
In the future, instead of a prune-command you could do ```auto docker stop docker rm -f ``` Run the modified docker run command. ---
**Author:** ![bobber\_c](https://avatars.discourse-cdn.com/v4/letter/b/3d9bf3/32.png) [@bobber\_c](https://www.wago.community/u/bobber_c)\ **Post date:** [September 21, 2023, 4:29pm UTC](https://www.wago.community/t/cannot-connect-to-node-red-interface-via-port-1880-cc100/600/5 "2023-09-21T16:29:14Z")
Bjorn, thank you for the information, you’ve been a great help. Further progress updates: In this application, the project called for the PLC inside of a panel, calling api missions based on a time of day, and able to handle power outages. For panel application: We used an Antaira AMS-2111 as a client-bridge, and connected the CC100 to that via ethernet in order to connect to the network. For time-based calls: Joe Remisiewicz and Joe Polasek (Wago) were able to point me to the CronPlus module in Node-RED, used as a scheduler for Post requests, which then call missions and adjust PLC registers on a MiR robot. For power outages: I discovered the docker script option ‘–restart always’ and added that to the end of first line of the code snip you gave above when creating my Node-RED container. ```auto docker run -d --name wago-node-red --restart always \ ``` Now, when the CC100 loses power, it takes a little bit of time to boot up and then it begins running the Node-RED flow again. These steps may be old news to most, but it has been a big breakthrough for me! I plan on spending some more R&D time learning how to integrate the PLC I/O in Node-RED so that I can make API calls based on sensor inputs.