rgrodzicki Posted December 11, 2020 Posted December 11, 2020 Installed Passwordstate v8.9 Build 8991 for evaluation: Windows Server 2019 Standard, Clean Install with IIS SQL Server Express 2019 Base URL: https://internal_fqdn:9119 /selfdestruct/ shown as Application in IIS Manager Selecting "Save" in System Settings produces this error: Viewing the Error Console provides the following errors (note: no AV installed on system): Visiting the /selfdestruct/ URL produces the following error: Any idea what could be the issue? As mentioned, this is a brand new installation of everything for evaulation. Installation instructions were followed to get to this point. Thanks
support Posted December 11, 2020 Posted December 11, 2020 Hello, Could you please check the following for us? With the screenshot below of the key for your Self Destruct feature, have a look at the file C:\inetpub\Passwordstate\selfdestruct\web.config file and see if it matches? If it does, can you also do the following for us: Confirm if you are using any Load Balancers or Reverse Proxies? If not, can you contact us via the following support page and provide us a copy of this web.config file to have a look at - https://www.clickstudios.com.au/support.aspx Regards Click Studios
rgrodzicki Posted December 14, 2020 Author Posted December 14, 2020 After reviewing the files/config, the keys were not matching. Attempts to make the keys match did not help. I will be sending support request via the link provided. Thank you.
support Posted December 14, 2020 Posted December 14, 2020 Thanks - I've responded to your email, and hopefully we've provided you a fix. It looks like we've included extra configuration items in this web.config file that are already present in the parent web.configs file, so we will look into this and fix it for the next release. Sorry for the inconvenience. Regards Click Studios
rgrodzicki Posted December 14, 2020 Author Posted December 14, 2020 Thanks for the help. This solved the issue. Looking forward to evaluating this product.
Martin Wallin Posted December 18, 2020 Posted December 18, 2020 I have the same problem, new install recently bought the product.
Martin Wallin Posted December 20, 2020 Posted December 20, 2020 Solved by support, new web.config needed. /Martin
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