1Password Extension stuck loading on all browsers

willaxa
willaxa
Community Member
in Browsers (Edge, Chrome, Firefox, etc.)

Hello,

Is there a timeframe where the 1Password is in maintenance mode? It seems like in the evening 5pm PST onwards it seems to be difficult to login to 1Password via browsers such as Microsoft Edge and Chrome.

Sometimes the when I click on the extension nothing happens, or the login window appears but when I place my user name and password nothing happens. Autofill does not appear and I have to load the website manually and copy and paste the values.

Thank you,
wiL

1Password Version: 7.9.828
Extension Version: 2.2.2
OS Version: windows 11
Referrer: forum-search:1Password Extension stuck loading on all browsers

Comments

  • Joy_1P
    Joy_1P
    1Password Alumni

    Hey @willaxa, sorry about the trouble you're seeing. 1Password was not in maintenance mode yesterday, so there's likely something else going on with the extension in your browser. First, let's try quitting the 1Password app, quitting your browser, and then re-launching both to see if that resolves the issue.

    1. Quit 1Password completely:
    * Open 1Password.
    * Right-click the 1Password icon in the top menu bar and select Quit 1Password Completely.
2. Quit your browser:
    * Open your browser.
    * Click the name of your browser in the menu bar and choose Quit.
3. Open and unlock 1Password.
4. Open your browser and see if the issue is resolved.

    If that doesn't help, I'd like you to replicate the issue and send over the following so we can take a closer look at things:

    Attach the logs and diagnostics to an email message addressed to support+forum@1password.com.

    With your email please include:

    You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!

  • willaxa
    willaxa
    Community Member

    Thank you,

    The information has been sent.

    There seems to be maintenance happening every midnight PST Pacific Standard time?

    Thank you,
    wiL

  • Jack.P_1P
    Jack.P_1P

    Hey @willaxa:

    Thanks for sending it in! We'll take a look, and get back to you via email.

    Jack

    ref: PHS-59152-462

  • willaxa
    willaxa
    Community Member

    Thank you Jack, much appreciated. :)

  • mirv
    mirv
    Community Member
    edited February 2022

    I am seeing this same (or similar?) issue. I'm running MacOS 12.3 Beta (21E5222a), and after updating to this beta OS and beta 1P app today the 1Password extension has been difficult to start up in both Safari and Firefox. The symptoms are:
    1. when I click on the inline 1P icon on a web site, instead of opening the extension window the main 1P.app wakes up and its screen sits in front of the browser without doing anything.
    2. When I go back to the browser there is a little popup that says "Please unlock 1Password from the toolbar icon."
    3. Clicking on the 1P toolbar icon also makes the 1P.app open but then going back to the browser the extension has opened but it is spinning.
    4. Eventually the spinning seems to time out and ask for the master password. At that point I can enter the master password and it will allow me to fill the id/pw.

    I am going to do the above instructions to send logs/diags to the support email address. (Quitting 1P completely per above did not change things at all.)

  • mirv
    mirv
    Community Member

    Bitbot created this support id: [#CQA-78514-417] .

  • Nhat_Nguyen
    Nhat_Nguyen

    Hello @mirv, Thank you very much for reaching out to us. I can't find a ticket with the Mask number you provided, but I think I sent you a response earlier. Let us continue our conversation there, and we can update the results here later.

  • mirv
    mirv
    Community Member

    This problem (at least for me) seemed to be resolved with the latest 1Password for Mac 8.6.0 (80600047, on NIGHTLY channel), as we discussed via email. It's working fine now. Thanks again for the great customer service.

  • Nhat_Nguyen
    Nhat_Nguyen

    Hello @mirv. Thank you for the confirmation. Please feel free to give us a shout if you need anything, and have a great week.

  • jayzed
    jayzed
    Community Member

    I have the same issue with Safari Extension on Mac. It is EXTREMELY unreliable that it literally needs restarts of my Macs several times per day just to get the extension to work. Constant lost contact of the extension with 1 Password.

    I had lodged a bug report with support but after a few back and forth emails they don't seem to have any more suggestions so I have given up on the Beta and gone back to 1Password 7.

    The rest of the Beta 8 App is actually very stable and fast but the extension is unusable in its current state and frankly the Safari extension IS the most important aspect of 1Password so if that doesn't work well the entire app becomes unusable.

  • Nhat_Nguyen
    Nhat_Nguyen

    Hello @jayzed,

    The 1Password app is the best place to manage your data while the 1Password in Safari saves and fills your websites

    That said, I am sorry to hear that it doesn't work for you correctly. If you have time, please send us 1Password logs and a new diagnostics report from your computer to our website here: support+x@1password.com

    You can follow the steps here to create a diagnostics report from your computer:

    https://support.1password.com/diagnostics/

    You can try the steps here to create 1Password's logs: https://support.1password.com/cs/extension-console-log/

  • Zectzozda
    Zectzozda
    Community Member

    Hi, I'm hoping I can piggyback this forum (sorry if necroing the thread), as I'm experiencing the same issue in Chrome. I believe the application used to launch 1Password on Windows 10 if it wasn't running actively or in the background, but doesn't do this at all in Windows 11 Pro. Steps to reproduce:
    1. Turn PC on (cold boot preferably) and 1password startup disabled in Windows
    2. Log into Windows 11 account
    3. Launch Chrome Version 101.0.4951.67 (Official Build) (64-bit)
    4. Go to any webpage (e.g. this forum's login page)
    5. Either click the extension in the extension toolbar or use the keyboard shortcut (I have mine set to Ctrl + comma)
    6. The extension's popup appears with the loading gif for a seemingly indefinite period.

    Workaround:
    1. Open the 1Password app for Windows 11
    2. Sign in
    3. Go back to the browser and retry step 5 above
    4. It will authenticate through

    Logs and other stuff:
    When I was trying to replicate the issue to obtain the console logs, I discovered the 'open 1password' button does nothing despite 1password now running in the background on my Windows 11 Pro system. Clicking this button throws these errors that are in the below spoiler tag (I tried uploading as .log, .txt. .docx and this form disallowed these file types from uploading):

    21:50:35.152 background.js:2 Unable to show the unlock screen 💥 Failed to send because our port was disconnected.
    Eee @ background.js:2
    await in Eee (async)
    t7 @ background.js:2
    get-popup-config @ background.js:2
    await in get-popup-config (async)
    j4 @ background.js:2
    r @ background.js:2
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.393 Unchecked runtime.lastError: The message port closed before a response was received.
    21:50:35.202 background.js:2 Loaded page details in 41 ms.
    21:50:35.202 background.js:2 Analyzed the page in 0.19999998807907104 ms.
    21:50:38.325 background.js:2 Unable to request unlock when not connected to Desktop app
    request-managed-unlock @ background.js:2
    j4 @ background.js:2
    r @ background.js:2
    21:50:50.483 background.js:2 Unable to request unlock when not connected to Desktop app
    request-managed-unlock @ background.js:2
    j4 @ background.js:2
    r @ background.js:2
    21:50:50.939 background.js:2 Unable to request unlock when not connected to Desktop app
    request-managed-unlock @ background.js:2
    j4 @ background.js:2
    r @ background.js:2
    21:50:51.128 background.js:2 Unable to request unlock when not connected to Desktop app
    request-managed-unlock @ background.js:2
    j4 @ background.js:2
    r @ background.js:2
    21:51:09.690 background.js:2 Unable to request unlock when not connected to Desktop app
    request-managed-unlock @ background.js:2
    j4 @ background.js:2
    r @ background.js:2
    21:51:11.930 background.js:2 Unable to request unlock when not connected to Desktop app
    request-managed-unlock @ background.js:2
    j4 @ background.js:2
    r @ background.js:2
    21:51:15.286 background.js:2 Unable to request unlock when not connected to Desktop app
    request-managed-unlock @ background.js:2
    j4 @ background.js:2
    r @ background.js:2
    21:51:24.301 background.js:2 💫 Looking for desktop app com.1password.1password
    21:51:24.301 background.js:2 📤 Sending message to native core <2108836374>
    21:51:34.316 background.js:2 💫 Looking for desktop app com.1password.1password7
    21:51:34.316 background.js:2 📤 Sending message to native core <1556687102>
    21:51:34.316 background.js:2 Desktop app port disconnected. Error: Specified native messaging host not found.

This discussion has been closed.