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.

SABnzbd questions (needo's docker)

Featured Replies

I've started SAB, but it's not downloading anything now.  It was working yesterday, but not tonight.

 

I'm getting...

 

Server: news.usenetserver.com

 

Status: Enabled

 

# Connections: Failed to connect: (9, 'Bad file descriptor') [email protected]:563

 

which I've not seen before.  I'm not sure that it means, or how to fix it.  I've verified usenetserver is working fine, and they dont' have any network issues.

 

I restarted the SAB docker: no better.

 

I removed the EDGE=1 variable: no better

 

I removed the container, and recreated it: no better.

 

I removed the other SAB docker I had tried (binhex): no better.

 

I changed network setup from bridge to host: no better.

 

I changed it back to bridge: no better.

 

I ran out of ideas of things to try.

 

Suggestions?

 

*Also, can this docker use the EDGE setting?  I really want to move to the latest SAB for a few recent bug fixes, if possible.

I have had this error before I was using Docker.

 

This happened to me once when the Usenet server SSL port 443 was down. I rectified by switching to 563 and everything was up and running again.

 

In your case I am not sure based on your post what the problem is but I would say it is at your Usenet Server end not client end.

 

Also - good isolation test to check. Download a client to your PC / MAC and see if you can connect from there. That could at least eliminate Unraid from the equation.

 

EDIT: If it helps, I am also running this needo Docker with EDGE set to 1 and everything is working fine.

  • Author

This happened to me once when the Usenet server SSL port 443 was down. I rectified by switching to 563 and everything was up and running again.

 

In your case I am not sure based on your post what the problem is but I would say it is at your Usenet Server end not client end.

 

...

 

EDIT: If it helps, I am also running this needo Docker with EDGE set to 1 and everything is working fine.

 

I just tested again when I woke up this morning, and it seemed to connect fine, so I'll chalk it up to usenerserver error.

 

for EDGE; did you just add it under environmental variables as variable = EDGE and value = 1?

 

That's what I had, but I could never get it to actually download/use the latest beta version of SAB.  It just kept on using version 7.2.

 

Am I missing a step, or doing it wrong?

Archived

This topic is now archived and is closed to further replies.

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.