# NETDATA go.d plugin is bound to all tcp ports. **URL:** \ **Category:** Help\ **Created:** [April 8, 2023, 2:19pm UTC](https://community.netdata.cloud/t/netdata-go-d-plugin-is-bound-to-all-tcp-ports/4049 "2023-04-08T14:19:07Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![George\_Li](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/george_li/32/2758_2.png) [@George\_Li](https://community.netdata.cloud/u/George_Li)\ **Post date:** [April 8, 2023, 2:19pm UTC](https://community.netdata.cloud/t/netdata-go-d-plugin-is-bound-to-all-tcp-ports/4049/1 "2023-04-08T14:19:07Z")
I have Netdata installed on a windows sever 2019 server via UBUNTU wsl. It works perfectly and is very reliable in terms of uptime, however over time, the go.d plugin binds to all availble TCP ports, preventing the server from creating new connections. netstat -qno shows all TCP ports BOUND. Is there anyway to restrict the plugin to a certain number of ports? Why does it need to connect to ports? Any help will be greatly appreciated. ---
**Author:** ![Christopher\_Akritid1](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/christopher_akritid1/32/419_2.png) [@Christopher\_Akritid1](https://community.netdata.cloud/u/Christopher_Akritid1)\ **Post date:** [April 11, 2023, 1:31pm UTC](https://community.netdata.cloud/t/netdata-go-d-plugin-is-bound-to-all-tcp-ports/4049/2 "2023-04-11T13:31:41Z")
The go.d plugin does not bind itself to any ports to listen. It will use a single port for each job though (e.g. if you check an http endpoint liveness/latency, obviously it will need to open a connection to it). I can imagine a condition where Netdata autodetects hundreds of things it can monitor and tries to query all of them, but I’ve never heard of such a case before. Please provide more info on your set up, monitored services and Netdata version and install method. ---
**Author:** ![Christopher\_Akritid1](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/christopher_akritid1/32/419_2.png) [@Christopher\_Akritid1](https://community.netdata.cloud/u/Christopher_Akritid1)\ **Post date:** [April 11, 2023, 1:32pm UTC](https://community.netdata.cloud/t/netdata-go-d-plugin-is-bound-to-all-tcp-ports/4049/3 "2023-04-11T13:32:34Z")
This is tracked in > > > \### Bug description > > The go.d plugin process is using up all available TCP ports… and is showing as BOUND when queried using netstat -qno. > > > \### Expected behavior > > Restrict go.d to using to specific or limited number of ports > > \### Steps to reproduce > > Installed on windows server 2019 in wsl. > > > \### Installation method > > from git > > \### System info > > \`\`\`shell > /etc/lsb-release:DISTRIB\_ID=Ubuntu > /etc/lsb-release:DISTRIB\_RELEASE=20.04 > /etc/lsb-release:DISTRIB\_CODENAME=focal > /etc/lsb-release:DISTRIB\_DESCRIPTION="Ubuntu 20.04.6 LTS" > /etc/os-release:NAME="Ubuntu" > /etc/os-release:VERSION="20.04.6 LTS (Focal Fossa)" > /etc/os-release:ID=ubuntu > /etc/os-release:ID\_LIKE=debian > /etc/os-release:PRETTY\_NAME="Ubuntu 20.04.6 LTS" > /etc/os-release:VERSION\_ID="20.04" > /etc/os-release:VERSION\_CODENAME=focal > /etc/os-release:UBUNTU\_CODENAME=focal > \`\`\` > > > \### Netdata build info > > \`\`\`shell > Version: netdata v1.38.0-301-nightly > Configure options: '--build=x86\_64-linux-gnu' '--includedir=${prefix}/include' '--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' '--disable-silent-rules' '--libdir=${prefix}/lib/x86\_64-linux-gnu' '--libexecdir=${prefix}/lib/x86\_64-linux-gnu' '--disable-maintainer-mode' '--prefix=/usr' '--sysconfdir=/etc' '--localstatedir=/var' '--libdir=/usr/lib' '--libexecdir=/usr/libexec' '--with-user=netdata' '--with-math' '--with-zlib' '--with-webdir=/var/lib/netdata/www' '--disable-dependency-tracking' 'build\_alias=x86\_64-linux-gnu' 'CFLAGS=-g -O2 -fdebug-prefix-map=/usr/src/netdata=. -fstack-protector-strong -Wformat -Werror=format-security' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro' 'CPPFLAGS=-Wdate-time -D\_FORTIFY\_SOURCE=2' 'CXXFLAGS=-g -O2 -fdebug-prefix-map=/usr/src/netdata=. -fstack-protector-strong -Wformat -Werror=format-security' > Install type: binpkg-deb > Binary architecture: x86\_64 > Packaging distro: > Features: > dbengine: YES > Native HTTPS: YES > Netdata Cloud: YES > ACLK: YES > TLS Host Verification: YES > Machine Learning: YES > Stream Compression: YES > Libraries: > protobuf: YES (system) > jemalloc: NO > JSON-C: YES > libcap: NO > libcrypto: YES > libm: YES > tcalloc: NO > zlib: YES > Plugins: > apps: YES > cgroup Network Tracking: YES > CUPS: YES > EBPF: YES > IPMI: YES > NFACCT: YES > perf: YES > slabinfo: YES > Xen: NO > Xen VBD Error Tracking: NO > Exporters: > AWS Kinesis: NO > GCP PubSub: NO > MongoDB: NO > Prometheus Remote Write: YES > Debug/Developer Features: > Trace Allocations: NO > \`\`\` > > > \### Additional info > > \_No response\_ ---
**Author:** ![George\_Li](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/george_li/32/2758_2.png) [@George\_Li](https://community.netdata.cloud/u/George_Li)\ **Post date:** [April 11, 2023, 11:43pm UTC](https://community.netdata.cloud/t/netdata-go-d-plugin-is-bound-to-all-tcp-ports/4049/4 "2023-04-11T23:43:30Z")
Thank you Chris, I will attempt to recreate the issue again when the server has a moment of downtime again.