Jeff Pritchett Posted June 4, 2020 Share Posted June 4, 2020 We recently installed and setup Passwordstate on one of our PC's running IIS. I've configured DNS to point to our machine at pass.ourdomain.ca. We are currently using HTTPS to access it with the self-signed certificate and its working fine with no problems. As soon as I switch the certificate under binding in IIS from the self-signed one to the wildcard certificate that we have installed the site just doesn't work. I get an error in chrome that says This site can’t be reached The connection was reset. As soon as I change it back to the Self-signed one it works fine again. I can't see it being a DNS or firewall issue because the Self-signed cert works fine. Is there something I'm missing? Link to comment Share on other sites More sharing options...
Jeff Pritchett Posted June 4, 2020 Author Share Posted June 4, 2020 Nevermind, I figured it out. Apparently I was using TLS 1.0 which Chrome just refuses to load completely, no encryption error or anything. I had to change the registry to only use TLS 1.2 and that seems to fix the issues. Link to comment Share on other sites More sharing options...
support Posted June 6, 2020 Share Posted June 6, 2020 Thanks for posting back here Jeff. For any other customers reading this post, this issue was on a Windows 7 operating system. Regards Click Studios Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now