BUG: Reachability WARN and Nyx ConnectionTracker error on Debian 12 (Docker Host Mode)

[demolayy]

Issue Description:

Environment:

OS: Debian 12 (Bookworm)

Provider: IONOS VPS (Germany)

Torware Version: Latest (Running Tor 0.4.8.10)

Network Mode: Host

The Problem:
Despite the ORPort (9001) being confirmed as OPEN via external testing (curl telnet://IP:9001) and the network interface (ens6) showing high traffic volume (~150GB RX/TX), the Tor process inside the container continuously logs reachability warnings.

Logs & Errors:

Tor Reachability Warn:

[warn] Your server has not managed to confirm reachability for its ORPort(s) at 217.160.49.192:9001. Relays do not publish descriptors until their ORPort and DirPort are reachable.

Plaintext

Nyx ConnectionTracker Bug:

[NYX_NOTICE] BUG: Unexpected exception from ConnectionTracker: "getpwnam(): name not found: 'tor'"

Version Obsolescence:
The authorities are flagging version 0.4.8.10 as obsolete.

Observations:

Nyx running as root on the host cannot map connections to the 'tor' user inside the container, resulting in empty traffic graphs.

The docker stats command shows 0B / 0B for Net I/O due to the --network host configuration, making it difficult to monitor health without external tools.

Requested Fix/Update:

Please update the Torware image to the latest stable Tor version (0.4.8.21+ or 0.4.9.x) to clear the obsolescence flag.

Investigate why the containerized Tor fails its self-reachability test on certain cloud providers (like IONOS) even when the port is demonstrably open.

Fix the Nyx user-mapping bug to allow real-time traffic visualization on the host.