IPv4 Loopback issue?

Sonarr version (exact version): 2.0.0.5239
OS: Windows 10 v1083
Description of issue:
Sonarr has been running fine for months, but now I am suddenly unable to connect to it remotely. I have verified the bind address * and port 8989. I have tried running as Admin, restarting, reinstalling, rebooting, changing ports… Nothing seems to work. I can only access Sonarr on the local machine via 127.0.0.1:8989 or localhost:8989

When checking the port listening under Windows 10 Resource Monitor, port 8989 (or which ever port I change Sonarr to) is listed as being used by ‘System’, and using address IPv4 Loopback. No matter what I do though, I seem unable to change this :frowning:

Enable trace logging, restart Sonarr and post the log file, that’ll log the startup process so we can see what Sonarr sees.

I managed to find a fix:
Running
netsh http add iplisten ipaddress=192.168.0.9
has resolved it. Not sure how this happened or not why, but all is running fine now.

1 Like

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