1Password for Windows desktop has stopped working...

leesweet
leesweet
Community Member
edited April 2023 in 1Password 7 for Windows

Just loaded the beta and started getting this popup with the close/debug. After some checking, it looks like it's from the Firefox 1P plugin. I deleted and reinstalled the plugin, no change. I also did the same to Chrome, it doesn't have an issue.

I also keep getting refused connections from Firefox which are probably the cause of the popup (I see the refused connections in Windows and in the 1P/Settings/Browsers , so that also looks like the issue). The plugin installs just fine, so what would be the root cause here? The only thing out of 'normal' is that FF is 60.0B5, but would that be this weird? We're up to 59 for 'normal' now.


1Password Version: 7.0.529
Extension Version: 4.7.0.90
OS Version: Win10 1709
Sync Type: Dropbox

Comments

  • leesweet
    leesweet
    Community Member

    To add, it's not the FF beta, loaded on my home Windows 10 PC (same version, same FF), no issues.

    Only other thing I can think of is that the work laptop has Fiddler on it... that does things with certs, and I'll see if I can uninstall it, since I don't use it.

    Any other ideas? Thanks!

  • leesweet
    leesweet
    Community Member

    Ugh... turned off the firewall, redid the FF Plugin and now it seems to be fine. I would have thought if it was a firewall issue, it would have had the usual popup requesting connection permission.

    Unless someone has a comment, we can count this closed.

  • Lars
    Lars
    1Password Alumni

    @leesweet - I'm not really certain why you experienced what you did...but for now, if you've resolved the issue, I'm content to let it go if you are. Keep an eye on it, and let us know if you experience any further issues.

  • Hi @leesweet,

    Thanks for reporting this. Can you email us your 1Password diagnostics report, it may have some logs that we can use to understand what happened. Please use this guide to generate the report and email it to us at support+windows@agilebits.com. Also, in the email, include the link to this thread along with your forum username, so that we can connect the email to this thread.

    Let us know here when you've sent it, so we can confirm we got the email.

    In addition, can you tell me if you're using McAfee anti-virus solution or if not, which solution you're using?

  • leesweet
    leesweet
    Community Member

    Mike, sure thing, done. AV is Windows Defender, nothing special. Since this worked after many tries when I turned off the firewall (Windows Firewall Control), pretty sure that was it, but it's still weird it didn't do it's normal prompting for allowing a connection.

  • leesweet
    leesweet
    Community Member

    Sigh.... Getting the same issue this morning and since I tied it down to the Windows Firewall Control, I now figured it out. The new version of WFC installed a few weeks ago seems to come with notifications disabled by default. That may help others that use Windows Firewall Control (it sits on top of the normal Windows Firewall and lets you control what gets in to your PC). Since the notifications were off, there was no way to enable things you actually wanted to run.

    Once notifications were again popping up and you could enable connections you wanted, the FF plugin connection worked with no issue.

  • AGAlumB
    AGAlumB
    1Password Alumni

    @leesweet: Aha! Thanks for letting us know. I know I've had issues with updates changing some settings on me. But the one thing I don't understand is how the firewall could interfere with 1Password in this case. Is it blocking apps, not just network connections?

  • leesweet
    leesweet
    Community Member

    There has to be some sort of internal localhost connection when the app tries to install the plugin (the connection between the app and the browser), is all I can think of. As soon as I opened up WFC (when I didn't know it wasn't allowed to ask for things...), it worked fine. Perhaps the plugin team can advise? :)

  • Hi @leesweet,

    Thanks for these details.

    There is no internal localhost connections or any network code involved in 1Password extension for Firefox, we've removed all traces of it when we switched to WebExtension and Native Messaging. Native Message allows 1Password extension to directly connect to the running 1Password's process.

    The only thing I can think of is that Firefox launches our native messaging process via Explorer.exe, it is possible there was some unintended interaction between WFC and explorer.exe/Firefox that prevented it from launching our process.

    I use WFC on my machines and I didn't notice any breakage. I'll investigate to see what it may be.

  • leesweet
    leesweet
    Community Member

    Yes, there was also a connection to explorer showing in the refused connections list when things weren't working. Which I couldn't figure out what was 'explorer' doing talking to the browser plugins....

    If it helps at all, I use WFC in 'Medium' mode. 5.1.0.0 is the current version, as you no doubt know, and I think the 'no notifications' crept in when version 5 appeared (but that could be something weird that only happened to me). Recently I've been prone to turning WFC off whenever launching a new collaborating software install (everyone seems to have their own), and now I know why I had to resort to this, the WFC notifications were off!

  • AGAlumB
    AGAlumB
    1Password Alumni

    Yes, there was also a connection to explorer showing in the refused connections list when things weren't working. Which I couldn't figure out what was 'explorer' doing talking to the browser plugins....

    @leesweet: Aha! That makes sense. Yeah, explorer.exe is the Windows shell, so that launches Firefox which in turn starts the Native Messaging host...which is how 1Password connects to Firefox. A lot of moving parts there to allow the main 1Password app to integrate with the browser.

    If it helps at all, I use WFC in 'Medium' mode. 5.1.0.0 is the current version, as you no doubt know, and I think the 'no notifications' crept in when version 5 appeared (but that could be something weird that only happened to me). Recently I've been prone to turning WFC off whenever launching a new collaborating software install (everyone seems to have their own), and now I know why I had to resort to this, the WFC notifications were off!

    That's really helpful. Thank you! Glad it all worked out in the end. Cheers! :)

This discussion has been closed.