Skip to main content
November 27, 2025
Solved

Beta version not working on HTTP sites

  • November 27, 2025
  • 14 replies
  • 948 views

There's another issue with this build: the extension stopped working on http sites at all.

The autofill buttons do nothing either.

Best answer by 1P_Dave

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 

14 replies

1P_Dave
1Password Employee
January 7, 2026

Hello 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

Spaldo
January 7, 2026

Hi@1P_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
1Password Employee
January 8, 2026

@Spaldo 

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

January 7, 2026

Confirmed Nightly extension on Edge and MacOS is filling HTTP sites now.

1P_Dave
1Password Employee
January 8, 2026

Thank you for confirming that the nightly version resolves the issue for you! 

-Dave

January 8, 2026

I can confirm autofill is working for Windows 11 + Chrome with the 1password Nightly dekstop app (81200006) and 1password Nightly chrome extension (8.12.0.3)

1P_Dave
1Password Employee
January 8, 2026

Thank you for the confirmation! 

-Dave

1P_Dave
1P_DaveAnswer
1Password Employee
January 21, 2026

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 

January 21, 2026

Hi@1P_Dave 

Thanks for the feedback. When can we expect the fix to be released on the iOS App Store ?

 

EDIT : sorry, update already available in iOS apps tiré and working, thanks 

1P_Dave
1Password Employee
January 21, 2026

@tchirou 

The fix is already available in the latest version of 1Password for iOS: How to keep 1Password up to date

Are you still seeing the issue when using the latest version of 1Password for iOS (8.12.0)? 

-Dave