Sync problem - iPhone to PC [Resolved: App Update Fixed Issue]

GoodfellowsIT
GoodfellowsIT
Community Member
edited October 2014 in iOS

I have a client using the 1password trial version to try out if 1password is anything for him. He cannot however sync his iPhone app with his windows browser plugin. I'll post what he reports the problem is and perhaps you can give me some tips of what to look for.

My iPhone says it connects to computer with IP 192.168.2.140:6262.

Then it says ”Sync started”.

Then nothing happens.

After a long while (about 10 minutes) I'll get an error message on my iPhone: ”Sync Problem. The operation coudln’t be completed. Socket is not connected.” Under More Info it says ”Error Domain_NSPOSIXErrorDomainCode=57 ”The operation couldn’t be completed. Socket is not connected”

The computer log file says:

<-- auth --> {"timestamp":1409906881,"session":"FB7F4E47E1794A5395F33C2790D4ABCB","request":"auth","version":1}

<-- {"session":"FB7F4E47E1794A5395F33C2790D4ABCB","request":"handshake","timestamp":1409906755} --> {"timestamp":1409906895,"session":"FB7F4E47E1794A5395F33C2790D4ABCB","request":"handshake","profile":{"lastUpdatedBy":"","profileName":"default","passwordHint":"","createdAt":0,"uuid":"40B1C8DB8569494AADC1322DEFFF3CC5","salt":"dASif853V3ufRv0vh+wV2A==","iterations":10000,"updatedAt":1409906895,"masterKey":"b3BkYXRhMDEAAQAAAAAAAFW7BQ+TI43hetdPHGU0vG/Dgsyi9ZpMiJXMzWV4EdYDNlsfHThk5Ad+j/NX9minYxF2cME7UQ2XJZ8mbfX6ariYugafGXyx6huNYBxR5GtmLidk2MqFPCwttx1x5d1V1VYoXoyzKuQPhpVteNcn4qKsT/gCmWSheUTmksPm10x0jIFHq8zzyDGq3mEQlV8Xv9p4ZCUJi7TaprzR7LUlhxYkgrj4H1I61Ht6RxbF9hQp6jgVy/P3AiLaXL0k+IU2jglrbTPoSfmaI6pZFZGwKGpsecLR4oDfwm7fxtxWRSMoK7VV7K4g2ARMSbPrL3eM7NmnBFU0txgVgT7yYK5Cl/okWCxTLyRataFEPxsCvldhlDyodr7P9gTthXK7GnjqFniiwtQvlh1Sm430Q8NpLnEdtI17fXS1h9jFQ8b+xVm0","overviewKey":"b3BkYXRhMDFAAAAAAAAAAB02Y0cRBzeXFuxLmtLJG/Kvo3ibFpTxTzPZELT6JsqCMfFfK3Nn2OFWh6yFTvNQXpb4D24SuADF6vuWH6luhMyu7cosibbqZJGPcqKXV0067SWsoVfigdF87MuPMmEPDW4Prk+Po6p7ECQV9LmzKsv93ajCdirzrdPV8DO/maLw"}}

I've tried both ”No proxy server” and ”Auto-detect proxy settings”. The log above is from the attempt with ”No proxy server”.

Comments

  • Hi @GoodfellowsIT‌,

    The first things I need to know are the following from your clients devices.

    • Version of iOS on the iPhone.
    • Version of 1Password on the iPhone.
    • Version of Windows
    • Version of 1Password (main app) on Windows.
    • Browser in use and its version.
    • Version of the browser extension in use.

    Also, if they have any antivirus or 3rd party firewalls, it would be helpful to know which one they have. The socket not being connected in the error is a tip off that something is blocking the WebSocket connection hat the extension needs for communication. Make sure 127.0.0.1 is configured to be whitelisted.

  • GoodfellowsIT
    GoodfellowsIT
    Community Member
    edited September 2014
    • Version of iOS on the iPhone: Iphone 4 running IOS 7.1.2 (Build 11D257)
    • Version of 1Password on the iPhone: 4.5.3
    • Version of Windows: Windows 7 pro x64
    • Version of 1Password main app on Windows: 4.0.1.503 Demo

    Browser and extension:

    • Google Chrome Version 37.0.2062.124 m, Browser extension: 1Password: Password Manager and Secure Wallet 4.2.4.90
    • Mozilla Firefox 32.0.3, Browser extension: 1Password 4.2.4
    • Any antivirus or 3rd party firewalls. Vipre Business, no 3rd party firewall
  • Megan
    Megan
    1Password Alumni

    Hi @GoodfellowsIT‌

    Please ensure that Vipre Business has whitelisted localhost 127.0.0.1. :)

  • GoodfellowsIT
    GoodfellowsIT
    Community Member

    The problem appears to have been solved by upgrading to 1Password 4.1.0.526.
    Thanks for the replies.

  • chrisdj
    edited October 2014

    Hi @GoodfellowsIT‌,

    Glad to hear our intrepid developers were able to fix the problem with an update!

    I'm going to go ahead and close this thread, but please don't hesitate to start a new discussion should you need further help with anything, or write our support team at support@agilebits.com. :smile:

This discussion has been closed.