Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] binhex - SABnzbd

Featured Replies

The docker menu doesn't show 'web ui' option anymore, only 'console', see picture.

You can access the web ui by browsing to the ip:port you configured, but the option is gone?

 

Screenshot 2024-08-08 094440.png

  • Replies 592
  • Views 133k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • @binhex any chance you are going to push the 3.6.1 sabnzbd to docker hub?

  • spencers
    spencers

    I too updated the sabnzbd container today and now i cannot access it. Appears to be same as WonkoTheSane.   2017-05-24 19:40:34,503 DEBG 'sabnzbd' stderr output: 2017-05-24 19:40:34,503::ERRO

  • brawny had the answer in another thread that helped me. put simply, check  Local IPv4 address, under status and interface options (the wrench) in sabnzbd and make sure that they are the sam

Posted Images

Recently had to reboot the server and when everything was back up and running Sabnzbd was not started.  Upon starting I instantly get a Execution Error code 403.  I have search google and the forums but nothing is helping.  I checked the log files and there is nothing that shows an error.  Also my cache drive is not filled, about 150gb free space remaining.  All the log files are small in size as well.  I have tried rebooting the server again but that does not fix the problem.  All of the other dockers are working fine, it's just the binhex-sabnzbd docker that will not start.

Thank you for any help!

Chris

  • Author
17 hours ago, cosmicrelish said:

Recently had to reboot the server and when everything was back up and running Sabnzbd was not started.  Upon starting I instantly get a Execution Error code 403.  I have search google and the forums but nothing is helping.  I checked the log files and there is nothing that shows an error.  Also my cache drive is not filled, about 150gb free space remaining.  All the log files are small in size as well.  I have tried rebooting the server again but that does not fix the problem.  All of the other dockers are working fine, it's just the binhex-sabnzbd docker that will not start.

Thank you for any help!

Chris

