SABnzbd Forums

Computer Name "blackred"
Windows Pro x64
Latest build 21H1
Standard hardware
Asus Dark Hero motherboard
Ryzen 9 5950x processor
64GB 3600 memory
2TB WD Black NVMe PCIe 4.0 drives
Asus Strix RTX-3090 OC GPU

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. I also use Sonarr which is http://blackred:8989

I rarely have issues I can't fix myself or at least get some support online. Received the message that 3.3.1 was out. Grabbed it and when I went to install it gave me an error saying please close Sabnzbd.exe first. 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. So I shutdown the service and the install proceeded and finished. Oddly I had to start the service manually myself which I did. Then when I tried to access the UI via computer name:
http://blackred:8080/sabnzbd/
nothing would happen. This was a first. I kept getting
ERR_CONNECTION_REFUSED

So I tried the old school way http://127.0.0.1:8080/sabnzbd/ and that worked fine. So at least I knew SabNZBD was running. I still cannot figure out what is blocking this connection. I checked my Windows 10 (64bit Pro) firewall and Sabnzb was in there to pass on private of course. I even shut down my entire firewall for testing and that had no affect. 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.

If anyone has any suggestions, give me a shout here. I appreciate the help!

By the way, I did check the logs and there is nothing in the Sabnzbd log that shows it was even trying to be accessed. I'll have to check the Windows event viewer to see if I can find something there.

There are some changes in the newest version to reduce the chance of being hacked. See https://sabnzbd.org/access-denied

It should still show up in the log so in your case I think it's a Windows configuration problem. Try finding the firewall configuration for Sonarr and check for differences.

Puzzled wrote: ↑June 28th, 2021, 6:02 am There are some changes in the newest version to reduce the chance of being hacked. See https://sabnzbd.org/access-denied

It should still show up in the log so in your case I think it's a Windows configuration problem. Try finding the firewall configuration for Sonarr and check for differences.

I will check that URL but for testing I turned off my firewall completely and it still did not work. So it must be the changes in 3.3.1 that you are referring to. 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. I tried switching back to the previous version and I'm able to access the UI inside my network just fine via computer name. I never access the UI outside my own LAN, so the setting you are talking about isn't relevant.
Thanks though.

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. At least temporarily. Some kind of DNS issue is not working here. When I ping my server "blackred" it does respond, but only in IPV6.

I even tried another router. My handy Asus router...same results...so I'm doing the ol' school of process of elimination here and so far it boils down to the 3.3.1. I'm surprised no one else has this issue.



Thanks!

I did go back to my other router which is a newer model and has better wireless capabilities. My Sonarr backlog was huge so Sab is still downloading, even with a 1.2GBps download speed it takes time. Looks like my Hydra2 is broken or acting weird too. All because of an update. I'll need to check the readme file or see what was really changed. Hopefully there are specifics in there I can check out.

I apologize for adding all the time, but I figured this would be the best spot to add everything.
My Sonarr URL works great
http://blackred:8989
but what's really weird is the Sab URL does not
http://blackred:8080

Time to dig into my firewall and figure out why port 8080 is not working. Or something else may be trying to scoop it up.

Sounds to me like Sonarr responds to IPv6 and SABnzbd doesn't.

Puzzled wrote: ↑June 29th, 2021, 4:37 pm Sounds to me like Sonarr responds to IPv6 and SABnzbd doesn't.

Maybe a developer can confirm this? I did turn off IPV6 which forced everything to use IPV4 and did not have any effect.

Did you configure SABnzbd to use IPv6? https://sabnzbd.org/wiki/advanced/ipv6

Ok, I have to apologize for anyone that tried to help me out on this one. This was a very stupid mistake on my part. When I installed the 3.3.1 update it changed one thing that I kept overlooking. In the GENERAL section, the very first option. It was set for 127.0.0.1. And all I needed to do was change that to the computer name and it all started working normally. I would have never entered 127.0.0.1 but apparently I did or the install of 3.3.1 update did. I feel like such a dumbass but it happens to the best of us I guess.

Glad you figured it out!

Someone recommended to me to uncheck direct stream?

Sorry what?

safihre wrote: ↑July 1st, 2021, 3:11 am Glad you figured it out!

Well I did not figure it out. After a few Windows updates I cannot access my Sabnzbd server via port 8080 from any machine on my network. Changing the host to the computer name fixed this before, but it is still the computer name but now not working. I ran the Windows diagnostics utility and this is what came back.

This is what Windows said:

resource (blackred) is online but isn't responding to connection attempts. Detected Detected

The remote computer isn’t responding to connections on port 8080, possibly due to firewall or security policy settings, or because it might be temporarily unavailable. Windows couldn’t find any problems with the firewall on your computer.

Well, I checked the firewall of course and made sure the sab executable can pass through and also added port 8080 also. I even added them on incoming AND outgoing as well as private and domain. I thought that would for sure fix it, but here we go again. If definately has something to do with Sabnzbd itself because I can access Sonarr with no problems at all via http://blackred:8989. But when trying to access sabnzbd at http://blackred:8080 nothing. Very strange.

UPDATE: I'm almost embarrassed to post this but I believe I have JUST found the problem. IDIOT me wanted to try Windows 11, so instead of using my beautiful built-in VM capability on my unraid server I downloaded Oracle VirtualBox like a dummy. Need I say more? My power computer that runs all my programs and services has a DHCP reservation, so it will always pick up the same IP address on my network. After you stab me in the eye with a pencil Virtual Box was changing that IP address with some sort of process that was running in memory, so it was picking up a completely different IP. I just tried Hydra, clicked on the sabnzbd icon and all my nice categories showed up like normal. Ok, you can now stick me in my other eye with a blow poke from a fireplace. Sometimes I can miss such the small things and it drives me nuts. As I shake my head back and forth I'm still trying to find a reason why in the world I would ever even use VirtualBox when unraid has all the VM capabilities built right in.
Well, I want to thank all of you who tried to help me and were going to help me. I really do appreciate all the work that's put into this program and how good it runs, even in a docker. Ok, you can now shoot me. If I wasn't so tired I believe I would be beating myself up.