[Windows] 6.1.312.1629 - HTTPS pages not loading at first, works after refresh

[gustms]

Sent this and logs to support as well with UserID: 1495949

Hello, yesterday I updated both AdGuard to version 6.1.312.1629 from the beta before, and ESET Internet Security to version 10.0.390 from 10.0.369 (something along this).

Then, I started noticing a problem. Sometimes, HTTPS pages will hang from loading, like, freeze in a blank page and waiting for server "https://www.XXXXXX.com/" for a long time, until I press to reload the page again. Then it will load correctly.

At first, I thought it was a new problem between WFP and ESET's SSL scanning, so I disabled ESET ssl. But the problem kept happening. Then, I tried disabling AdGuard Service, and the problem wasn't happening again. Reinstalled AdGuard, but the problem remains.

It is kind of random, like, it will load correctly it the first time sometimes, and sometimes not. This morning, I decided to try to get a debug log of the problem, and I think I managed it. You will see in the logs that around 9:18 AM I turn on the debug log, and then open Cyberfox 51.0.1. My home page is a blank page, so it opens correctly. Then, I try to do a google search from the search box, and the site hangs for some time, without loading. After a minute or so, I press enter again to refresh, and the site loads correctly.

Hope I could reproduce the problem and you can find it. Thanks a lot in advance. I'm open to any more questions you might have.

 

[avatar]

Let's do a quick check: tray menu -> advanced -> settings -> uncheck "Use local injections" there.

Does it make any difference?

 

[aegis]

Works fine for me (with AdGuard to version 6.1.312.1629 and ESET IS 10.0.390).
I used Cyberfox 51.0.2 though, but I don't think it makes any difference.
Have you actually noticed the problem in any other browsers btw?

 

[gustms]

Thank you @avatar and @aegis

I spent the day with my notebook in the university, and no problems there. I unchecked the mentioned options in advanced settings, but sometime after I checked it again, and everything was working great. I think it might have been a problem with my home connection, with a coincidence to turning adguard service off, and seems like it fixed itself as it is not happening again this evening.

I did not try another browser, as I use only Cyberfox, and thought the log showed some different values that could point to the problem, but this might be to debug mode having more info.

Thanks anyway for the comments, and will keep an eye if it comes back to evaluate more carefully.

 

[avatar]

That's a relief! I was afraid that ESET had reverted their driver back to the problematic state.