nfsen-ng ghcr.io/mbolli/nfsen-ng:latest https://github.com/mbolli/nfsen-ng/pkgs/container/nfsen-ng bridge bash false https://github.com/mbolli/nfsen-ng/issues https://github.com/mbolli/nfsen-ng nfsen-ng is a modern, in-place replacement for the ageing NfSen web frontend. It sits on top of the nfdump tools and visualises NetFlow / sFlow / IPFIX traffic with real-time SSE push, a responsive light/dark UI, Sankey traffic-flow diagrams, and RRD or VictoriaMetrics storage. This is the WEB UI. It only displays flow data that a collector has already written to its data directory. Install the companion "nfsen-ng-nfcapd" collector template (or run the bundled Compose stack) and mount BOTH containers on the SAME appdata path so the UI can read what the collector writes. A device on your network (pfSense/OPNsense/MikroTik/…) must export flows to the collector. The app does not terminate TLS by design; front it with SWAG, Nginx Proxy Manager, or Traefik. Network:Management Tools: Status:Stable http://[IP]:[PORT:9000]/ https://raw.githubusercontent.com/mbolli/nfsen-ng/master/deploy/unraid/nfsen-ng.xml https://raw.githubusercontent.com/mbolli/nfsen-ng/master/deploy/unraid/nfsen-ng-icon.png --restart unless-stopped Buy the maintainer a beer https://paypal.me/bolli A NetFlow/sFlow/IPFIX collector must write into the same data directory this container reads. Use the companion nfsen-ng-nfcapd template and point both at the same appdata path (default /mnt/user/appdata/nfsen-ng). Your router/switch must export flows to the collector's UDP port. 9000 /mnt/user/appdata/nfsen-ng UTC flows 80,443,22,53 /data/nfsen-ng /usr/local/nfdump/bin/nfdump INFO 3