Page 1 of 1

Error in Newsbin Premiumize Server

PostPosted: Wed Dec 04, 2019 10:15 pm
by aussiedean
Hi there,

i have recently been using Premiumize as a Usenet provider as well as other uses and I have asked the question in there support but not heard anything as yet but I'm getting this problem in the pic below. Have the latest version of Newsbin and have tried both SSL and port 119 with the same result.

Any ideas on where i could start?

https://imgur.com/a/gXi9fCP

Re: Error in Newsbin Premiumize Server

PostPosted: Thu Dec 05, 2019 1:34 am
by Quade
What happens if you try it without SSL? This is some sort of SSL error I think.

What have you put in for the address field?

Re: Error in Newsbin Premiumize Server

PostPosted: Thu Dec 05, 2019 9:52 am
by aussiedean
HI there .... changed to nil SSL and the same issue.

Server address is usenet.premiumize.me

Re: Error in Newsbin Premiumize Server

PostPosted: Thu Dec 05, 2019 5:03 pm
by Quade
I was able to connect to the server this morning. Not using SSL with the address of "usenet.premiumize.me" and the port set to 119.

"Read Zero bytes from Socket" isn't that unusual if the server is disconnecting the connection. Can you still download? Some servers will kill a connection after you've downloaded some number of bytes from it, forcing Newsbin to re-connect and continue the download.

Re: Error in Newsbin Premiumize Server

PostPosted: Thu Dec 05, 2019 8:55 pm
by aussiedean
Tried to download and it does seem to work downloading. I don't think the Premiumize service is that crash hot to be honest as opposed to a premium usenet provider like Usenet Server that I had previously. Thanks for trying anyway its probably nothing to do with your program.

Re: Error in Newsbin Premiumize Server

PostPosted: Fri Dec 06, 2019 6:17 pm
by aussiedean
Tried Grabbit and no errors, probably not as fancy as Newsbin with the logging.

Re: Error in Newsbin Premiumize Server

PostPosted: Sat Dec 07, 2019 12:56 am
by Quade
Yeah, I should suppress that error since a disconnect isn't a real error. I'll look into it.