Greetings,
I have been using SAB for several years now with nearly zero issues. However, about a month ago, my shows stopped updating. I am running the program on a QNAP TS-419P+ NAS. When I attempt to access the web interface, I get a screen that says connection refused. I decided to uninstall the software and update to the newest version from this April. After updating, I went through the menus and got everything set up again. I went to bed last night and this morning it's back to the same connection refused screen and I am unable to access the web interface again. I tried removing and reinstalling everything again, and this time, I added a user/pass. An hour later the connection was refused again.
Any ideas?
Thanks.
Connection Refused from QNAP NAS
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Connection Refused from QNAP NAS
Which browser?
What is the exact, full error message?
Which URL do you use?
Can you login on your QNAP (via management tool / GUI?) and see if SABnzbd is running at all?
What is the exact, full error message?
Which URL do you use?
Can you login on your QNAP (via management tool / GUI?) and see if SABnzbd is running at all?
Re: Connection Refused from QNAP NAS
I'm using Chrome. Never caused a problem before...
'This site can’t be reached
192.168.1.X refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED'
I'm using the default port 8800
'This site can’t be reached
192.168.1.X refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED'
I'm using the default port 8800
Re: Connection Refused from QNAP NAS
I can only tell you that it is installed and appears on the App Center page. I will add that Sickbeard/Sickrage are unable to access it.
Re: Connection Refused from QNAP NAS
How did you install your SABnzbd? Which QPKG are you using?
Stuff I like: Apache bash cron DD-WRT Debian DNSMasq Entware FireFox GitHub ImageMagick Kate KDE LibreELEC Netrunner NFS NVIDIA OpenVPN Orvibo-S20 pfSense Python Raspberry-Pi RAID SABnzbd Transmission Usenet VirtualBox Watcher3 XFCE
Re: Connection Refused from QNAP NAS
Sherpa:
https://forum.qnap.com/viewtopic.php?f=320&t=132373
I'm using the version from 4/27/18. This problem began with a very old version that I was using and never had a problem with. I upgraded and it worked briefly, then went back to the same problem.
https://forum.qnap.com/viewtopic.php?f=320&t=132373
I'm using the version from 4/27/18. This problem began with a very old version that I was using and never had a problem with. I upgraded and it worked briefly, then went back to the same problem.
Re: Connection Refused from QNAP NAS
For the record, can you please include your QTS firmware version too? Some of the more recent firmwares appear to be problematic.
Let's confirm SABnzbd is running. SSH into your NAS as the 'admin' user, then:
Also, please check the SABnzbd QPKG log:
Let's confirm SABnzbd is running. SSH into your NAS as the 'admin' user, then:
Code: Select all
ps ax | grep -i sabnzbd | grep -v grep
Code: Select all
cat /var/log/SABnzbdplus.log
Stuff I like: Apache bash cron DD-WRT Debian DNSMasq Entware FireFox GitHub ImageMagick Kate KDE LibreELEC Netrunner NFS NVIDIA OpenVPN Orvibo-S20 pfSense Python Raspberry-Pi RAID SABnzbd Transmission Usenet VirtualBox Watcher3 XFCE
Re: Connection Refused from QNAP NAS
I am using QNAP firmware version 4.3.3.0546. I was thinking that may have triggered the problem.
The first entry produced nothing.
Here is the output from the second entry:
-------------------- start requested --------------------
= Tue May 15 00:55:38 PDT 2018
= (SABnzbdplus) is not active
* updating (SABnzbdplus): OK
Already up to date.
* updating (nzbToMedia): OK
Already up to date.
* starting (SABnzbdplus): OK
-------------------- stop requested --------------------
= Tue May 15 22:46:22 PDT 2018
= (SABnzbdplus) is not active
-------------------- stop requested --------------------
= Tue May 15 22:46:24 PDT 2018
= (SABnzbdplus) is not active
-------------------- start requested --------------------
= Tue May 15 23:16:42 PDT 2018
= (SABnzbdplus) is not active
* updating (SABnzbdplus): OK
Cloning into '/share/MD0_DATA/.qpkg/SABnzbdplus/SABnzbdplus'...
Already up to date.
* updating language support (SABnzbdplus): OK
* updating (nzbToMedia): OK
Already up to date.
* stopping (SABnzbdplus) with SIGTERM: stopped OK in 0 seconds
* starting (SABnzbdplus): OK
-------------------- start requested --------------------
= Tue May 15 23:18:08 PDT 2018
= (SABnzbdplus) is active
* stopping (SABnzbdplus) with SIGTERM: stopped OK in 1 seconds
* starting (SABnzbdplus): OK
-------------------- stop requested --------------------
= Wed May 16 10:40:05 PDT 2018
= (SABnzbdplus) is not active
-------------------- stop requested --------------------
= Wed May 16 10:40:07 PDT 2018
= (SABnzbdplus) is not active
-------------------- start requested --------------------
= Wed May 16 10:41:57 PDT 2018
= (SABnzbdplus) is not active
* updating (SABnzbdplus): OK
Cloning into '/share/MD0_DATA/.qpkg/SABnzbdplus/SABnzbdplus'...
Checking out files: 100% (444/444), done.
Already up to date.
* updating language support (SABnzbdplus): OK
* updating (nzbToMedia): OK
Already up to date.
* stopping (SABnzbdplus) with SIGTERM: stopped OK in 0 seconds
* starting (SABnzbdplus): OK
-------------------- start requested --------------------
= Wed May 16 10:42:59 PDT 2018
= (SABnzbdplus) is active
* stopping (SABnzbdplus) with SIGTERM: stopped OK in 1 seconds
* starting (SABnzbdplus): OK
The first entry produced nothing.
Here is the output from the second entry:
-------------------- start requested --------------------
= Tue May 15 00:55:38 PDT 2018
= (SABnzbdplus) is not active
* updating (SABnzbdplus): OK
Already up to date.
* updating (nzbToMedia): OK
Already up to date.
* starting (SABnzbdplus): OK
-------------------- stop requested --------------------
= Tue May 15 22:46:22 PDT 2018
= (SABnzbdplus) is not active
-------------------- stop requested --------------------
= Tue May 15 22:46:24 PDT 2018
= (SABnzbdplus) is not active
-------------------- start requested --------------------
= Tue May 15 23:16:42 PDT 2018
= (SABnzbdplus) is not active
* updating (SABnzbdplus): OK
Cloning into '/share/MD0_DATA/.qpkg/SABnzbdplus/SABnzbdplus'...
Already up to date.
* updating language support (SABnzbdplus): OK
* updating (nzbToMedia): OK
Already up to date.
* stopping (SABnzbdplus) with SIGTERM: stopped OK in 0 seconds
* starting (SABnzbdplus): OK
-------------------- start requested --------------------
= Tue May 15 23:18:08 PDT 2018
= (SABnzbdplus) is active
* stopping (SABnzbdplus) with SIGTERM: stopped OK in 1 seconds
* starting (SABnzbdplus): OK
-------------------- stop requested --------------------
= Wed May 16 10:40:05 PDT 2018
= (SABnzbdplus) is not active
-------------------- stop requested --------------------
= Wed May 16 10:40:07 PDT 2018
= (SABnzbdplus) is not active
-------------------- start requested --------------------
= Wed May 16 10:41:57 PDT 2018
= (SABnzbdplus) is not active
* updating (SABnzbdplus): OK
Cloning into '/share/MD0_DATA/.qpkg/SABnzbdplus/SABnzbdplus'...
Checking out files: 100% (444/444), done.
Already up to date.
* updating language support (SABnzbdplus): OK
* updating (nzbToMedia): OK
Already up to date.
* stopping (SABnzbdplus) with SIGTERM: stopped OK in 0 seconds
* starting (SABnzbdplus): OK
-------------------- start requested --------------------
= Wed May 16 10:42:59 PDT 2018
= (SABnzbdplus) is active
* stopping (SABnzbdplus) with SIGTERM: stopped OK in 1 seconds
* starting (SABnzbdplus): OK
Re: Connection Refused from QNAP NAS
Yes, 546 is one of the problem builds. I think 516 is still OK (but I don't use these later QTS versions myself).
Then SABnzbd isn't running.
Hmm, there are no 'stop' operations to end each SABnzbd session. This means SABnzbd is exiting due to some other issue (crash, QBoost, QTS, etc...)
The only other thing I can think to check for would be the SABnzbd log (available via the SABnzbd UI), but that would be best interpreted by @sander, @safihre, and the other experienced devs here.
You might look at downgrading your QTS firmware.
Stuff I like: Apache bash cron DD-WRT Debian DNSMasq Entware FireFox GitHub ImageMagick Kate KDE LibreELEC Netrunner NFS NVIDIA OpenVPN Orvibo-S20 pfSense Python Raspberry-Pi RAID SABnzbd Transmission Usenet VirtualBox Watcher3 XFCE
Re: Connection Refused from QNAP NAS
I will first try to downgrade the firmware. I have no real reason to have installed the upgrade, anyhow. Will report back.
Re: Connection Refused from QNAP NAS
Version 513 works! That was it.
Re: Connection Refused from QNAP NAS
Awesome, nicely done.
Stuff I like: Apache bash cron DD-WRT Debian DNSMasq Entware FireFox GitHub ImageMagick Kate KDE LibreELEC Netrunner NFS NVIDIA OpenVPN Orvibo-S20 pfSense Python Raspberry-Pi RAID SABnzbd Transmission Usenet VirtualBox Watcher3 XFCE
Re: Connection Refused from QNAP NAS
And thanks to you!
Re: Connection Refused from QNAP NAS
Came back to it not working again this week. It must just be a matter of time before it starts getting blocked again. Really odd.