Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Solved
Autofill no longer works on HTTP pages; iOS shows white blank screen
I’m running into an issue where 1Password can’t fill on any http:// pages across multiple platforms, and on iOS it can even result in a white/blank screen when I try to fill.
What’s happening
- iOS (1Password app + Safari extension): On http:// pages, 1Password cannot autofill. When I invoke 1Password to fill on an HTTP page, the 1Password UI becomes a white/blank screen.
- Chrome / Edge extension (desktop): Autofill does not work on http:// pages at all.
- macOS app / Safari (macOS): Same behavior — no filling on http:// pages.
Expected behavior
I understand HTTP is insecure, but I still expect either:
- autofill to work (possibly with a warning/confirmation), or
- a clear message explaining that filling is blocked on http:// pages — not a blank/white screen on iOS.
Notes / why this matters
These http:// sites are mostly local network / self-hosted services that don’t have HTTPS enabled yet (or are reachable only via LAN IP/hostnames). So “just use HTTPS” isn’t always possible.
Also, I saw other reports that HTTP filling stopped working recently in some extension versions (people mentioned it worked again after downgrading), so I’m wondering if this is a regression. 1password.community
Steps to reproduce (iOS)
- Open Safari on iOS and go to an http:// login page (example: http://[local-address]/login).
- Tap into the username/password field and try to fill with 1Password (AutoFill or Safari extension pop-up).
- Result: no autofill; in some cases the 1Password UI turns into a white/blank screen.
My environment
- iOS: 26.2
- 1Password for iOS: 8.11.22
- macOS: 26.2
- 1Password for macOS: 8.11.22
- Browser: Chrome 143.0.7499.170 / Edge 143.0.3650.96 / Safari 26.2 (21623.1.14.11.9)
- 1Password browser extension: Chrome/Edge 8.11.27.2、Safari 8.11.22.27
What I’ve tried
- Restarted browser(s) and device(s)
- Updated 1Password apps and extensions
- Re-enabled / reinstalled the extension(s)
- Confirmed the Login item is correctly associated with the site
Could you confirm whether filling on http:// pages is supposed to be blocked now, and if not, whether this is a known bug/regression?
If you need diagnostics/logs, tell me what to collect and where to send them.
Hi everyone, thanks for reaching out.
Our developers are aware of this issue and have a fix that is being tested in our current Nightly release for the browser extension. Once the fix has passed through the testing in the nightly release it will move to our Beta release and finally to the Production release.
If you are interested in using the Nightly release of the browser extension you can install the nightly release by referencing the details found on the page linked below:
As an alternative to testing the nightly release you can also use the Drag and Drop functionality in 1Password on Windows, Mac, and Linux devices to make filling the details on an HTTP page slightly easier while we wait for the fix to be released in the production version.
If you're using an iOS device, you can tap and hold a login field on HTTP pages > choose Autofill > Passwords > and then select the login item in the 1Password app.
I understand these workarounds are not ideal and I apologize for any inconvenience caused. Let us have any questions!
- FS-4500
9 Replies
This has been an issue for me for some time. I don't come to the forums often so me getting to this point is rather telling.
I thought part of the reason for subscription costs was to help speed up development and ensure consistency and a solid product. These types of issues are seemingly cropping up more and more and it's getting frustrating. This type of feature "breaking" should have been fixed within days, not weeks...
The scope of this issue's impact is so large and it has lasted so long; it has not been fixed until now (nearly a month), which is completely unacceptable.
HTTP autofill, such an obvious and commonly used feature, surprisingly went unnoticed for issues across multiple release stages (nightly, beta, production). The funniest part is that fixing this bug also has to go through nightly, beta, and production versions.
It gradually becomes hard to trust.
By the way, at the very beginning of the issue, I searched the community and found that people had already reported this problem in the nightly and beta versions before the production release. XD
There're still many HTTP website, such as intranet in enterprise, please don't remove HTTP autofill function again.
Does your team knows how many user were influenced by this update? Maybe you can do a survey. I think this is a P0-level bug. Because it's been a while, and people who came here because they know it may caused by HTTP autofill.
But I think most user they don't know what's going on and why so many websites can't autofill, so they don't came to this community.
You can just see how many issues were posted recently was related to this bug, and how many views on this post. So please fix this ASAP.
I've been always satisfied with 1Password, and paid for many years. I always recommand 1Password to my friends. But I just a little disappointed this time, it's been 3-4 weeks I think, you still didn't fix it.
Same here. I don't use a socket layer on internal IP for my cameras. This is bit frustrating.
ChrisC1PModerator
Hi everyone, thanks for reaching out.
Our developers are aware of this issue and have a fix that is being tested in our current Nightly release for the browser extension. Once the fix has passed through the testing in the nightly release it will move to our Beta release and finally to the Production release.
If you are interested in using the Nightly release of the browser extension you can install the nightly release by referencing the details found on the page linked below:
As an alternative to testing the nightly release you can also use the Drag and Drop functionality in 1Password on Windows, Mac, and Linux devices to make filling the details on an HTTP page slightly easier while we wait for the fix to be released in the production version.
If you're using an iOS device, you can tap and hold a login field on HTTP pages > choose Autofill > Passwords > and then select the login item in the 1Password app.
I understand these workarounds are not ideal and I apologize for any inconvenience caused. Let us have any questions!
- FS-4500
I also have this issue on our intranet which is http. (It used to autofill for years, no longer does now.) Windows 11 - Firefox, Edge or Chrome.
I've encountered the same issue, and it stops me from using 1Password to log into my router as well as my local Raspberry Pi Homebridge setup.
