Dec 01
Some users have issues connecting to SABnzbd with 1.2.5.
I’ve added a hidden option to change http timeout value.
If you have troubles like suddenly it said via growl “not started”, then switched back to “downloading”, try to change timeout value with with command in Terminal :
defaults write ~/Library/Preferences/org.sabnzbdx.team timeout -int 5
you can change value between 1 and 10 (default value in SABnzbdX 1.2.4 was 5, in 1.2.5 was 1 and in 1.2.6 it’s 2).
SABnzbdX is available for free to download, but if you’d like to see it continue to be developed then please donate.
December 1st, 2009 at 5:23 am
Don’t forget to set your API key in Preferences
If you still have troubles, please come to SABnzbd forums
December 1st, 2009 at 1:31 pm
I take it SABnzbdX is redundant if we’re using SABnzbd+ 0.5.x?
December 1st, 2009 at 2:47 pm
I think it’s complementary.
If you install SABnzbd on one computer, you can use SABnzbdX on a other to monitor it…
If you use SAbnzbd on one computer only, no need to install SABnzbdX anymore.
December 2nd, 2009 at 4:12 pm
Anyone get SABnzbdX to add items to the queue on a remote machine running SABnzbd+ 0.5.0Beta1 ?
On my machines growl says an .nzb is added to the queue but it is never actually added to the queue on the remote machine.
December 2nd, 2009 at 5:57 pm
@wasp : It works for me, come to forums (see first comment) to discuss.
December 2nd, 2009 at 6:30 pm
My Bad.
Appears that in SABnzbd+ 0.5Beta1 there is a problem adding .nzb’s if a proxy server is configured in network settings.
I had a proxy server configured on the machine running SABnzbd+ 0.5Beta1.
Once I disabled the proxy server both SABnzbd+ 0.5Beta1 on the host machine and SABnzbdX 1.2.6 running on the remote machine worked fine.
I can add .nzb’s from either machine fine now.
December 2nd, 2009 at 7:35 pm
@wasp : thanks for reporting !
March 4th, 2010 at 6:12 am
What if you… want the proxy server?