Ports

Ports is an Unraid plugin that provides a scannable view of every Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) listener on your server.

  • Network Services
  • Plugins
  • Security
  • Tools & Utilities
Ports is an Unraid plugin that provides a scannable view of every Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) listener on your server. It attributes each listener to the owning process and Docker container (when applicable), merges duplicate IPv4/IPv6 and TCP/UDP entries into a single line, resolves docker-proxy host-port mappings back to their owning containers, and flags listeners bound to the wildcard address. It is aimed at Unraid users who want to audit what is listening and exposed without parsing netstat output.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

42/100 Fair

Maintained
77last commit 16 days ago
Popular
00 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 4 days ago

GitHub stars
0
Open issues
0
Last commit
2026-11-05
License
MIT
Activity
rising

Checked 4 days ago - source: GitHub (marching-poozer/unraid-port-viewer)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install the Linux serial helper package On Ubuntu, install the libnserial package (the native helper library that lets the app talk to serial ports) using the .deb package file that matches your Ubuntu version. If you skip this or install the wrong version, the app may not find the serial-port support it needs. source
  • Match the port settings to your device Set the serial port's baud rate (speed), data bits, stop bits, parity (error-checking bits), and flow control (handshake) to match the hardware before opening the port. If these don't match, the app may open the port but the data can come out garbled or the device may not respond. source
  • Set buffer sizes before opening the port If you change the receive or transmit buffer sizes (the waiting areas for data), do it before you open the port. If you don't, the app may not use the new sizes and could drop or mis-handle serial data. source
  • Install Install the Ports plugin from Unraid Community Applications; the viewer then appears under Settings → Network Services. source
  • Installing the Plugin Install the Ports plugin from the Unraid Community Applications store. Once installed, it appears under Settings → Network Services in the Unraid web UI. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I install Ports on Unraid?

Install the Ports plugin from Community Applications, or use Settings > Plugins > Install Plugin and paste the plugin URL. It then appears under Settings > Network Services.

Does Ports show only Docker container ports?

No, it shows every TCP and UDP listener on the Unraid server. It also attributes the owning process and Docker container when applicable.

Can I find which Docker container owns a host port?

Yes, it resolves docker-proxy host-port mappings back to the owning container. This includes port ranges and host-network containers.

Will Ports tell me if a listener is exposed beyond the local network?

It flags exposure by distinguishing listeners bound to a wildcard or public address from ones only reachable on the LAN, link-local, or localhost.

Are duplicate entries for IPv4/IPv6 or multiple interfaces shown?

No, it deduplicates identical bindings across interfaces and address families. This keeps multi-homed daemons from cluttering the list.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads