I created a self signed wild card certificate (*.website.local) on our internal environment which can be accessed using an internal DNS URL (ex: https://site1.website.local). I have HSTS enabled for the purpose of testing I want to enforce it. When browsing to the site using Edge I would see the following error.
Error:
Your connection is not private. Attackers might be trying to steal your information from website.local (for example, passwords, messages, or credit cards). NET::ERR_CERT_INVALID. website.local normally uses encryption to protect your information. When Chrome tried to connect to website.local this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be website.local, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Chrome stopped the connection before any data was exchanged.
You cannot visit website.local right now because the website sent scrambled credentials that Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later.
I know the work around is to type in thisisunsafe or badidea and it would work after that.
It would be nice to not having to type this in and instead do something to make the browser recognized that I trust my own self sign certificate. I attempted to put the certificate into my Trusted Root CA but it does not help. Do you know of any other steps I can try?