Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
brianoflondon
1 month agoNew Contributor
Has something changed: http:// not filling in any more?
For passwords I have that are specifically http:// like on my own Lan, these aren't being suggested any more by 1Password extension in Brave. Anything https:// is working.
And yes I have http:// set as the Website address.
I'm sure this was working until very recently.
Hey everyone! đź‘‹
We’re testing a fix for HTTP filling, including non-HTTPS localhost setups. That fix is already live in the nightly version of the browser extension, and assuming things look good, we’ll roll it into beta and then production next. For now, the workaround is still to copy and paste or drag and drop your credentials.
If you’re willing to help us test, you can grab the nightly builds here (there is no nightly version for Safari): Use 1Password beta or nightly releases
Appreciate everyone’s patience here. If you try the nightly and notice anything weird, definitely give us a shout here in the thread.
46 Replies
- Juiceof2limesNew Contributor
Also have the same issue with Edge browser on local LAN sites, yet Chrome not affected.
1Password for Windows 8.11.23 (81123001)
1Password browser extension version 8.11.22.27 - UrsaBearNew Contributor
Based on my observation, it is likely that the 8.11.22 version of the browser extension in the Edge extension store introduced the use of the window.crypto.randomUUID method.
However, the window.crypto methods can only be used in localhost and HTTPS environments (See: https://developer.mozilla.org/en-US/docs/Web/API/Crypto/randomUUID). In HTTP environments, it reports the error “window.crypto.randomUUID is not a function”, which causes the auto-fill feature to fail.
Currently, I have switched to version 8.11.20.39 from the Chrome extension store, and it is still working fine.
- passion_to_liveNew Contributor
i alse installed older version:8.11.18.36 that autofill works well for me, but when i reopen chrome for updating, the 1P extension will auto update to latest version, and autofill fail works again.... and i re install 1P ex older version .....
- CamFlyerCHNew Contributor
I installed also this older version and it fixes it for now ..
- 1P_Blake
Community Manager
Hey brianoflondon​! We’ve seen a few similar reports recently about this, so were currently investigating internally.
When you have a sec, could you share which version of Brave you’re running, and which version of the 1Password browser extension you’ve got installed?
- brianoflondonNew Contributor
I thought I replied to this but it failed to post. Probably copied in some html.
I was on an older version of Brave, it updated and seems to have fixed this issue.- 1P_Blake
Community Manager
Thanks for sharing that! I've included it in our investigation.
- brianoflondonNew Contributor
A funny thing happened on my way to finding my Brave version. I think I hit reload and got an update. And now the behaviour I was seeing earlier today and for the last day or two seems to have gone!

Brave is up to date
Brave 1.85.116 (Official Build) (x86_64)
Chromium: 143.0.7499.110

1Password – Password Manager
8.11.20.39

I have a sneaking suspicon I was on:
Release Notes v1.85.111 (Dec 3, 2025)
Because I had a left over tab.
- WackyWRZNew Contributor
Seeing similar behavior for things on my own lan as well not autofilling in Edge (Unraid webgui for example). Even if using https but "insecure site" it won't autofill, suggest, or even save. It was working earlier in the week for sure.
EDIT: Looks like it may be a known issue - https://www.reddit.com/r/1Password/comments/1pitywa/autofill_is_not_working_in_edge_on_http_sites/