Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Solved
Beta version not working on HTTP sites
There's another issue with this build: the extension stopped working on http sites at all. The autofill buttons do nothing either.
Hello everyone,
Our development team has released a fix for an issue that prevents 1Password from filling login credentials on HTTP websites, including non-HTTPS localhost websites. The fix is included in the latest stable version of 1Password in the browser (8.11.29.1 or later) and is available in the Chrome Web Store and Apple App Store with the Firefox version being reviewed and set to be released as soon as possible.
I'm sorry again for the inconvenience that the issue is caused. If you still experience issues after updating to 8.11.29.1 then let me know and I can help further.
-Dave
1P_Dave
Moderator
ModeratorHello folks,
Our development team is currently testing a fix for an issue that prevents 1Password from filling login credentials on HTTP websites, including non-HTTPS localhost websites. The fix is currently available in the nightly version of 1Password in the browser and we hope to release it to the beta and production versions as soon as possible. For the time being, the best workaround is to copy and paste (or drag and drop) your login credentials into the website in question.
If you'd like to help us test the fix then you can find the nightly version for various browsers here (there is no nightly version for Safari): Use 1Password beta or nightly releases
-Dave
Hi1P_Dave thanks for the update and reply. Do you think that a month turn around for this vital issue is an acceptable timeframe for your customers?
- 1P_Dave
That’s a fair question, and I understand why this feels like a long time, especially for something that affects day-to-day workflows.
Changes in this area require careful testing because they affect how credentials are handled and filled, and we want to be sure we’re not introducing new issues when we resolve this one. The nightly release is part of making that process faster while still being responsible.
I agree that this isn’t ideal, and we’re actively working to get the fix into beta and production as soon as we’re confident that it’s reliable. The team is also looking into adding additional testing for each release to ensure that this doesn't happen again. We appreciate your patience and feedback.
-Dave
Your response feels perfunctory, and I think it’s clear that your team has not fully recognized the seriousness of this issue. I’m somewhat angry about your reply and disappointed in your team’s incident response capability. When a critical bug occurs, such as a P0-level bug, there should be at least a month allocated for fixing and testing to ensure that no new bugs are introduced. Don’t you have a rollback mechanism in place?
