IP Address Binding with Multiple NIC's

Help & Support
1

Hey

I originally joined the forum today to seek help on an issue regarding the webui and being unable to connect to it using the bound IP address. I was still able to connect using localhost.

After some testing I believe I may have found an issue using multiple NIC’s within the the host machine and/or changing the Sonarr NIC after install.

I recently installed a second NIC and diverted all my traffic over this NIC whilst changing the IP address ranges. Using this NIC and changing the bound IP address within Sonarr config I was unable to access the webui using 192.168.xxx.xxx:port but could access it using localhost:port.

Using netstat and currport I determined the ports were listening however I was unable to establish a connection both from the host machine and remote machine webui’s.

Unable to resolve this issue I returned all the traffic to NIC 1 (eth0) using the updated IP addresses that I implemented above and the webui came back to life using 192.168.xxx.xxx:port.

Moving from NIC 1 (eth0) to NIC 2 (eth1) appears to have left the Sonarr application connected to eth0 despite changing the IP binding address.

Everything is back up and running now just on the original NIC.

I am unsure if anyone is aware of this and thought I would share my findings with the community. If anyone needs more information please let me know.

Cheers
Zhi

Edited: I should add the host is Windows 8.1

2

I have this same issue. I wanted to change to port 80 on a multi nic system. I’m running SAB on port 80 on another NIC on the host. When I change the binding to 80 it won’t start because of a conflict.
It turns out the Sonarr service still runs on every nic in the system, just only responds on the NIC specified. Don’t know if this is a bug or not.

3

Unfortunately this is a limitation of the webserver that Sonarr uses, at this time there is not a viable workaround.

1 Like
4

Thanks for the update Markus. Appreciate the response.

5

One thing I did to work around a similar issue was to use nginx as the front-end web server and proxy-pass through to Sonarr.

I have Sonarr configured to listen on port 8988 for ip address 127.0.0.1 ( I just moved the port so I could reuse the standard port in nginx).

I then run nginx on the same system listening on port 8989 for all ip addresses. It simply has a proxy_pass to the Sonarr port on port 8988, but I do not send the Host header as that caused Sonarr’s web server to try and resolve the host binding and re-introduce the original problem.

As an example, basic nginx config (without any other settings that anyone might want, like connection timeouts, listening on other ports such as for ssl, etc.) is:

server {
listen 8989;
location / {
proxy_pass http://127.0.0.1:8988/;
}
}

Seems to work so far.

I am not however using multiple nics, but I do have multiple IP addresses that I use to access the same service (localhost, 0.0.0.0, 192.168…, 172,…, and a public IP address). Seems to work ok for now.

A side-effect of this is if you happen to have a public IP address, nginx can also handle your SSL cert (letsencrypt.org if for some unknown reason you don’t have your free SSL cert yet) and proxy-pass through to the non-ssl Sonarr port.

6

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.