Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Hoelder
2 years agoOccasional Contributor
Error when using 1Password in the browser: "Your session has expired."
Since today, there is a strange problem with the 1Password extension in Edge: When I open a website or click on the tab of an open website, the 1Password sign-in webpage (https://my.1password.com/signin/?a=XXXXXXXXXXX) is being opened in another tab. See screenshot.
This happens only when I unlocked the browser extension beforehand.
When I sign in, the tab is closed automatically. Since the extension is unlocked, I can sign in via the extension.
I already tried to manually open the sign-in page, sign-in and logout, but that doesn't help.
What's wrong here? Does someone else have the same problem?
54 Replies
- 1P_Dave
Moderator
I'm sorry for missing that, thank you for quoting the appropriate section from your post. It sounds like you're running into the same issue that I mentioned earlier. You can workaround the issue, until we have a permanent fix released, by using one of the workarounds that I described here.
Our developers don't need any other information, like a console log from your end, at this time.
-Dave
- 1P_Dave
Moderator
- 1P_Dave
Moderator
I understand that it can be difficult to send in a console log and I'm sorry that you're also seeing the issue. So that I can determine if you're affected by the known issue that I mentioned earlier, can you tell me the following:
- Is two-factor authentication enabled for your 1Password account? If it it then are you using Duo or Okta or just another authenticator app?
- Do you have the desktop app installed?
- In the "Security" section of the extension's settings, do you have "Automatically lock 1Password" toggled off?
I look forward to hearing from you.
-Dave
- 1P_Dave
Moderator
- krischikOccasional Contributor
Well at least we have a workaround. Tying the password every 8 hours is better then typing it all the time.
- kiplingNew Contributor
Just to add another data point, I'm having this same issue. 2FA with Authy, Chrome extension auto-lock set to off, and no desktop app installed. The problem with the request to provide the extension console log is that the instructions say to enable it and then reproduce the issue, but the problem appears periodically on its own, and I don't know what steps to take to actively reproduce it.