· ISP Router is connected to DMZ Network Nginx Proxy Manager (NPM) is connected to DMZ Firewall connects DMZ and LAN Roon Server is connected to LAN ISP Router has DynDNS enabled and forwards any request to NPM Various subdomains are forwarded to NPM and from NPM to the Service connected to LAN
Thank you for reaching out and for the detailed description of your network setup.
After reviewing your configuration, we can see that you have a fairly advanced infrastructure — with a DMZ, Nginx Proxy Manager, and a firewall separating your Roon Server from the rest of the network. While we appreciate the thoroughness of your setup, this type of custom network architecture falls outside the scope of what Roon Support is able to assist with.
Roon is designed to work on a standard local network where the Server and its clients (Remotes and endpoints) can communicate freely via multicast/broadcast. Configurations involving DMZ segments, reverse proxies, and custom firewall rules between network zones can interfere with Roon’s discovery protocols in ways that are difficult for us to diagnose or support remotely.
We recommend consulting with a network specialist who can review your firewall and routing rules directly. You may also find helpful discussion in the Tinkering , where other technically advanced users have shared their experiences with similar setups.