support Posted November 24, 2021 Share Posted November 24, 2021 Issue: Some functionality may not be working in Passwordstate, and to rule out an issue with your production HTTPS Binding, you need to bypass it. Procedure: Open IIS on your Passwordstate webserver, and create a new HTTPS binding called "localhost". Set the Port to 443 and assign any certificate you have available to this new binding: Whilst still logged into your web server, open your browser and brose to https://localhost. You may receive a warning from the browser that the certificate is not trusted. Click the Advanced button and then Proceed to the website: You should now be able to log into your Passwordstate website with your normal credentials. Please perform the appropriate test as directed via Click Studios support and report back results. Regards, Support 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