Chrome Extension will not open some links [Result of missing http or http:// protocol, edit to add]

edited November 2014 in Mac

Hi,

I'm having a problem and couldn't find anything on the forum about. I use Chrome on a Mac (the latest version Version 38.0.2125.111), and am running 1Password 5 (Version 5.0.1 (501000) Agile Web Store) and when I use the browser extension, most links open with no problem, but some refuse to open. I first noticed the problem on an older version of 1Password on my wife's computer when I was getting it set up for her, but I've since experienced it myself on my own system. Here are the steps that produce the problem:

  1. Open Chrome
  2. Click the 1Password extension
  3. Enter master password to unlock 1Password
  4. Search for a login and press enter

For most logins, this opens the link saved in the login, and autofills the username and password, and submits the form. But for others, I get an error from Chrome: "This webpage is not found." A concrete example URL in the address bar is

chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk/www.massmutual.com

The details say that there was no webpage for this address, but I've verified that the URL saved in 1Password is correct. It has an error code:

Error code: ERR_FILE_NOT_FOUND

This happens on my wife's computer for her Gmail login, but my Gmail login works fine. I can't figure out what's going on. Thank you for your help!

Comments

  • MikeTMikeT Agile Samurai

    Team Member

    Hi @the_jazzman17‌,

    Can you edit the item to include the http:// or https:// in the website field, it might happen because there is no http protocol at the beginning. Once you do that, see if opening it from the extension will work now.

  • Hi! Yes, that seemed to fix the problem. I'll go through and make the changes on all the logins that aren't currently working. Strange though! Thank you!

  • MikeTMikeT Agile Samurai

    Team Member
    edited November 2014

    Hi @the_jazzman17‌,

    Thanks for the confirmation. We're not sure why it is a recent problem but we'll investigate further to see if we can issue a fix for this in our code.

    Bug ID #: OPX-579

This discussion has been closed.