Beau P. Posted September 26, 2019 Share Posted September 26, 2019 We just upgraded to the latest build (8792) and the new browser extension is not autoconfiguring. I inspected the extension and found it was getting a 404 on the authenticate API. I've attached a picture of the error. Any ideas? Link to comment Share on other sites More sharing options...
support Posted September 26, 2019 Share Posted September 26, 2019 Hello Beau, Please reference the following forum post for this, as an upgrade to Passwordstate will be required to fix this - https://www.clickstudios.com.au/community/index.php?/topic/2850-build-mismatch-error-in-the-chrome-browser-extension/ Sorry again for the inconvenience. Regards Click Studios Link to comment Share on other sites More sharing options...
Beau P. Posted September 26, 2019 Author Share Posted September 26, 2019 Hello, I read that post but I'm confused. My issue is only occurring AFTER upgrading to the latest version. Per my post, I upgraded to 8792 (latest version AFAIK) and getting that error. Link to comment Share on other sites More sharing options...
support Posted September 26, 2019 Share Posted September 26, 2019 Hello Beau, I'm so sorry - I misread your original post. We haven't had any other reports of this, so we're not sure of the cause at this stage. Could you try the following to see if it will help: Restart IIS, then try logging into Passwordstate again Clear your cache in Chrome, and then try again Go to the Help Menu in Passwordstate, open the Web API Documentation page, and then open the Standard Documentation - does this load okay And can you check if this is working for any other users? Thanks Click Studios Beau P. 1 Link to comment Share on other sites More sharing options...
Beau P. Posted September 27, 2019 Author Share Posted September 27, 2019 1. Tried this. Did not fix. 2. Tried this. Did not fix. 3. Yes. 4. Not working for all users. There is a message in the Audit log for a failed API call every time the extension tries to authenticate: Failed API Call: An exception has occurred executing an API Script. Error = Object reference not set to an instance of an object. from IP Address xx.xxx.xx.xxx, using a URL of https://<oursite>/api/browserextension/authenticate/. Link to comment Share on other sites More sharing options...
Beau P. Posted September 27, 2019 Author Share Posted September 27, 2019 @support I found and fixed the issue. This is our first upgrade after installing the product. Shortly after installing, we copied the install from c:\inetpub\PasswordState to g:\PasswordState and modified the directory for the passwordstate site in IIS to be the new directory. I did not realize that there were 4 applications inside that website so they were still pointed to the old path (which didn't get upgraded). I modified those and restarted the website, recycled the app pools and restarted the service and the extension is now working. Thanks for looking into this with me. Link to comment Share on other sites More sharing options...
Beau P. Posted September 27, 2019 Author Share Posted September 27, 2019 On a side note, I've gotten a lot of feedback that the new browser extension is awesome. Great job on an excellent product! Link to comment Share on other sites More sharing options...
support Posted September 27, 2019 Share Posted September 27, 2019 Hi Beau, Thanks for letting us know, and for your kind words about the new extension Have a great weekend. Regards Click Studios Beau P. 1 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