1Password for Windows 10 Version 7.2.617 does not sync my items anymore -> Folder offline changes

Changes on my windows PC are not synchronized with my 1Password Account on 1Password.com and vice versa.
On the windows app I see a new folder in the app called 'Offline changes' with all the changes on the PC.

In the current log file I find entries like

W400238msThreadId(3)1Password::api:1796 │ 400243ms │ Network request #7 timed out in 100.003ms
W400239msThreadId(3)1Password::api:1796 │ 400244ms │ failed to check for updates
W400239msThreadId(3)1Password::api:1796 │ 400244ms │ Failed to download updates manifest from https://c.1password.com/dist/1P/win6/updates.json

but https access in browser (Chrome) is succesful
-> https://c.1password.com/dist/1P/win6/updates.json
{
"*": {
"stable": { "version": "7.2.617", "url": "https://c.1password.com/dist/1P/win6/1PasswordSetup-7.2.617.exe" },
"beta": { "version": "7.3.619", "url": "https://c.1password.com/dist/1P/win6/1PasswordSetup-7.3.619.BETA.exe" },
"-nightly": { "version": "7.3.639", "url": "https://c.1password.com/dist/1P/win6/1PasswordSetup-7.3.639.BETA.exe" },
"-test": { "version": "7.3.639", "url": "https://c.1password.com/dist/1P/win6/1PasswordSetup-7.3.639.BETA.exe" }
}
}

What is wrong?


1Password Version: 7.2.617
Extension Version: Not Provided
OS Version: Win 10 1809
Sync Type: 1Password.com
Referrer: forum-search:1Password for Windows 10 Version 7.2.617 does not sync my items anymore-> Folder offline changes

Comments

  • brentybrenty

    Team Member

    @BlubbBlubber: This indicates a pretty serious network issue in your system:

    W400238msThreadId(3)1Password::api:1796 │ 400243ms │ Network request #7 timed out in 100.003ms

    Did you just start having problems recently? Definitely try restarting Windows.

  • In the meantime the problem disappeared.
    I don't know why because I did not restart the system.
    All other applications had no problem with the network.
    Seems as if a 1Password server did not respond.
    Perhaps a concret IP adress in the logs would be helpful.

  • MikeTMikeT Agile Samurai

    Team Member

    Hi @BlubbBlubber,

    I'm glad to hear it came back online. I have a feeling it is due to our current network stack we're using; for an example, the way it takes 100 seconds to time-out a network request in your logs. It already went through 7 network requests, that's 700 seconds already without a successful connection. Normally, other apps have a shorter timeout and can reconnect faster.

    We're planning to switch away from Microsoft's .NET network stack to build our own that'll use the native Windows network APIs directly to manage the network requests ourselves, so we can reconnect faster.

This discussion has been closed.