imjustabill

That sort of works. If I go to https://localhost/my-site I still get the warning. If I go to https://127.0.0.1/my-site I don't get the warnings but the browser tells me that the site isn't secure, which I can live with. I just don't know if I can make the switch to start using the ip rather than localhost. I've been using localhost for many years and it's ingrained. It's probably better than having to deal with that warning. Thank you.

Hi, I'm running a webserver locally for development work, and I need to run it using https in order to test some features. I created a self-signed certificate for localhost and when I go to the page, I get a warning from Kasperky saying that the websites certificate is invalid. If I view the certificate, it says "This ca root certificate is not trusted. To enable trust, install this certificate in the Trusted Root Certification Authorities store." I can get past it by clicking on "I understand the risks and wish to continue". I can then navigate through the site, but then every 10 min or so, I need to go through the process again. Is there any way I can add an exception to to Kaspersky for this certificate running in localhost so that I do not get this message?