Required manual unblock?

[jimage]

I'm using the new 0.5.0 beta4 and seems every time my server or internet has a hiccup sabnzbd set it to blocked and then I have to realize that and go to config and click the 'unblock' link.  I've read elsewhere that it's should unblock itself after ten minutes?  Mine is definitely not doing that.  Another weird thing is that my server does not require username/password and that is listed as the reason it was blocked.  It will stay blocked for hours, however long until I unblock, any idea what's wrong?

2009-12-18 21:12:18,476
WARNING:
Thread [email protected]:119: Server news.server.net:119 requires user/password

Just now I specifically sat there for over ten minutes after it blocked to see if anything would change and nothing did, I unblocked and things worked just fine, no user/password required.

[shypike]

SABnzbd only shows that message when we receive the '480' status message from the server.
The official meaning of that code: "480 Authentication required"
So it looks like a problem with the server.
Please complain with your Usenet provider too.

480 means that the server wants a username and password.
SABnzbd did not send these, because they were not set by you.
Can you try to set a fake user name and password?
See what happens then?

BTW: if you are using the "smpl" skin, the unblock link will not work.
That's a bug, it does work in the other skins.

[john3voltas]

Uff, I thought I was the only one with the unblock button that didn't work.
After all it's a template issue.
May I ask if it's due to be fixed in 0.5.0 final?
To a coding ignorant like me it sounds like an easy fix, right?
Cheers

[jimage]

Setting a fake user/pass makes me not connect at all.  I have supernews through my isp and if I use my isp login I can login on any computer but only with 3 threads and 50kb/s limit.  If I'm at home I'm allowed through the ip (no user/pass) that I'm on to have 5 threads and no kb/s limit. So I'm guessing that is why it won't let me use a fake user/pass.

But I think the problem is that when my server or internet hiccups my server throws up a user/pass required error (why, I do not know), which it's not required but that's what it does.  Is SABnzbd not set up to automatically unblock after it receives that error?

I use the plush theme and my unblock link works just fine, I just don't want to have to do it myself every single time.

[shypike]

Uff, I thought I was the only one with the unblock button that didn't work.
After all it's a template issue.
May I ask if it's due to be fixed in 0.5.0 final?
To a coding ignorant like me it sounds like an easy fix, right?
Cheers

It's not an easy fix or I would done it already.
I'm waiting for the skin's designer to pick this up.

[shypike]

Is SABnzbd not set up to automatically unblock after it receives that error?

It unblocks after "soft" errors, the ones that are expected to go away.
Not having the right username/password is a "hard" error.
It's no use trying to keep logging in with the wrong credentials.

I don't think its our job to compensate for a shoddy job at the server's end.
Please complain to your provider too.

[philonimbus]

Would it be possible to add an option asking how to deal with 480 errors ?
It simply stops downloading for hours until I do something about it, knowing that I have to restart sabnzbd manually, as the unblock feature doesn't work for me either.

[shypike]

SABnzbd is an automation solution. Set and forget.
In most situations, there's no "asking" the user anything.
The most we could do is email an alert.
Might be a good idea for a later release.

[john3voltas]

Might be a good idea for a later release.

Agreed.

[philonimbus]

Indeed, that's how I use SABnzbd : set and forget !
That's what I meant by asking the user how to handle 480 errors, a setting.
In the way you set the number of connections, a "retry after X minutes" setting could be nice.
I don't think I'm the only user to download at night, and it can be quite frustating to see your queue hasn't been downloaded because the server is blocked until user intervention.

Btw the unblock feature doesn't seem to work on my system, I'm usisng v.5RC3 on ubuntu 9.10

[shypike]

Indeed, unblocking will not work for permanently blocked servers.
In principle this is correct, however the "deblock" link suggests otherwise.
The idea is that you change the server settings, this will unblock the server too.

I'll fix this before 0.5.0 Final.

[shypike]

The solution will be:
1. Allow manual unblocking of servers with "permanent" errors.
2. Servers with "permanent" errors will be retried after 30 minutes.

That's it for 0.5.0. We may refine this later.