newsbin.com

Hello,
I can not use any version greater then 6.42 anymore!
Is there something changed in the ssl engine?
6.42 works oke.

[17:17:35] ERROR Error: SSL Negotiation Failed, Host: news.eu.supernews.com Error: SSL Connection Failed: 5 Error 0 The operation completed successfully.

Regards,
Zworld.

I assume you mean, 6.50?

It's probably your virus scanner or firewall. Lots of people are using 6.50 with SSL to supernews. You really want to make you security software ignore Newsbin's connections to the news servers. They cause corruption of the downloaded files even when they don't block the connections.

Hello Quade,
I have tried with/without firewall, with/without proxy. But no connection.
[20:07:05] ERROR DG - Connection Failed: SUP1 Index:3
There must something changed in the code....... because 6.42 works flawless.
6.50B11 can not establish a connection over SSL.
I am downloading with 6.42 right now without any error........

Regards,
Zworld.

All I use is SSL and it works fine so, I don't agree. If you turned the proxy on, and don't have a proxy, it won't work at all.

Change the address to "news.supernews.com". Restart Newsbin and try again. It's either configured wrong or it's a firewall like I originally said.

I'd simply remove the firewall and virus scanner, reboot, try a couple downloads, then re-install them if it works

Ok Thanks Quade,

I have Newsbin installed in a vm. works oke.....
Strange, back to the drawing board.
Thanks again.
Zworld

Hello Quade,
One more question, I have found out the connection is not working with socks proxy.
I have upgraded to the latest version of dante socks, but still no luck.
Without socks the connection is oke.
Socks is oke in 6.42, any changes in the socks code?

Regards,
Zworld.

After looking in the socks logfie this error:
Jun 17 22:04:03 (1371499443.070587) sockd[3549]: info: block(1): tcp/accept ]: 192.168.1.100.60665 192.168.1.254.1080: error after having read 1 bytes: unknown socks version 22 in client request
Jun 17 22:04:03 (1371499443.071812) sockd[3550]: info: block(1): tcp/accept ]: 192.168.1.100.60666 192.168.1.254.1080: error after having read 1 bytes: unknown socks version 22 in client request
Jun 17 22:04:03 (1371499443.074303) sockd[3549]: info: block(1): tcp/accept ]: 192.168.1.100.60667 192.168.1.254.1080: error after having read 1 bytes: unknown socks version 22 in client request
Jun 17 22:04:03 (1371499443.075667) sockd[3549]: info: block(1): tcp/accept ]: 192.168.1.100.60668 192.168.1.254.1080: error after having read 1 bytes: unknown socks version 22 in client request
Jun 17 22:04:03 (1371499443.076815) sockd[3549]: info: block(1): tcp/accept ]: 192.168.1.100.60669 192.168.1.254.1080: error after having read 1 bytes: unknown socks version 22 in client request
Jun 17 22:04:05 (1371499445.575178) sockd[3549]: info: block(1): tcp/accept ]: 192.168.1.100.60671 192.168.1.254.1080: error after having read 1 bytes: unknown socks version 22 in client request
Jun 17 22:04:05 (1371499445.575952) sockd[3550]: info: block(1): tcp/accept ]: 192.168.1.100.60673 192.168.1.254.1080: error after having read 1 bytes: unknown socks version 22 in client request
Jun 17 22:04:05 (1371499445.575951) sockd[3549]: info: block(1): tcp/accept ]: 192.168.1.100.60672 192.168.1.254.1080: error after having read 1 bytes: unknown socks version 22 in client request
Jun 17 22:04:05 (1371499445.577354) sockd[3549]: info: block(1): tcp/accept ]: 192.168.1.100.60674 192.168.1.254.1080: error after having read 1 bytes: unknown socks version 22 in client request
Jun 17 22:04:05 (1371499445.578070) sockd[3550]: info: block(1): tcp/accept ]: 192.168.1.100.60675 192.168.1.254.1080: error after having read 1 bytes: unknown socks version 22 in client request
Jun 17 22:04:05 (1371499445.578395) sockd[3550]: info: block(1): tcp/accept ]: 192.168.1.100.60676 192.168.1.254.1080: error after having read 1 bytes: unknown socks version 22 in client request

I don't know. I'll have to setup a proxy and try it.