-
-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sickbeard adding repeat duplicate nzbs to sabnzbd #1561
Comments
Ubuntu 20.04 uses a pre-alpha version of SAB 3. Anyway: use the PPA of SABnzbd to get a more recent version of SAB 3. Then test again. |
Thanks Sanderjo just mentioning I have the ppa installed and currently using Understood that Sickbeard is very old but its served me well over the years. I have heard of a few alternatives like sickrage but never bothered as sickbeard was working so well. Any other project you would suggest? |
Ps think I found the code spot :), sab.py was expecting a response of ok. I'll try change it... |
Fixed in .sickbeard/sickbeard/sab.py From:
To:
|
You would be better off switching to any of the maintained sickbeard forks |
Thanks Any suggestions before I go and start my research? |
@zeus65 sickchill or sickgear are probably your best bet if you want to stay in the sb family. lots of people switched to sonarr for various other reasons+features that depending on your needs may be better suited. |
For some reason since upgrading to 20.04 ubuntu I notice sickbeard struggles to add nzbs to sabnzbd, It actually does it but for some reason doesn't think the response was correct?
e.g.
2020-07-27 22:38:30 SEARCHQUEUE-BACKLOG-295647 :: Unknown failure sending NZB to sab. Return text is: {'status': True, 'nzo_ids': ['SABnzbd_nzo_fhfyge7e']}
This is causing my sabnzbd to download multiple copies of the same thing.
I even tried to switch the connection to https. That hasn't helped
Just wondering if the sabnzbd response has change or some such?
The text was updated successfully, but these errors were encountered: