When I ping my server "blackred" it does respond, but only in IPV6. Some kind of DNS issue is not working here. Went back to the 3.3.1 version and configured my download client in Sonarr to be 127.0.0.1 instead of the computer name and that seemed to fix it. I never access the UI outside my own LAN, so the setting you are talking about isn't relevant. I tried switching back to the previous version and I'm able to access the UI inside my network just fine via computer name.
Install sonarr in windows 10 vm update#
I'm not having issues getting to the UI, if you re-read my post you'll see I can access the UI fine by using 127.0.0.1 but when I use my computer name, which I would want to since I multiple systems on the same network that is what the 3.3.1 update broke. So it must be the changes in 3.3.1 that you are referring to. I will check that URL but for testing I turned off my firewall completely and it still did not work. Try finding the firewall configuration for Sonarr and check for differences. It should still show up in the log so in your case I think it's a Windows configuration problem. There are some changes in the newest version to reduce the chance of being hacked. I'll have to check the Windows event viewer to see if I can find something there. I appreciate the help!īy the way, I did check the logs and there is nothing in the Sabnzbd log that shows it was even trying to be accessed. If anyone has any suggestions, give me a shout here. I can only guess I'm missing a new feature or option that was in the new version maybe? I even tried to change the port to something else also. I even shut down my entire firewall for testing and that had no affect. I checked my Windows 10 (64bit Pro) firewall and Sabnzb was in there to pass on private of course. I still cannot figure out what is blocking this connection. So I tried the old school way and that worked fine. Then when I tried to access the UI via computer name: Oddly I had to start the service manually myself which I did.
Install sonarr in windows 10 vm install#
So I shutdown the service and the install proceeded and finished. Yea, I knew it was closed and I thought it probably was the service running in the background that was holding files/folders or whatever. Grabbed it and when I went to install it gave me an error saying please close Sabnzbd.exe first. I also use Sonarr which is I rarely have issues I can't fix myself or at least get some support online.
It is just a high end gaming system, which I have several services running on it that barely makes a different if they were there or not.
0 kommentar(er)
