@dteare Yep! Will see if I can replicate this issue as well and provide logs.
Yup! Looks like you have the same settings I had when I recreate this issue. Thanks for sharing.
By the way, the lock settings for 1Password for Mac have no effect on 1Password X. They're completely independent.
We'll look into this and try to get a fix out soon.
Whether or not you get forum notifications depends on how you've configured Notification Preferences, like I described over here.
The software for this forum doesn't have an option to disable notifications for specific discussions, which would be the most desirable way to do it. An alternative is to bookmark only ones you want notifications for, with at least Notify me when people comment on my bookmarked discussions enabled.
I hope that helps even if it's not optimal.
[_request] Request "/api/v2/vault/gzjh7kn6e5iweldbh5m5ap2htm/119/items" failed: ServerError: "Authentication required."
[_request] Request "/api/v1/overview" failed: ServerError: "Authentication required."
[action/auth#createNewContext] Error: "Missing current user"
Failed to save login: Error: "Missing current user"
Woot! Thanks for the logs, @boberonicus. That's exactly what I needed.
@beyer and I found the issue. Turns out it was indeed related to sessions timing out, which normally manifests itself when autolock is disabled. The thing that made this especially hard to track down was the error would only happen after your session timed out for a second time.
We just released beta 1.12.6 which has a fix for this. Please put it through it's paces and let us know how it goes.
Can you link to the beta 1.12.6 Firefox add-on?
@boberonicus: There is no beta for Firefox. It's something we'd like to offer in the future, but for the time being it's only for Chrome (-based browsers). Sorry.
Thank you so, so much for fixing this. 1Pass is such a good app. This issue plagued me for months but I stuck around because everything else is great. I haven't experienced the problem yet since installing the beta version.
@boberonicus: We actually have an internal Firefox beta but it's not something we share externally very often. I plan on making this public once we polish a few remaining rough edges.
@dteare I've been having this same issue and (at least in my case) I think it may have to do with enabling Two-Factor Authentication. After enabling it on another machine, I was able to sign into my 1 Password account without entering the 2FA code on a different browser, but kept getting the 'Unable to reach server' message when trying to save a Login, after uninstalling and reinstalling the extension, it asked for the 2FA code when signing in, and now I am able to save correctly.
I believe the team have identified a couple of regressions this week that could be the cause of this not being completely squashed. My hope is we'll see the fixes in a new copy of 1Password X soon.
We thought we'd got all of this worked out and at least for most people the current stable seems to have helped. Something could still be amiss though as we have had one or two reports since the last stable.
To help us can you let me know the following.
What version of 1Password X your browser is reporting.
How many 1Password accounts you have connected to 1Password X, their type (just in case it turns out to be a factor) and whether you have 2FA enabled. So I'm thinking something like 2 accounts; 1 Individual with 2FA, 1 Families with no 2FA.
It's just to see if we can sport a pattern in those still affected that might help pin down where the issue lies.