After updating to 0.6.9 i was unable to use nzbdstatus, sabconnect++, or sickbeard to download any nzb's directly.
Every time i tried i got "URL Fetching failed; (),"
I could manually download nzb's and add them to sabnzbd without any issues.
Checked my api key, user name, password, everything was fine.
Downgraded to 0.6.8 and everything works again.
Running windows 7 pro. x64
sabnzbd+ 0.6.9 URL Fetching failed; (),
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+ 0.6.9 URL Fetching failed; (),
what's the URL that nzbstatus etc are using, so ip-address/name and port? When you use that URL in a webbrowser from the same machine that's using nzbstatus, does it work?
Re: sabnzbd+ 0.6.9 URL Fetching failed; (),
I left everything on default
my-local-ip:8080/sabnzbd/
I have dyndns setup so i'm able to connect to sabnzbd from anywhere.
Both nzbstatus/sabconnect++ are able to connect to sab, both locally and remotely (i can see stats, download speed, que etc..)
I've tried with the actual ip on the pc that sab is installed on, i can connect to sab, but when nzbstatus/sabconnect++ sends the nzb file to to sab, it fails to fetch url.
If i manually download the nzb file, nzbstatus does detect it and is able to automatically add it to sab.
This works both locally and remotely, the problem is only when i use the "download to sab" direct link, neither nzbstatus or sabconnect++ work.
Sickbeard was not able to add anything to sab as well, anytime it tried, i got the same error.
Downgraded to 0.6.8 and everything is working.
my-local-ip:8080/sabnzbd/
I have dyndns setup so i'm able to connect to sabnzbd from anywhere.
Both nzbstatus/sabconnect++ are able to connect to sab, both locally and remotely (i can see stats, download speed, que etc..)
I've tried with the actual ip on the pc that sab is installed on, i can connect to sab, but when nzbstatus/sabconnect++ sends the nzb file to to sab, it fails to fetch url.
If i manually download the nzb file, nzbstatus does detect it and is able to automatically add it to sab.
This works both locally and remotely, the problem is only when i use the "download to sab" direct link, neither nzbstatus or sabconnect++ work.
Sickbeard was not able to add anything to sab as well, anytime it tried, i got the same error.
Downgraded to 0.6.8 and everything is working.
Re: sabnzbd+ 0.6.9 URL Fetching failed; (),
I've no idea how to help you. Sorry.
Re: sabnzbd+ 0.6.9 URL Fetching failed; (),
haha, no problem.
0.6.8 is working perfectly so I can live without 0.6.9.
Just wanted to post in case anyone else had this issue, or if it was a bug in the new version.
0.6.8 is working perfectly so I can live without 0.6.9.
Just wanted to post in case anyone else had this issue, or if it was a bug in the new version.
Re: sabnzbd+ 0.6.9 URL Fetching failed; (),
Weird, because
a) there are no changes in 0.6.9 that can even remotely explain this.
b) nzbdStatus works fine for me with the same SABnzbd version and the same OS
I cannot test all your use cases, but I'm at a loss where a cause could be.
a) there are no changes in 0.6.9 that can even remotely explain this.
b) nzbdStatus works fine for me with the same SABnzbd version and the same OS
I cannot test all your use cases, but I'm at a loss where a cause could be.
-
- Newbie
- Posts: 1
- Joined: October 12th, 2011, 8:02 pm
Re: sabnzbd+ 0.6.9 URL Fetching failed; (),
Same problem here.
Re: sabnzbd+ 0.6.9 URL Fetching failed; (),
More information and preferably a debug log (see Status page) are needed.
Just saying "same problem" won't help anyone.
Just saying "same problem" won't help anyone.