SABnzbd Forums

A couple days ago I started getting this on every download I try (xx sec is some number of seconds):

WAIT xx sec / Trying to fetch NZB from https://[oznzb url]/[SOMEFEEDID]

Same for nzbs.org:

WAIT xx sec / Trying to fetch NZB from http://[nzbs.org url]/[SOMEFEEDID]

I've tried restarting SAB, restarting my server, checked my connection to my usenet provider, nothing fixes this. I tried uploading a nzb file directly, which I haven't done in years, but it didn't work at all... Didn't give me an error, just changed to 'No file chosen' and nothing gets added to the queue. I'm running this on an Ubunutu 12.04 LTS machine. I've seen lots of messages about this issue, but they all say it's a specific issue with the nzb site, and this is happening for me on both of the sites I use for nzbs.

Any ideas? I'm shut down until I can figure this one out...

Thanks!

This is normally caused by an indexing site that uses rate limiting.
Or by one that's incompatible with SABnzbd.
Which one is SABnzbd trying to access?

In this case I'm trying to access both nzbs.org and oznzb.com. I'm a paid member of both, and have used both for several years in SABnzbd without limits. Also would be a bit odd for this to just start happening on BOTH at the exact same time if it were a limit issue...? I believe I hit nzbs.org much more often. I checked my logs and what I see is a long stream of this over and over:

2014-09-03 17:20:22,498::INFO::[urlgrabber:199] Retry URL [SOMEURL]
2014-09-03 17:20:22,498::INFO::[urlgrabber:199] Retry URL [SOMEURL[]

It just repeats that pattern for the same URL every five minutes. So it looks like it's just failing to grab the nzb from the url, but I have no idea why, or how to fix it...

Hard to diagnose when two parties are involved.
Have you tried to restart SABnzbd, your computer?

From my original post: "I've tried restarting SAB, restarting my server, checked my connection to my usenet provider, nothing fixes this.".

I'm considering reinstalling from scratch to see if that helps. I'll backup the config and try that this weekend.

Sorry, read too fast.
Possibly a queue reconstruction might help, Status page.

hey shypike, I'm seeing the same issue on multiple providers right now

2015-03-15 15:54:05,970::INFO::[urlgrabber:116] Grabbing URL https://provider.com/getnzb/eace4721804 ... c8462f5ad5
2015-03-15 15:54:06,448::DEBUG::[urlgrabber:372] No response from indexer, retry after 60 sec
2015-03-15 15:54:06,448::INFO::[urlgrabber:199] Retry URL https://provider.com/getnzb/eace4721804 ... c8462f5ad5

Same recipe.
Restart SABnzbd or a queue repair.
(Careful with the latter)

I have restarted sabnzbd. How do I do a queue repair? And what care need I exercise?

Thanks for responding

in the meantime, I tried stopping it and removing the following files, but it did not work.

• Rating.sab
• future
• postproc1.sab
• rss_data.sab
• watched_data.sab
• bookmarks.sab
• history1.db
• queue9.sab
• totals9.sab

The queue repair button is on the Status page.
It may also remove all pending NZB fetches from the queue.
Are you sure the indexing sites are responsive?

Manual use of the URL's in the fetch message work perfectly fine. ( I had to change to plush theme to see the queue repair )

There was no luck with the repair :/ still the same issue after. Any other ideas?

Which operating system are you using?
If you run from sources or use a Linux package,. which Python version do you use?

FreeBSD luffy 10.1-RELEASE FreeBSD 10.1-RELEASE
SABnzbd 0.7.20
Python 2.7.9

OK, your server is using an invalid SSL certificate.
Since 2.7.9, Python verifies SSL certificates by default.
That's a positive development, but backfires when sites do not use valid certificates.

Does your server(s) have alternative URL's?
Example: binsearch.nl uses the (valid) certificate of binsearch.info.
But when you use the .nl address, certificate verification will fail because its tied to the .info address.

We're working on an option to disable certificate verification.
Not easy because we're also using a complicated third party RSS module.