Hi,
first of all, let me say that I've been using SABnzbd now for months, and it's the best darn product on the market !
I have a strange problem since today, though.
I use Firefox and a plugin called NZBstatus to tie in with SABnzbd. When I browse through Newzbin, the NZB icons next to the reports are replaced by a little SAB button. When I clicked this, I used to get the download added to SABnzbd right away. Since today, the message "retrieving message ID" followed by the report number shows up in the download queue, and the connection to Newzbin times out.
All the time.
I can still manually add NZBs, if I download an NZB for the same file, and SABnzbd picks it up out of my watched folder, it works too.
It's just that this direct sending of NZBs to SABnzbd via NZBstatus doesn't work anymore.
I've checked the setup, everything works ..... except it doesn't
Any ideas ?
Thanks
BC55
SABnzbd is no longer fetching message IDs from Newzbin
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: SABnzbd is no longer fetching message IDs from Newzbin
Have you tried just entering a newzbin report number into SABnzbd?
Have you tried to restart SABnzbd?
It may take a long time to get NZB files from newzbin, due to their rate limiting.
Do the fetches end up in the history eventually?
Have you tried to restart SABnzbd?
It may take a long time to get NZB files from newzbin, due to their rate limiting.
Do the fetches end up in the history eventually?
Re: SABnzbd is no longer fetching message IDs from Newzbin
Hi, thanks for replying so quickly.shypike wrote: Have you tried just entering a newzbin report number into SABnzbd?
Have you tried to restart SABnzbd?
It may take a long time to get NZB files from newzbin, due to their rate limiting.
Do the fetches end up in the history eventually?
Adding the report number directly didn't work either, same error.
Yes, I even re-installed SABnzbd and NZBstatus from scratch.
What does the rate limiting mean exactly ? You mean it might be due to high traffic / demand on their server ?
No, the fetches just stay there, with the time out error repeating itself forever .....
Funny thing is that if I leave Newzbin out of the chain, by downloading NZBs and SABnzbd grabbing them from the watched folder, it works as always.
I have a feeling Newzbin is slow or maybe not working as usual, even though the site admin wrote and said all was fine .....
Re: SABnzbd is no longer fetching message IDs from Newzbin
Stop SABnzbd, start a command prompt and instead run "c:\program files\SABnzbd\SABnzbd-console.exe" from there.
Make sure SABnzbd is paused and then enter a newzbin report number.
The black console should show you what is happening.
Make sure SABnzbd is paused and then enter a newzbin report number.
The black console should show you what is happening.
Re: SABnzbd is no longer fetching message IDs from Newzbin
Well whaddaya know - it works.shypike wrote: Stop SABnzbd, start a command prompt and instead run "c:\program files\SABnzbd\SABnzbd-console.exe" from there.
Make sure SABnzbd is paused and then enter a newzbin report number.
The black console should show you what is happening.
Both ways, pasting the report number in, or clicking the little SAB icon.
So what did I do differently ? Was it just Newzbin being slow ?!
Or should I generally start with the -console bit added ?!
Cheers for the help !
Re: SABnzbd is no longer fetching message IDs from Newzbin
Must have been either newzbin having an off moment/
Or SABnzbd was confused: you did restart the program,
which is often a good cure for any malfunctioning program.
The console version is identical to the normal version,
except for the display part.
Or SABnzbd was confused: you did restart the program,
which is often a good cure for any malfunctioning program.
The console version is identical to the normal version,
except for the display part.