I’ve checked everything:
all my many other server apps work via their web browsers at their ports
port forwarding is correct
in sonarr settings, “binding address”, I have tried both * and the IP address
Any idea why this has stopped working? My server is “headless”, and without the ability to use web browser, I have to use team viewer
I appreciate your response. Amateur mistake: I should’ve mentioned windows 10 pro! Can you elaborate more about what needs to be run as administrator?
It worked before so I don’t know what changed although I did migrate my windows profile several months ago. Still I’m at a loss as to why I can access everything else: from sabnzbd to a half-dozen file/media apps with web interfaces.
Sonarr itself needs to run as Administrator once so it can adjust http urlacl (just run as admin once, then stop it again). Sonarr uses the .net framework http subsystem which in turn uses a windows mechanism that managed permissions on which urls an app can be hosted under. Sonarr needs to reserve ‘http://*:8989’. Consider it a mechanism that verifies who can sell lemonade in front of your house.
The existing reservations can be seen by running ‘netsh show urlacl’. The same cmdline tool can be used to add the appropriate reservations, but Sonarr will do that for you if it runs as Admin.
True, but statistics is not on your side: < 5% of Sonarr instances run on a mac, and a fraction of those (if any at all) uses a Mac as headless server. Compound probabilities
Maybe so, but that’s kinda like telling the lottery winner that they shouldn’t have bothered because the odds were too stacked against them. I happen to be one of those Mac users who sometimes uses teamviewer so…
I clicked the start tile, went to sonarr in the program list, right clicked, selected “run as administrator” which opened the web browser.
I tried that command. I got “The following command was not found: show urlacl.” If I type “show ?” to bring up the help for “show”, it says commands available are alias, helper, mode.
Recently switched your network from private to public perhaps? (you may not have done it intentionally)
The firewall has several profiles: public, private, domain. which allows you to set different rules based on what network you’re on (private lan, public wifi, work etc)
If the profile of your primary network connection changed, then that may have affected which rules applies and could explain what happened.
I doubt it’s the .exe stuff you did since Sonarr doesn’t run from the temp folder.