Is anyone else having SSL problems with Giganews? Everything was working fine but suddendly I can't retrieve headers. I get:
ssl connect error
I've tried ports 443 and 563 but no luck. Regular traffic through port 119 is flowing fine. I use Avast! and disabled it but didn't make any difference. No other firewall/antivirus software running.
I've submitted a ticket with Giganews but haven't heard anything.
Thanks.
SSL errors with Giganews
Re: SSL errors with Giganews
OK, to answer my own question in case anyone else runs into the same problem.
It WAS Avast. They must have changed something in the latest update. To fix it, I went to "Mail Shield -> Expert Settings" and unchecked "Scan newsgroup messages (NNTP)".
For some reason I had to reboot before the change took effect but now it isn't blocking the SSL traffic.
BTW, I tried to add an SSL account for giganews in the list of known SSL accounts but it didn't work.
It WAS Avast. They must have changed something in the latest update. To fix it, I went to "Mail Shield -> Expert Settings" and unchecked "Scan newsgroup messages (NNTP)".
For some reason I had to reboot before the change took effect but now it isn't blocking the SSL traffic.
BTW, I tried to add an SSL account for giganews in the list of known SSL accounts but it didn't work.
-
- Posts: 17
- Joined: Sun Jul 13, 2008 7:22 am
- Location: France
Re: SSL errors with Giganews
I'm having the same problem with Avast! - when I turn off Avast!, the SSL errors stop. But your solution didn't work. Do you have any other suggestions?
TIA
Les
TIA
Les
Re: SSL errors with Giganews
SSL errors may well mean the incoming traffic is corrupted by the antivirus, so look for feedback on this version on the internet, you should find something since it may affect many programs p2p including.
i remember when SSL avast didn't check the nntp traffic whatever is the setting - since it is not possible, disabling nntp scan worked only for compressed headers "uncompress" errors.
i remember when SSL avast didn't check the nntp traffic whatever is the setting - since it is not possible, disabling nntp scan worked only for compressed headers "uncompress" errors.