Intermittant problems with HTTPS with 5.2x

Discussion in 'ESET Smart Security' started by Oswald2, May 19, 2012.

Thread Status:
Not open for further replies.
  1. Oswald2

    Oswald2 Registered Member

    Joined:
    Oct 3, 2006
    Posts:
    63
    Upgraded to 5.2 the other day. Since then, I keep getting

    The connection was reset
    The connection to the server was reset while the page was loading.​

    Particularly when visiting HTTPS sites. Other times, the site partially loads, but then sort of hangs forever, leaving some images unloaded, etc. This was never a problem with 5.0.95. I was able to get things to work better by turning off HTTPS protocol checking under HTTP/HTTP Scanner|HTTP protocol mode. But I wonder if I'm losing some protection by doing this, and why I never had to play with this in 5.0.95. I don't necessarily want to roll back to 5.0.95 (and not sure where to find it anyway), but if most sites have this problem, I may need to find it.
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    What OS and browser do you use?
     
  3. Oswald2

    Oswald2 Registered Member

    Joined:
    Oct 3, 2006
    Posts:
    63
    I'm using Windows XP Home SP3, and I'm seeing it under Firefox (12.0), Chrome, and IE 8.
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    With v. 5.0.95, SSL scanning did not work with Firefox and Chrome. We've tested SSL scanning with these browsers and didn't find any issues. Is anybody else experiencing the same?
     
  5. Michigan

    Michigan Registered Member

    Joined:
    May 20, 2012
    Posts:
    1
    Location:
    Germany
    Almost the same here. I'm running Windows 7 x64 and since I upgraded to 5.2.9 I'm not able to connect with HTTPS (Firefox 12). Help is to completely disable the firewall (then SSL scanning seems to work) or disable SSL scanning.
     
  6. Oswald2

    Oswald2 Registered Member

    Joined:
    Oct 3, 2006
    Posts:
    63
  7. Oswald2

    Oswald2 Registered Member

    Joined:
    Oct 3, 2006
    Posts:
    63
    I was able to verify that I got the same results in IE8. When I turned on ESET's HTTPS scanning, it eventually stopped working. When I turned it off, it immediately started working again.
     
  8. Oswald2

    Oswald2 Registered Member

    Joined:
    Oct 3, 2006
    Posts:
    63
    This is still frustrating me. After going several days with HIPS turned off and HTTPS filtering off and no problems with HTTPS connections, I turned them on last night only to find that after several hours of use, HTTPS connections start failing. Click "Do not use HTTPS protocol checking" and bam, the connection starts working again. Affects several browsers (IE8, FF, Chrome). Have not tested in Opera and Safari.

    I'm leaving it off for now, since Marcos said it didn't work in 5.0 anyway.
     
  9. Oswald2

    Oswald2 Registered Member

    Joined:
    Oct 3, 2006
    Posts:
    63
    Having the same problem with Windows 7 Pro SP1 on a totally different network.
     
  10. Uroboros

    Uroboros Registered Member

    Joined:
    Nov 9, 2003
    Posts:
    70
    I've had the same problem but it only seems to happen with Firefox (v.13).

    Can't get into HTTPS sites. Firefox tells me "This Connection is Untrusted"

    Specifically the technical info is

    www.google.com uses an invalid security certificate.

    The certificate is not trusted because no issuer chain was provided.

    (Error code: sec_error_unknown_issuer)

    If I try to add an exception and look at the certificate, says it's been issued by ESET

    If I turn off HTTPS protocol checking for selected ports then it works.

    Didn't happen before the upgrade and doesn't with the other browsers.

    I suppose there probably is an option to turn off this checking in Firefox; but of course that's not the way it should work.
     
  11. Grandcanyon

    Grandcanyon Registered Member

    Joined:
    Jun 11, 2012
    Posts:
    1
    Location:
    USA
    Having the same problem. After updating to current version I can not enter any page that is HTTPS with FF or IE.

    If I turn off HTTPS protocol checking for selected ports then it works.

    I am reading work a rounds here, but when will Eset fix this issue??
     
Thread Status:
Not open for further replies.