# Not see tcp in port in the server

**URL:** <https://discourse.nodered.org/t/not-see-tcp-in-port-in-the-server/84897>\
**Category:** General\
**Tags:** docker\
**Created:** [25 January 2024 01:10 UTC](https://discourse.nodered.org/t/not-see-tcp-in-port-in-the-server/84897 "2024-01-25T01:10:57Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![iamlaobie](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/iamlaobie/32/87640_2.png) [@iamlaobie](https://discourse.nodered.org/u/iamlaobie)\
**Post date:** [25 January 2024 01:10 UTC](https://discourse.nodered.org/t/not-see-tcp-in-port-in-the-server/84897/1 "2024-01-25T01:10:57Z")

</div>

I want to use "tcp in" create a tcp server using port 8899. After deploy, I can't see the port by netstat command in docker container,How can I connect this port from outside of node-red?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [25 January 2024 01:20 UTC](https://discourse.nodered.org/t/not-see-tcp-in-port-in-the-server/84897/2 "2024-01-25T01:20:12Z")

</div>

Hi, welcome to the forum.

As per my normal recommendation, don't use docker if you don't know how to set it up - instead install node-red on your computer os

Is there a particular reason for using docker?

If you must use docker, you'll have to read up on [opening TCP ports in docker](https://gprivate.com/6920m) 😉

---

<div class="post-metadata">

**Author:** ![iamlaobie](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/iamlaobie/32/87640_2.png) [@iamlaobie](https://discourse.nodered.org/u/iamlaobie)\
**Post date:** [25 January 2024 02:09 UTC](https://discourse.nodered.org/t/not-see-tcp-in-port-in-the-server/84897/3 "2024-01-25T02:09:41Z")

</div>

Thanks for your replying, I know how to map docker port, I just puzzled why I can't see the opened port after deployed the flow include "tcp in" node.  
In my mind, if I use tcp in, the host running node-red will open a tcp port for receive tcp client connecting.

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [25 January 2024 05:19 UTC](https://discourse.nodered.org/t/not-see-tcp-in-port-in-the-server/84897/4 "2024-01-25T05:19:57Z")

</div>

Did you map the port you want to open ?

---

<div class="post-metadata">

**Author:** ![iamlaobie](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/iamlaobie/32/87640_2.png) [@iamlaobie](https://discourse.nodered.org/u/iamlaobie)\
**Post date:** [25 January 2024 05:29 UTC](https://discourse.nodered.org/t/not-see-tcp-in-port-in-the-server/84897/5 "2024-01-25T05:29:15Z")

</div>

No.  
I executed "docker exec -it node-red netstat -an" and didn't show the port.  
run the node-red command directly and can show the tcp in port by netstat

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [25 January 2024 05:40 UTC](https://discourse.nodered.org/t/not-see-tcp-in-port-in-the-server/84897/6 "2024-01-25T05:40:36Z")

</div>

If you don't map the port, it cannot open the port I would think, it will then not show up either. (assuming that the container network is bridged)

---

<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:** [24 April 2024 05:40 UTC](https://discourse.nodered.org/t/not-see-tcp-in-port-in-the-server/84897/7 "2024-04-24T05:40:43Z")

</div>

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