Mixnode 1.10.0 (Tourist Build) Running but Not Visible on Explorer - API/H2 Warnings

Node Operators Ask for help
1

Hi Nym Community,

I’ve set up a Nym Mix Node and could use some help figuring out why it’s not visible on the explorer and why I’m seeing some persistent API communication warnings in the logs.

Node Details:

  • Node ID (Alias): hxt21
  • Identity Key: E536yNcijJ5NVkiH1s71aXy2NH82bB2KAuBvyYgGsg4J
  • nym-node Version: 1.10.0 (from nym-binaries-v2025.8-tourist, commit SHA: e594630314d4676cbe9bba9ab07bd405a9cf679a)
  • Operating System: Fedora Server (latest version, kernel seems to be 6.11 based on other systems)
  • Bond: 105 NYM

Setup Summary:

  • The node is running as a systemd service under a dedicated non-root user (ebbe).
  • SELinux is Enforcing (initial file context issues like bin_t for the executable have been resolved with restorecon).
  • The server has a static public IP: 87.54.92.12.
  • The Nym node server has two NICs:
    • One for SSH management on an internal network (192.168.1.156/24).
    • One dedicated to Nym traffic (enp5s0) on its own VLAN (192.168.42.42/24), directly connected to the primary UDM-Pro.
  • The Nym interface (enp5s0) is the preferred default route (metric 90).
  • The server’s DNS resolution is configured to use public DNS servers (1.1.1.1, 8.8.8.8) directly via the Nym interface, bypassing internal DNS filters. This has been verified with dig.
  • Port forwarding for TCP 1789 and TCP 1790 is configured on the UDM-Pro from the public IP to the node’s internal IP (192.168.42.42).
  • The local firewall (firewalld on Fedora) allows incoming TCP 1789 & 1790 on the Nym interface (enp5s0) and SSH only on the management interface.
  • The Nym VLAN is isolated from other internal networks using the UDM-Pro’s “Isolate Network” feature and allows internet access.

The Problem: The nym-mixnode systemd service starts successfully and remains active (running). However:

  1. The node has been running for over 9-10 hours but is not visible on any Nym Explorer (neither the old explorer.nymtech.net nor the newer “Spectre Explorer”) when searching by its Identity Key.
  2. The nym-node logs (via journalctl) show the following warnings appearing shortly after startup and potentially periodically (though not in every metrics log line): WARN nym-node/src/node/mod.rs:859: failed to resolve the refresh request: request failed with error message: failed to refresh node description (This appears when trying to contact https://validator.nymtech.net/api/) And sometimes followed by: WARN /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/hickory-proto-0.25.1/src/h2/h2_client_stream.rs:534: h2 connection failed: peer closed connection without sending TLS close_notify...
  3. Despite these warnings, curl -v https://validator.nymtech.net/api/v1/nym-nodes/rewarded-set from the Fedora server itself works fine and returns a 200 OK with JSON data.

My Questions for the Community:

  1. Are these API/H2 warnings known issues with nym-node v1.10.0, especially the “tourist” build (commit e5946303)?
  2. What could be causing these specific API communication warnings and the resulting lack of explorer visibility, given that basic connectivity (ping, dig) and curl tests to the API endpoint work from the server?
  3. Are there other diagnostic steps, specific log levels, or configurations I should check for this node version to ensure it can properly register and communicate its status to the network directory?
  4. Is the “nym-binaries-v2025.8-tourist” build intended for mainnet, or could it be for a specific testnet or require different API endpoints than the default https://validator.nymtech.net/api/?

Any help or pointers would be greatly appreciated! I’m keen to get this Mix Node contributing.

Thanks,

2

check if you have the necessary ports open. 8080 1789 1790

http://87.54.92.12:8080/api/v1/swagger/
can’t open and obviously the validators can’t see your node.

1 Like
3

Screenshot_20250510_095446
Screenshot_20250510_0954461839×955 164 KB

welcome to mixnet!

1 Like