1PX FF lagging with synch

Hi,

My 1PasswordX's (Firefox, MacOS, Linux) are often lagging behind with synch or maybe not synching - who would know?

Is there a way to force/trigger a synch besides closing the browser? Closing the browser is quite annoying since many sites require re-login apart from the fact that I need to enter the password for 1PasswordX again as well.

Thanks
b


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

Comments

  • Add: I have a similar issue when I update the password of an account using the 1Password Browser extension since the Password Generator works better there. Afterwards 1PX seems not yet to know/have the new Password.

  • jxpx777jxpx777 Code Wrangler 1Password Alumni

    Hi, @binaranomaly. 1Password X behaves similar to other clients in that it gets notified by the server when there are changes and then syncs those to its local cache. This should be quite quick, but it could take a few seconds. If you save/update a Login in 1Password for Mac, then it might take up to a few seconds for it to sync that to 1Password.com. Then, 1Password.com would notify the connected 1Password X and it would trigger a sync there as well. So, it could take a few to several seconds. Any more than that and I think we'd have to consider it an opportunity for improvement. You might be able to trigger a sync by going to Tools > Add-ons and disabling/reenabling 1Password X, but if you find that's necessary, it might be worth trying to pin down the problem a little more precisely.

    Let us know what you find or if we can help further.

    --
    Jamie Phelps
    Code Wrangler @ 1Password
    Fort Worth, Texas

  • Thanks @jxpx777 for the explanation of the underlying mechanism. If I recall correctly I waited more than just a few seconds and the items still didn't show up.

    The problem of the current state and available info is: You wouldn't know wheter it is dead or slow... i.e. I'd find it helpful to be able to see when the last synch happened, if one happened at all and whether if failed or was successful.

  • Just tested it again @jxpx777

    Setup: Debian stable, FF60, 1PX
    Action: Open 1PX select item, click edit, 1password in browser opens, change title of item, save
    Result: 1PX still not updated after minutes, 1Password iOS synched after seconds

  • beyerbeyer

    Team Member

    @binaranomaly: Can you please try removing your 1Password account from the 1Password X settings page and then adding it again?

    After doing so, can you try editing the same item again and seeing if it updates in 1Password X?

    -Beyer

  • @beyer Did so and at least for the moment when I tested it was in synch on the spot. Hope it stays...

  • brentybrenty

    Team Member

    Sounds good! Hopefully you don't run into any further issues, but we're here if you need us. :)

  • @beyer: Just happened again (guess I'm not editing that often...). Closing and re-opening the browser fixed it. Still not superb since I have to re-enter the password, re-login, etc.

  • junkmanjunkman
    edited June 2018

    I was having sync problems too, but it seems the suggestion by @beyer fixed it. I created a new login on my iPhone, but it never updated in 1Password X. I am running Firefox 60.0.1 on Fedora 28. However, when I close and then reopen Firefox, the problem comes back. I currently have Firefox to clear all History and Data when closing.

    Didn't help:

    • Disabling/enabling the add-on
    • Closing/opening Firefox
    • Completely removing add-on then reinstalling it (this updates everything, but changes from then on still don't sync)
      Does help:

    • Remove 1PasswordX account from 1PasswordX settings page, and then add it again.

    I was having two other problems which seemed to be fixed by removing/adding back my account via 1PasswordX settings:

    • I couldn't not save a new login. The window popped up "Save in 1Password" and I clicked "Save", but I got the error: "We were unable to reach the server. Please check your internet connection and try again." Now this works.
    • When I clicked on "Edit" for an item in the 1PasswordX pop-up, it would open a new tab but wouldn't ever load. The icon just keep spinning forever. Now this works as well.

    Any suggestions?

    I really like 1Password and 1PasswordX. @brenty @beyer Thanks for making a great product and being very helpful/responsive on the support forums.

  • Synch just broke down again completely here. I had to re-register again from scratch.
    Would dare to say that we most likely have an issue here.

  • dtearedteare Agile Founder

    Team Member

    Thanks for following up on this, @binaranomaly.

    @junkman: those issues you fixed by reinstalling 1Password X reminds me of a similar problem that would happen after changing your Master Password, Secret Key, or 2FA. Did you happen to change any of those around the time that this issue started affecting you?

    I wonder if the clearing all History and Data when closing is related. 🤔

    In any event, could both of you look in the browser console to see if there are any errors there?

    Unfortunately this log tends to be very chatty with a lot of noise, but if you enter background.js into the filter, it should narrow things down to the important bits.

    I'm guessing there's some errors there for you. Let's see and go from there! 🙂

    ++dave;

  • Thanks @dteare.

    Ironically I now just had a problem in the other direction, Linux 1PX FF was editing/updating an item fine but 1PW and 1PX on Mac were not updating.
    1. Had to quit 1PW Mac completely - now in synch
    2. iOS was fine
    3. 1PX FF on Mac is still not in synch (after hours)

    I'm seeing lots of these:

    15:04:21.757 [_request] Request "/api/v1/session/touch" failed: ServerError: Authentication required.
    Stack trace:
    [email protected]://69324181-62a2-174b-b01b-4312278d223a/background/background.js:1:929200
    e/[email protected]://69324181-62a2-174b-b01b-4312278d223a/background/background.js:1:1118198
    [email protected]://69324181-62a2-174b-b01b-4312278d223a/background/background.js:1:1317529
    c/<@moz-extension://69324181-62a2-174b-b01b-4312278d223a/background/background.js:1:1317225
    [email protected]://69324181-62a2-174b-b01b-4312278d223a/background/background.js:1:1457524
    [email protected]://69324181-62a2-174b-b01b-4312278d223a/background/background.js:1:1457702
    [email protected]://69324181-62a2-174b-b01b-4312278d223a/background/background.js:1:1458221
    1 background.js:1:817699
    f/e[t] moz-extension://69324181-62a2-174b-b01b-4312278d223a/background/background.js:1:817699
    e/this._request/</< moz-extension://69324181-62a2-174b-b01b-4312278d223a/background/background.js:1:1117145

    I have the feeling no matter what OS 1PW/1PX have recurring synch problems especially after a computer is being woken up from sleep...

  • brentybrenty

    Team Member

    @binaranomaly: Interesting. Certainly that doesn't help things, but maybe there's something we can do to try to work around it. If you lock and unlock 1Password again, does that help at all?

  • If you lock and unlock 1Password again, does that help at all?

    Sometimes it did and sometimes I had to re-register...
    I think it would be more beneficial to identify and solve the root cause of these issues since the workarounds are not a real solution.

  • brentybrenty

    Team Member

    I think it would be more beneficial to identify and solve the root cause of these issues since the workarounds are not a real solution.

    @binaranomaly: Yep. That's what I'm trying to do. You're the only one seeing this as far as I'm aware, so I was hoping you'd be willing to troubleshoot a bit. What does this mean?

    Sometimes it did and sometimes I had to re-register...

    By "re-register" are you signing up for a new account? You mentioned it earlier, but I'd like to understand exactly what steps you're taking. What if you use 1Password X in a new profile? Do you see the same issue there?

  • What does this mean?

    Sometimes locking/unlocking helped. Other times I had to remove the account completely as suggested previously in the thread by @beyer. But that is retrospective and was with FF60.

    You're the only one seeing this as far as I'm aware, so I was hoping you'd be willing to troubleshoot a bit.

    Hard to imagine but maybe I'm using it more intense/often than the average user or the FF mac/debian constellation is also not that common.

    One of the main problems is that there is no log that can easily be consulted to see what is really going on - or not. That makes analysis difficult and opaque. Try this, try that, etc, etc. A "could not synch because of xyz..." log entry would be worth a lot.

    The issue does not occur constantly just every few days when adding/editing an item (and usually when I am in progress of doing something completely different than troubleshooting 1PX).
    I don't have the issue right now the Firefox 61 update forced me to re-login (and maybe that also changed something behind the scenes)? Maybe I'll run into it again the next time I update an item, keep you posted and will check the Browser Console as suggested by @dteare.

  • Just had an out of synch situation again, lock and unlock helped.

    Browser console:

    17:38:15.323 Error: Promised response from onMessage listener went out of scope
    background.js:1:1204725
    17:38:24.874 [Show/hide message details.] detailsUrl.contains is not a function
    background.js:288
    17:38:27.997 Error: Promised response from onMessage listener went out of scope
    background.js:1:1204725
    17:39:21.709 Error: Promised response from onMessage listener went out of scope
    background.js:1:1204725
    17:42:57.733 [Show/hide message details.] detailsUrl.contains is not a function background.js:288
    17:43:00.604 [Show/hide message details.] detailsUrl.contains is not a function background.js:288
    17:43:00.809 [Show/hide message details.] Unchecked lastError value: Error: document.body is null background.js:1
    17:43:13.001 Error: Promised response from onMessage listener went out of scope background.js:1:1204725
    17:43:13.003 Error: Promised response from onMessage listener went out of scope
    background.js:1:1204725
    17:43:13.004 Error: Promised response from onMessage listener went out of scope
    background.js:1:1204725
    17:43:19.409 Error: Promised response from onMessage listener went out of scope
    background.js:1:1204725
    17:43:25.759 Error: Promised response from onMessage listener went out of scope
    background.js:1:1204725
    17:47:33.822 Error: n is null background.js
    17:47:37.598 Error: n is null background.js
    17:47:37.620 Error: Promised response from onMessage listener went out of scope background.js:1:1204725
    17:47:37.622 Error: Promised response from onMessage listener went out of scope
    background.js:1:1204725
    17:47:37.623 Error: Promised response from onMessage listener went out of scope background.js:1:1204725
    17:47:43.472 Error: Promised response from onMessage listener went out of scope
    background.js:1:1204725
    17:48:37.765 Error: Promised response from onMessage listener went out of scope
    background.js:1:1204725
    17:51:14.320 TypeError: this.CTX.account is undefined background.js:1:1221852
    17:53:44.984 Error: Promised response from onMessage listener went out of scope
    background.js:1:1204725
    17:53:44.988 Error: Promised response from onMessage listener went out of scope
    background.js:1:1204725
    18:47:16.192 Error: n is null background.js
    18:47:24.247 Error: Promised response from onMessage listener went out of scope
    background.js:1:1204725
    18:47:24.250 Error: Promised response from onMessage listener went out of scope background.js:1:1204725
    18:47:24.250 Error: Promised response from onMessage listener went out of scope background.js:1:1204725
    18:47:30.495 Error: Promised response from onMessage listener went out of scope
    background.js:1:1204725
    18:50:41.371 [LM] Locked at Sun Jul 01 2018 18:50:41 GMT+0200 (CEST) background.js:1:1238810
    18:50:41.466 [Show/hide message details.] Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist.
    background.js:1
    18:50:54.463 PBES2g-HS256(100000): 164ms background.js:1:875287
    18:50:54.551 [Show/hide message details.] Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist.
    background.js:1
    18:50:55.918 [action/Session#verify] background.js:1:780302
    18:50:55.920 [action/auth#signInWithEmailAndPassword] background.js:1:780302
    18:50:56.206 PBES2g-HS256(100000): 144ms background.js:1:875287
    18:50:56.393 Signed in sucessfully to removed @ removed with MFA and loaded account details. Elapse time 1551ms. background.js:1:1219395
    18:50:56.443 account info was up-to-date for account <removed> background.js:1:1223271
    18:50:56.443 keysets were up-to-date for account <removed> background.js:1:1223558
    18:50:56.511 updated vaults for account <removed> background.js:1:1225714
    18:52:14.462 Error: Promised response from onMessage listener went out of scope
    background.js:1:1204725
    18:53:18.747 Error: Promised response from onMessage listener went out of scope background.js:1:1204725
    18:53:18.748 Error: Promised response from onMessage listener went out of scope background.js:1:1204725
    18:56:34.273 Security Error: Content at moz-nullprincipal:{18a3d9bc-b813-b346-ad42-fc0b056ff6c7} may not load data from moz-extension://69324181-62a2-174b-b01b-4312278d223a/background/background.js.

  • Hello,
    just my 2 cents to letting you know that it happened to me too. @binaranomaly you are not alone and this was with 1passwordX 1.8 and Firefox 61 on macOS.

  • daltondalton

    Team Member

    @Ashokleyland: Thanks for letting us know you're seeing this behavior too.

    @binaranomaly: Thank you for all of the helpful details you have provided. We've been able to reproduce this behavior on our end and are looking into the best way to fix it. Essentially, 1Password X is failing to sync properly after being unlocked for an extended preriod of time. If you have Automatically lock 1Password disabled and allow your computer to sleep for ~30 minutes or more, you're more likely to experience this issue. For now, locking/unlocking 1Password X should allow syncing to resume as expected. Thanks for reporting this and for being so patient while we investigated the issue.

    ref: b5x-482

  • Thanks for the good news @DaltonD! Happy, I was not seeing ghosts ;) and of course looking forward to a future fix. Good success.

  • daltondalton

    Team Member
    edited July 2018

    @binaranomaly: I believe you're running into a real issue so I'm glad you reported it to us. 🙂 Have a great rest of your week!

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file