iPassword 8 - error signing in when using proxy

Hi @VCarmona,

Can you confirm that you're still having this issue with the latest nightly/beta builds, which is at 8.5.0-87?

If yes, can you email us your diagnostics report? Here's how:

1. Open 1Password and then its settings
2. Select the Advanced tab and select Send Diagnostics.

Attach the diagnostics to an email message addressed to support+windows@1password.com.

In your email, please also include:

• A link to this thread: https://1password.community/discussion/125015/ipassword-8-error-signing-in-when-using-proxy
• Your forum username: VCarmona

Please do not post your diagnostic report to the forum.

You'll get an email from our automatic reply from BitBot. It'll include a support ID, please include it in your next reply here, so we can look for the email.

Glad to hear that did it for you jkane001! :smile:

Looks like it works! Thanks!

Hi jkane001:

The improved SSL/TLS interception support is now in the beta channel as well. If you're looking to download the beta directly, it can be obtained from this link: https://downloads.1password.com/win/1PasswordSetup-latest.BETA.exe

Let me know how that goes!

Jack

Is this still just available in the nightly build, or is it live yet?

Hi,
This error may have a different origin, but in case it helps, I tried it in my work environment, and it didn't work for me, just like the production version.
Version 80500042 NIGHTLY running on Windows 7 x64 Enterprise SP1.
I have attached the three log files as a screenshot and the last log file as text.

1Password_r00002.log:
INFO 2021-12-09T08:14:14.315 ThreadId(7) [client:typescript] Client starting.
INFO 2021-12-09T08:14:14.360 tokio-runtime-worker(ThreadId(2)) [1P:native-messaging\op-native-core-integration\src\lib.rs:238] Mute native core integration is waiting for Shared Lock State to be enabled
INFO 2021-12-09T08:14:14.360 ThreadId(7) [1P:op-localization\src\lib.rs:185] system locale detected as 'es-ES'
INFO 2021-12-09T08:14:14.361 ThreadId(7) [1P:op-localization\src\lib.rs:211] selected translations for ES_ES based on detected locale es-ES
INFO 2021-12-09T08:14:14.361 ThreadId(7) [status:op-app\src\app.rs:306] App::new(1Password for Windows/80500042 (ES_ES), C:\Users\29159392s\AppData\Local\1Password\1password.sqlite)
INFO 2021-12-09T08:14:14.362 ThreadId(7) [1P:op-db\src\db.rs:94] Starting DB at version: 23
ERROR 2021-12-09T08:14:46.751 tokio-runtime-worker(ThreadId(5)) [1P:op-app\src\app\backend\updater.rs:177] AppUpdates(Http(IoError(IoError(error sending request))))

Best regards.

Ah! Great point, Mike. Thank you for clarifying. ❤️

++dave;

Hi folks,

Your security setup may actually block the updates from showing up. Please download the latest nightly from here: https://downloads.1password.com/win/1PasswordSetup-latest.NIGHTLY.exe

Hello everyone, 👋

I wanted to give an update on the changes to make things work properly with TLS/SSL interception setups in enterprise networks. The code that enables this was just merged a few minutes ago and we published a new nightly release so y'all could give it a try and see if it works in your setup.

If you'd like to give this a try yourself please go to Settings > Advanced and change the release channel to NIGHTLY and update. You should see build #80500038 or higher in the Settings > About window. Please let us know how it turns out. 🤗

For full discourse, note that this is a nightly release so in general it's not tested nearly as much as our betas. You'll be using the same version as our team is using which can be a good thing but can also mean you get bugs we haven't found yet and will need to live with them until they get fixed (likely in the next nightly or two).

Cheers! 🍻

++dave;

Thank you dteare for the detailed explanation of what's happening here. I was excited to give the version 8 client a try today at work but immediately ran into this issue. (I should have done a quick read of the known issues.) I've rolled back to the version 7 client and that will work fine until the issue is resolved. Like so many others, my workplace implements https inspection. I do understand why some organizations feel compelled to do this type of inspection but I don't love the practice. Indeed, one of the endearing qualities/features of the 1Password security architecture is that the TLS layer, while nice to have where available (uncompromised), is not technically necessary for the security of the client/server communications. It is 1Password's incorporation of SRP that really makes 1Password special in the cloud-based password manager product space.

Thanks again for the update. Hopefully, the issue will be resolved soon-ish. I'm eager to try out the new Electron-ified UI for the Windows application.

Best,
GBR