SABnzbd Forums

Hey all,

I'm using the free IPv6 servers. As some of you may know, there are 3, Eweka, XSNews and Zilla.

In the past I used Newsleecher which worked fine. The servers sometimes died/stopped working for a while, but I accepted that as a free service. When I moved to SABNZBd, Eweka never worked but it seemed to be having problems with Newsleecher so I didn't pay much attention. (Never paid much attention to Zilla because it's of limited interest due to the low retention.) XSNews was working great. Recently XSNews has been having problems so I've started to look at Eweka again. As it's working fine in Newsleecher I wondered what was wrong. Looking at the server list, I realised it had a username and password for the server even though I never added any. The username and password are the web login username and password. I can't delete these from the web interface, if I try they just stay there. (If I change them to something else that works, if I delete them they go back to the web login username and password.) I haven't yet tried to modify the config file to see if that works but of course this shouldn't be necessary.

BTW, with Eweka I get the error "Access denied to your node" which I've seen other people report perhaps for the same reason. (Well eventually I get connection denied I presume because I hammered the server too much.) I get the same error in Newsleecher if I enable login and put something in. (If I don't put a username or password I get an error about no username/password provided).

Unless I missed something (and I wonder if I have since some people seem to have gotten Eweka working although perhaps they're talking about another usenet client or Eweka used to accept any login but stopped), it seems to me this is a bug. There should be a no login option as many usenet clients have. If I'm not mistaken this is the way usenet works, the client tries to login or it can try to work without logging in. Since most users wioth SABNZBd use paid usenet servers with servers I guess that's why not many people have noticed this problem. Even if I could convince SABNZBd to accept no username and password my guess is it will still try to login and so have the same problem as with Newsleecher that I mentioned above.

Version: 0.4.11
OS: Windows XP SP3
Install-type: Windows Installer
Firewall Software: XP Firewall
Are you using IPV6? Yes (obviously :-P)
Is the issue reproducible? Yes

Cheers

You can enter servers without setting a username and password.
From a server definition which now has a username and password, you can remove them
by just clearing those fields and clicking "Save".

I have no idea why the web username/pw ended up in the server definitions.
But it can be fixed like described above.

So altogether, I'm not sure what your exact complaint is.

Sounds like your browser is putting your saved sabnzbd credentials in the usenet login fields. It happens to me too
If you don't save with it in there, or you save with empty fields then that's how they will be.

Damn, that didn't sound right.

Clear out the password fields of one server in the usenet server screen
Save
Repeat, if you have to, with the next server.

When the page reloads, the user/pass forms will be filled again, but that's just the browser filling them in. It's not saved to SAB unless you click Save when the forms arn't empty.

If you don't understand or want a different solution, manually edit your sabnzbd.ini file and restart SAB.
Again, when you view that page it probably won't look empty, but that doesn't mean sab sees it that way.

I hope you understand, it's not an easy thing to explain.

rollingeyeball wrote: Sounds like your browser is putting your saved sabnzbd credentials in the usenet login fields.

I always forgett that issue, thanks for reminding me.
Must think of a way to avoid this issue.

No worries.
Would just changing the field names do it? Either so the browser doesn't see them as the sab login fields, or as login fields at all.

rollingeyeball wrote: Would just changing the field names do it?

I'll tip the skin designers I'm not very good at that stuff.

Thanks you guys are right :-) Can't believe it didn't occur to me. I guess when there's no username/password it just doens't try to login?

Anyway now have Eweka working fine. I did actually test it after saving without username and password as mentioned but because the username and password appeared to stay there and Eweka was blocking me (I think) because of continual requests I didn't notice it was working.

By default it's not a problem when you add a server and do remove username and password but beyond the confusion, it does cause problems if you change number of connections or whatever (which I did at some stage) and don't remove or don't notice the username/password. (At first I didn't save username and password so didn't notice this when I first added the servers).

Cheers