Do more on the web, with a fast and secure browser!

Download Opera browser with:

  • built-in ad blocker
  • battery saver
  • free VPN
Download Opera

SSL certificate error when accessing https sites using Windows Family Safety

  • Windows 8.1
    Opera Beta
    Microsoft Family Safety on Kids account

    I've been using Opera and Microsoft Family safety on my kid's account without problems, but suddenly I can't access sites like youtube because I get an SSL error. If I turn off Family Safety then it works ok. But I don't want to turn it off because it's on my kid's account.

    I haven't changed any settings, and it worked fine until about a week ago.
    I don't know if MS have changed something in how Family Safety works, or if Opera or Chrome have changed something.
    It'd be really useful if it could be fixed though! I have irate kids!

    (I read somewhere that Family Safety has to use it's own certificates to get around HTTPS encryption, and that those are trusted by default in IE, but not in chrome/firefox. I wonder if it's to do with that. I'm not really sure about how certificates work though).

    PS/ while I'm here: the way opera updates is rather annoying because it keeps making new folders and the location of opera keeps changing, so things like Family Safety (and also spybot) lose track of it and it keeps getting blocked after each update until I re-allow it).

  • I have same issue and I discovered that is because of avast antivirus. Only if I unselect "Activate HTTPS scan" on Web protection settings I can navigate the web!

    Even you have avast antivirus?



  • I have avast, so I'll check that out.
    Not sure I want to start disabling antivirus though. maybe we should try posting on the avast forum as well and see if we can get it fixed.

    Thanks for the info

  • Ok. You were right.
    Disabling HTTPS scanning in the avast protection settings worked, but that seems to apply to all accounts on the PC.

    My solution was to put exceptions for * and * into avast.
    Hopefully that's a more secure solution. I guess.

    though if you are getting similar errors on lots of sites then it might not be a good idea to set up exclusions for all f them.