1Password has stopped auto filling password on LOCAL and HTTP addresses [FIXED]
.
My 1Password browser extension has stopped auto filling login details for my LOCAL (http://192.168.x.), none https devices. Other https address' work correctly. I did used to get a prompt asking me if I really wanted to auto fill none secure address', and always said yes and that worked. Now I don't get the option. This occurs in Edge and Chrome so it is not browser specific. I might also add that auto login on local none https site when using 1Password in iOS/iPadOS still works fine.
1Password Version: 8.10.30
Extension Version: 2.23.1
OS Version: Windows 11 23H2
Browser: Chrome
Comments
-
Exact same behavior for me on latest versions, but it's not specific to local addresses. It seems like 1password stopped Autofill on all http:// sites. The secure https:// sites continue to autofill just fine.
Edit: in addition to not autofilling, if I click the 1password icon in Chrome while visiting one of my http:// sites, the extensions hangs with a spinning icon for >5 seconds before opening. This doesn't happen for https:// sites, even if I use an https:// version of the same saved site.
0 -
Yes, I forgot to mention the time lag when initially opening the browser extension. Strange thing is, as I said, I can still log into my http address when using my iPhone or iPad. I still get the warning about accessing insecure sites, but I can chose to except the risk and carry on. The only http address I access are on my local network. If a site in a the web doesn’t use https, then I don’t access it.
0 -
I've got the exact same behavior as well.
1Password Version: 1Password for Mac 8.10.30 (81030032)
Extension Version: 2.23.1 (22300106, on STABLE channel)
OS Version: macOS 14.4.1
Browser: Chrome0 -
I've got the exact same behaviors as well.
1Password Version: 1Password for Windows 8.10.30 (81030032)
Extension Version: 2.23.1 (22300106, on STABLE channel)
OS Version: Windows 11 Pro 23H2 (22631.3527)
Browser: Google Chrome 124.0.6367.92 (Stable)1 -
I have got exact the same behavior. It seems to affect chrome based browsers. In my testing, it only seems to work correctly on Safari.
1Password Version: 1Password for Windows 8.10.30 (81030032)
Extension Version: 2.23.1 (22300106, on STABLE channel)
OS Version: MacOS 14.4.1 (23E224)
Browser: Opera One(Version: 109.0.5097.68) (arm64)1 -
Yes, I agree, I had a senior moment and forgot that both Edge and Chrome are based on Chromium.
1 -
Same here, this needs to be fixed asap!
1 -
Not working any more, please fix
1 -
Same issue here.
I use a lot of internal and some external http sites, if this has been an added "Feature" for security, please allow either a global override via the settings, or a whitelist of websites that are saved already in 1password, because this affects my daily workflow.1 -
I am hoping that this is a bug rather than a security feature. It appears only to be a problem in Chromium based browsers at the moment. Safari on all my I devices, still allows unhindered access. I do not access none https sites off my internal network, but is really is a major inconvenience accessing my home network. Please sort ASAP.
1 -
Adding my name to this list. Same issue, same symptoms, same situations, same platforms, same use-case.
0 -
Same issues:
1Password for Mac 8.10.30 (81030032)
Extension Version: 1Password browser extension version 2.23.1 22300106, on STABLE channel
OS Version: MacOS 14.4.1 (23E224)
Browser: Vivaldi 6.7.3329.17 (Stable channel) (arm64)0 -
I do hope that the 1Password team are reading this. Their silence is deafening.
0 -
Same issue here. This is a big deal. I am an engineer. I use local non https sites for both work and personal local development extensively.
1 -
Same issues across both my Chromium browsers on local addresses. A real pain. Autofill does not work via the hotkey nor clicking on autofill once item is found. Also delay in opening the 1password browser session as if it is searching or something before displaying found item.
0 -
Hello everyone,
I'm sorry that you're unable to fill logins on certain pages when using the latest version of 1Password in the browser. This is a regression that our developers are aware of and affects websites that don't use HTTPS, it's not intended behaviour and an issue has been opened to get this fixed.
When a fix is released, you'll see it noted in our release notes and I'll update this thread: 1Password Releases
For the time being, if the webpage address is correct and trusted, copying your password from 1Password and pasting it into the website in question is the best workaround. Alternatively, you can also drag and drop your login credentials. I'm sorry for the inconvenience and disruption.
-Dave
ref: dev/core/core#29387
3 -
Thank you for your response and I look forward to a resolution soon. It is good to know that it is not a new ‘feature’.
0 -
Autofill on HTTP sites stopped working today. It was working fine for me yesterday. I don't have an SSL cert for development websites that are behind a VPN wall. It still works fine on Production sites, which are identical (except for https:).
I made sure Chrome and 1Pass are up to date.
1Password Version: 1Password for Windows 8.10.30 (81030032)
Extension Version: 2.23.1
OS Version: Windows 10
Browser: Chrome 124.0.6367.920 -
I'm sorry that you're also running into the HTTP filling issue, I've merged your post into the existing thread. This is a known issue that our development team is working on. Please see my previous post here for an update on the current situation.
-Dave
0 -
I can confirm that updating the Chrome1Password Browser extension to v 2.23.3, the problem is resolved. However, the Edge extension v2.23.2 still does not work.
0 -
Edge browser extension is still v2.23.2
0 -
Hello folks,
The team has released a new version of 1Password in the browser that includes a hotfix for an issue where the autofill feature would not work on websites that are not secured via TLS or SSL certificates (the URL starts with https).
Please update to version 2.23.3: How to keep 1Password up to date in your browser
Review times will vary across the different browser stores but hopefully the new version is available everywhere soon. If you do still notice an issue with autofill on HTTP or LocalHost websites after updating to 2.23.3 then please let me know.
Thank you all for your patience while our team worked to release a fix.
-Dave
0 -
Yep, confirmed working now on both Edge and Chrome. The update to 2.23.3 took longer to propagate to Edge, but now all OK. Thank you once again.
0 -
0
