Prospective Customer

Environment: Win7 64bit, 1Password 1.0.9.299, Firefox 15.0.1, Android ICS

I've just installed 1Password and am finding my way around. it appears to be architected around a core Windows application and a satellite apps for one or more browsers (Firefox in my case). The Android app has limited functionality but is good enough for the moment - just means that changes must be applied from Windows.

Surely a basic requirement is seamless 2-way synchronisation between changes made in the Windows application and the browser app(s). Changes made in either one should be reliably reflected in the other. In my experience this does not reliably happen. There are obvious problems anyway e.g. what happens if a change in the Windows application are made and the browser app(s) are not active? Or vice versa? Are they queued somehow? Or do they just fail? In my testing both Firefox and the Windows application were running concurrently when changes were made yet sometimes an error was reported and sometimes the sunc simply fails.

This synchronisation issue is no doubt challenging because you are at the mercy of third party software changes. If you had your own browser you would be in complete control - but you are not: People want to run Firefox, Chrome etc. My fear is that updates to people's favourite browsers will occur and that these will render 1Password unusable until 1Password catches up.

Other gripes stem from the origins of 1Password. Why no localisation of input proformas e.g. for banks? Or better still make input proformas editable? Neither do I wish to see vestigial remains of Apple Mac stuff when I'm running Windows.

There is a a lot to like in 1Password but I have serious concerns.

Comments

  • khadkhad Social Choreographer

    Team Member
    edited October 2012
    Welcome to the forums, xermes! Thanks for your interest in 1Password. :)

    1Password manages the exchange of data between itself and the browser extensions through WebSocket connections. This allows the 1Password background process to communicate with the browser extensions while still respecting the “sandboxing” rules enforced by modern web browsers.

    If the connections are blocked for any reason, the extension will not be able to connect to 1Password, and no data transfer can occur. The most common symptom of this problem is a “helper not connected” message from the browser extension. The simplest solution is to ensure that local connections are not blocked on 127.0.0.1 by a proxy server or software firewall.

    The specific ports that 1Password uses through its WebSocket connections are 6258, 10191, 14821, 24861, 25007, 38151, 46360, 49801, 55730, and 59483; but it’s much easier simply to allow all connections to 127.0.0.1 (localhost).

    Please review our troubleshooting guide for data not being in sync between the main 1Password application and the browser extension(s), and follow each step carefully:

    http://help.agilebit...-connected.html

    Since the most common cause is a proxy server or other "Internet security" programs blocking the secure connection between the sandboxed browser extension and the main 1Password program, solutions to some common configurations are provided in the guide, and the latter has its own page linked in step seven:

    http://help.agilebit...figuration.html

    Please let me know how it goes and if the above applies to your situation.

    If you're still having trouble, could you please send us your Diagnostics Report? Select Help > Diagnostics Report > Export to File from the menu bar in 1Password. Then attach the report to an email to us: support AT agilebits DOT com

    Once we see your report we should be able to help more. Thanks in advance!
This discussion has been closed.