Sonarr version: 2.0.0.5344:
Windows 10 Pro - 18362.592:
I’ve got a bit of an oddsetup (I think).
I have a VM running on a separate machine, Sonarr is running on there.
This machine also has a VPN client running on it.
Everything was working fine locally, and I had it set up so that I could access through the web interface on my main computer. IT worked fine for a couple of weeks.
Today I restarted the VM, and Sonar started throwing up that the port 8989 is already in use.
I’ve checked the forums, and managed to clear the urlacl entry, and was able to user Sonarr again.
I previously was only able to get this working by:
- Running as administrator once.
- Manually adding a firewall rule
- Setting Sonarr’s bind address to the local IP
Running through these again, I’m unable to remotely access (receiving ERR_CONNECTION_TIMED_OUT in the browser).
I’ve noticed that whenever I run Sonarr as Administrator, it recreates the urlacl entry, and prevents me from running unelevated after that, as it gives the port in user warning each time.
I’m unable to run it permanently elevated, as Sonarr can’t access my network shares this way.
I can access the SABnzbd interface remotely without issue, just not Sonarr.
I admittedly don’t really understand what running elevated once actually achieves, and I don’t understand nestsh in any real depth… I figure this lack of understanding is stopping me from making this work again.
If anyone could please advise.
I’ve not pasted logs, because the configuration is all over the place after trying to figure it out, and if you have a clean-slate way of approaching the setup, I’d be most grateful.