try starting the container from the unraid terminal, so type `docker start <name of container>' and see what the error says, my money is that its a port conflict.

  • 3 months later...

HI, I am using the Container without VPN.

My question is about folders.

 

How can I separate downloaded content from Configurations?

 

I don´t get how to set this up. I have defined "Host Path 2" as: "/mnt/user/download/usenet", where it is supposed to store the downloaded content, however, it seems that the correct Variable is "/config".

But there the standard Path is appdata and everything, including downloads, will be stored there. So, I now have changed this path to my "/mnt/user/download/usenet", but now it generates metadata here. Which I don´t want.

 

-> How can I keep the metadata in the appdata folder AND have my downloads in my Share?

 

  • 2 weeks later...

I'm now getting a message "This site can’t be reached" when trying to pull up the web UI.  Also, other applications like sonarr are unable to connect to it.  This has worked for years and I cannot find anything to indicate why it is not responding on that address.  The docker page of Unraid says that it is started.

 

6 days later it started working - but 3 other dockers web UI stopped working.  They all show as started, but I don't think they are working.  Plex, for example, is not responding to Plex players on the network.

Edited by jtcweb

Hi

I can no longer access the webui for Sabnzdb.  I just get:

This site can’t be reached

192.168.1.10 refused to connect.

I istalled the Unifi Controller docker which used the same port, so I changed Sab from 8080 and that may have caused the problem, not sure.

I have since deleted Unifi and changed Sab back to 8080 but now I have the problem....  

Anyone able to offer any advice?

THX

40 minutes ago, Exsol said:

changed Sab back to 8080

And how did you change it? 

 

Hey mate

I changed it in the template (?).  

 

image.thumb.png.792070e79c0002c21f6f57d3191ca655.png

 

 

From the log, not sure if it helps:

 

024-12-15 22:06:03.937443 [info] Host is running unRAID
2024-12-15 22:06:04.140998 [info] System information: Linux f2783a8a370e 6.1.106-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 21 23:36:07 PDT 2024 x86_64 GNU/Linux
2024-12-15 22:06:04.574866 [info] Image tags: BASE_RELEASE_TAG=2024110703,IMAGE_RELEASE_TAG=4.4.0-1-01
2024-12-15 22:06:04.831222 [info] PUID defined as '99'
2024-12-15 22:06:05.606871 [info] PGID defined as '100'
2024-12-15 22:06:06.401215 [info] UMASK defined as '000'
2024-12-15 22:06:06.715007 [info] Permissions already set for '/config'
2024-12-15 22:06:07.044151 [info] Deleting files in /tmp (non recursive)...
2024-12-15 22:06:07.883555 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no'
2024-12-15 22:06:08.147273 [info] Starting Supervisor...
2024-12-15 22:06:09,514 INFO Included extra file "/etc/supervisor/conf.d/sabnzbd.conf" during parsing
2024-12-15 22:06:09,517 INFO Set uid to user 0 succeeded
2024-12-15 22:06:09,523 INFO supervisord started with pid 6
2024-12-15 22:06:10,526 INFO spawned: 'start-script' with pid 59
2024-12-15 22:06:10,527 INFO reaped unknown pid 7 (exit status 0)
2024-12-15 22:06:11,538 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-12-15 22:06:12,718 DEBG 'start-script' stderr output:
/home/nobody/start.sh: line 10:    61 Illegal instruction     python3 "${install_path}/SABnzbd.py" --config-file /config --server 0.0.0.0:8080 --https 8090

2024-12-15 22:06:12,731 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22758683520672 for <Subprocess at 22758670956976 with name start-script in state RUNNING> (stdout)>
2024-12-15 22:06:12,731 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22758669306672 for <Subprocess at 22758670956976 with name start-script in state RUNNING> (stderr)>
2024-12-15 22:06:12,731 WARN exited: start-script (exit status 132; not expected)
2024-12-15 22:06:12,732 DEBG received SIGCHLD indicating a child quit

Edited by Exsol
added info

I just keep trying it hoping that it fixed itself.  No luck so far....

  • Author
25 minutes ago, Exsol said:

I just keep trying it hoping that it fixed itself.  No luck so far....

what is the URL you are going to in your web browser?, if you are left clicking the docker container and selecting web ui it is possible its sending you to the wrong port number.

Hi there binhex

I am left clicking the docker container ant this is my browser:

 

image.thumb.png.920452e35181e53880dea8cefa6f4cca.png

  • Author

ok the url looks correct, can you try another browser and also try an incognito window.

I tried a Brave private window, Edge and Edge private.

I should also mention that that I tried removing and reinstalling the docker... no joy.  Thanks for jumping in here.

 

image.thumb.png.6727dc89a3bf2c594c9c5b9caf4b4dc0.png

  • Author
59 minutes ago, Exsol said:

I tried a Brave private window, Edge and Edge private.

I should also mention that that I tried removing and reinstalling the docker... no joy.  Thanks for jumping in here.

 

image.thumb.png.6727dc89a3bf2c594c9c5b9caf4b4dc0.png

OK i know this sounds a bit straw grasping here, but give your server a reboot, it wouldnt be the first time ive seen docker get its knickers in a knot after a port change.

p.s. i have confirmed the image is working, so the issue is local to your setup.

Rebooted and no joy, unfortunately.

I automatically assumed the problem was at my end.  I have this knack of being the first person to experience weird problems that nobody has seen before...

As I am new to UnRaid and dockers, is there a way to reinstall the docker completely from scratch?  

  • Author
30 minutes ago, Exsol said:

Rebooted and no joy, unfortunately.

I automatically assumed the problem was at my end.  I have this knack of being the first person to experience weird problems that nobody has seen before...

As I am new to UnRaid and dockers, is there a way to reinstall the docker completely from scratch?  

there are two steps you can try:-

 

1. re-configure the template - to do this stop the container then left click and select 'remove' and confirm it. then at the bottom click on 'add container' and then from the 'template' select the sabnzbd template from the first section, do not select anything under 'user templates', fill in the details and apply.

 

If step 1. doesn't fix it then go onto step 2.:-
 

2. re-create your config - to do this stop the container, then locate your /config folder for the container on your host and rename the folder name e.g. binhex-sabnzbd-old then start the container, this will create a brand new configuration in the original location.

 

Step 1. I Stopped and removed the container.  When I went to 'add container', it wasn't available in the top sction.  Very little was, in fact:

image.png.31fa5d70312353d7d88066c02eb491fe.png

 

So I had to choose from the User Templates and go to step 2.  I feel awful having to say that still no joy:

image.png.c5e0c3f0b76432da9e1cfb3221d4abc5.png

 

All other dockers work as they should. It is just this one and this is the only one I messed with when I tried Unifi but all I did was change the port number.

Should I be worried about this line in the log:

2024-12-16 22:53:30,826 DEBG 'start-script' stderr output:
/home/nobody/start.sh: line 10:    63 Illegal instruction     python3 "${install_path}/SABnzbd.py" --config-file /config --server 0.0.0.0:8080 --https 8090

 

And what does a child quitting mean?  That can't be good...

2024-12-16 22:53:30,828 DEBG received SIGCHLD indicating a child quit

 

 

FYI, I would love to know why this happened and how o fix it because I suspect that I will do it again to another docker at some point but in the meantime, I have installed binhex-nzbget and it is currently working for me.

Thanks for trying binhex and please do let me know if you come up with any other ideas to try.

Cheers

Last night Sabnzbd paused itself for the first time. I checked the logs and there was an error that my quota limit was reached and it was pausing. I went into config/switches and changed it to 100TB/day and it still hasn't restarted. I have over 40TB of storage left on the array so it's got plenty of space. I used the 'force' priority and they still won't begin downloading. Any idea what other quota there is that could be causing this paused state?

Usenet quota?  Did you put a value in config Servers > Quota?

 

Also, is it possible that you have a quota (daily limit) for you Usenet hosting, which might be hit and reported by SABnzbd?

When enabling tailscale (in unraid 7 rc2) it breaks this docker:

 


Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2024-12-27 20:42:27.848045 [info] Host is running unRAID
2024-12-27 20:42:27.875767 [info] System information: Linux ad87d6021abb 6.6.66-Unraid #1 SMP PREEMPT_DYNAMIC Mon Dec 16 16:09:03 PST 2024 x86_64 GNU/Linux
2024-12-27 20:42:27.903309 [info] Image tags: BASE_RELEASE_TAG=2024110703,IMAGE_RELEASE_TAG=4.4.1-1-01
2024-12-27 20:42:27.934835 [info] PUID defined as '99'
2024-12-27 20:42:27.986736 [info] PGID defined as '100'
2024-12-27 20:42:28.031544 [info] UMASK defined as '000'
2024-12-27 20:42:28.061737 [info] Permissions already set for '/config'
2024-12-27 20:42:28.093931 [info] Deleting files in /tmp (non recursive)...
2024-12-27 20:42:28.184223 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no'
2024-12-27 20:42:28.212182 [info] Starting Supervisor...
2024-12-27 20:42:28,418 INFO Included extra file "/etc/supervisor/conf.d/sabnzbd.conf" during parsing
2024-12-27 20:42:28,418 INFO Set uid to user 0 succeeded
2024-12-27 20:42:28,422 INFO supervisord started with pid 240
2024-12-27 20:42:29,424 INFO spawned: 'start-script' with pid 293
2024-12-27 20:42:29,424 INFO reaped unknown pid 241 (exit status 0)
2024-12-27 20:42:29,509 DEBG 'start-script' stdout output:
Not all required Python modules are available, please check requirements.txt
Missing module: sabctools
You can read more at: https://sabnzbd.org/wiki/installation/install-off-modules
If you still experience problems, remove all .pyc files in this folder and subfolders

2024-12-27 20:42:29,510 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-12-27 20:42:29,519 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23088742217920 for <Subprocess at 23088742213552 with name start-script in state RUNNING> (stdout)>
2024-12-27 20:42:29,519 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23088740811152 for <Subprocess at 23088742213552 with name start-script in state RUNNING> (stderr)>
2024-12-27 20:42:29,519 WARN exited: start-script (exit status 1; not expected)
2024-12-27 20:42:29,519 DEBG received SIGCHLD indicating a child quit

 

simply unchecking tailscale fixes this issue. Seems like sabctools is no longer present when enabling TS?

  • 4 weeks later...

I have mapped my 8080 port -> 6789 to avoid a conflict with qbittorent, but it still runs on 8080.  When I look at the details I see:

 

image.png.08776c42bd852c47558b8f4fb6dda8f8.png

 

8080 does indeed work, but why isn't it 6789 instead?

 

image.png.4d8214c03a1c8a337e592fb930c9f626.png

 

 

My fix was to move qbittorrent instead and that works perfectly.  Seems something is broken with this docker.

Edited by lovingHDTV

  • Author
3 hours ago, lovingHDTV said:

Seems something is broken with this docker.

not at all, you just dont understand port mappings in docker, because this is running via 'bridge' network you only need to change the host port, the container port is left unchanged (and is hard coded in this case), this allows you run multiple containers as long as the host port is unique.

My network type is None as I run it through GlueTun or are you referring to a different network called bridge?

  • Author
5 minutes ago, lovingHDTV said:

My network type is None as I run it through GlueTun or are you referring to a different network called bridge?

The default network type for this container is the default docker 'bridge' as can be seen in the unraid template, in this mode it works as i previously described.

 

If you are running this via a shared network such as gluetun or a vpn network from one of the vpn images i produce then you may then run into a container port clash if you have more than one container running on the same port inside of the shared network.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.