My Roon server has a static IP address of.80 on the network.
When I attempt to connect to the server from either the mobile app or my desktop client it attempts to connect to .1 (router address). I’m very technically savvy and have been looking at the Roon server logs.
It appears as though the Roon server is identifying itself as .1 in the logs.
[Brokerserver] client connected 192.168.168.1:49794
On start up there is a trace that says [SOOD] adding user IP 192.168.168.1.
I can then see the individual connections to the RAAT server and it’s saying that my client is attempting to connect to 192.168.168.1:49801
The connection says that it’s failed and then retrying and it does a push connection to 18.104.22.168
There are repeated attempts that all fail.
If I do a search for the actual IP of the Roon server as I have a signed it in the web GUI it doesn’t show up in the logs
If I do a search for the actual IP of the Roon server as I have a signed it in the web GUI it doesn’t show up in the logs.
I have also assigned a static IP to the ethernet Mac address of the Roon nucleus server and again no luck.
I have also enabled Wi-Fi and again no luck.
Throughout this all I can get to the web interface via the IP address that I have a signed however any RAAT connections keep going to the .1 IP address according to the logs and fail.
Additional debugging steps that I have done
- restarted Roon server
- Rebooted nucleus server
- powered down and restarted Roon Nucleus
- unplugged switch
- put Roon to DHCP
- stopped server, renamed database and let Roon create a new database.
- I tried using a different protocol such as SMB and was able to mount the Roon internal hard drive using the correctly assigned static IP address.
- I haven’t done any tests using Telnet to any of the ports indicated in the logs
All of these have no luck. When Roon reboots it goes green with the CORRECT IP address and gives me the button to connect for a split second and then fails
I can intermittently connect to the Roon server from my mobile app 1% of the time then nothing.
So those are the main logs. If I open up the RAAT logs it does indeed show me the correct IP address as I have said it and the RAAT services are resolving to localhost in other words 127.0.0.1
As far as I can tell the root of the problem appears to be that rune is broadcasting it self as a particular IP address that is incorrect and then when my client attempts to connect it’s connecting to the wrong IP address. As far as I can tell the root of the problem appears to be that rune is broadcasting itself as a particular IP address that is incorrect and then when my client attempts to connect it’s connecting to the wrong IP address
I have screenshots logs etc. etc. Please help