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.
There should be a no login option as many usenet clients have. 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. (If I don't put a username or password I get an error about no username/password provided). (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 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.īTW, with Eweka I get the error "Access denied to your node" which I've seen other people report perhaps for the same reason. I can't delete these from the web interface, if I try they just stay there. The username and password are the web login username and password. Looking at the server list, I realised it had a username and password for the server even though I never added any. As it's working fine in Newsleecher I wondered what was wrong. Recently XSNews has been having problems so I've started to look at Eweka again. (Never paid much attention to Zilla because it's of limited interest due to the low retention.) XSNews was working great. When I moved to SABNZBd, Eweka never worked but it seemed to be having problems with Newsleecher so I didn't pay much attention. The servers sometimes died/stopped working for a while, but I accepted that as a free service.
In the past I used Newsleecher which worked fine. As some of you may know, there are 3, Eweka, XSNews and Zilla.
0 kommentar(er)
