Problem with keychain sync and dropboc

Options
vincentsmyth
vincentsmyth
Community Member

I am running 1Password5 on 3 macs and 2 iOS devices .. and all of them except one of the macs is working fine. On the "problem" Mac ...somehow over the last year dropbox got out of sync and whenever I tried to sync it replicated old entries (that were deleted on the master) back to the master. I therefore deleted all the items in the problem vault to leave it empty and tried to sync via dropbox again but when i send the 1Password.agilekeychain via dropbox it won't sync on the problem machine. Not sure if it is relevant but the keychain file name actually appears as 1Password (1).agilekeychain ... Is this likely to be the problem and if I rename by removing the (1) on the master dropbox will this solve the problem ... or can I just rename the file on the "problem " machine ..., or do yo suspect something else is going on. Thanks Vincent


1Password Version: 1Password5
Extension Version: 5.3.2
OS Version: 10.10.4
Sync Type: dropbox

Comments

  • Drew_AG
    Drew_AG
    1Password Alumni
    Options

    Hi @vincentsmyth,

    I'm sorry you're having trouble with Dropbox sync on one of your Macs! Before getting into troubleshooting, I'd like to point out something very important that I noticed in your message:

    I therefore deleted all the items in the problem vault to leave it empty and tried to sync via dropbox again

    Normally, when sync is working correctly, deleting an item from your vault on one device will delete that same item from your vault on the other devices. Therefore, deleting all items from your vault on one device will delete all of those same items from your vault on the other devices. I'm guessing that's not what you wanted to do, so in this case it's actually a good thing that Dropbox sync didn't work! ;) (It's possible I misunderstood what you meant, but wanted to mention this just in case.)

    So, getting back to fixing the sync problem: I'm glad you noticed the difference between the .agilekeychain data files! If 1Password on the "problem Mac" is syncing with 1Password (1).agilekeychain, and your other Macs and iOS devices are syncing with 1Password.agilekeychain, that means the "problem Mac" is syncing with a completely different/separate sync file than the others. Simply renaming one of those files to match the other won't fix the problem, because they would still be two different files.

    Essentially, you're going to want to start syncing 1Password on the "problem Mac" with the same data file as the others. But first, assuming one of your other Macs has all your latest 1Password data, you should make a fresh backup of that. So, on one of the "good Macs", open 1Password and go to File > Backup. That will open the Backup preferences and show all your backups, including the new one you just made.

    Next, on the "problem Mac", the best thing to do is probably to reset 1Password by following the steps in this knowledgebase article. This is assuming all your latest data is on one of the other Macs, so you won't be losing anything from the problem Mac that you need to save.

    After that, when you open 1Password on the "problem Mac" it will be like the first time, and you'll be able to set it up by syncing your data from Dropbox. When you do that, make sure you choose the same keychain the others are syncing with: 1Password.agilekeychain

    Hopefully this helps, but please let us know how it all goes. Thanks!

  • vincentsmyth
    vincentsmyth
    Community Member
    Options

    Drew, many thanks for this ... I followed the steps 1 by 1 and now it is all working fine ... I will continue to tell friends and colleagues how wonderful 1password is. Now I can also tell them about the fast and effective support. Vincent

  • AGAlumB
    AGAlumB
    1Password Alumni
    Options

    @vincentsmyth: Excellent! Thanks for the update. On behalf of Drew, you are most welcome! I'm glad that worked for you.

    And thank you for the kind words. We do our best to deserve you and the rest of our awesome customers. We're always here if you need us! :)

This discussion has been closed.