Skip to main content
November 16, 2021
Question

iPassword 8 - error signing in when using proxy

  • November 16, 2021
  • 48 replies
  • 1691 views

I have a required local proxy security software (including SSL) on some of my systems for work, I've found there seems to be a problem with version 8. I can't sign in, it just gives a sign-in error, but if I look in the logs I'm getting some kind of HTTP error. With an identical system version 7, even the betas, work perfectly.

I can't exclude applications from it but I can exclude URLs if necessary.

These are the relevent log entries - If I try multiple times they just repeat each attempt.

WARN 2021-11-16T09:32:02.737 tokio-runtime-worker(ThreadId(5)) [1P:op-db-queue\src\operations.rs:1195] operation transaction #tx#7(set_object_bytes) took more than 100 ms (128 ms)
INFO 2021-11-16T09:32:07.473 tokio-runtime-worker(ThreadId(8)) [1P:foundation\op-windows\src\windows\network\proxy.rs:127] network proxies discovered: 1
INFO 2021-11-16T09:32:07.923 tokio-runtime-worker(ThreadId(8)) [1P:foundation\op-windows\src\windows\network\proxy.rs:220] proxy connected successfully
INFO 2021-11-16T09:32:07.923 tokio-runtime-worker(ThreadId(3)) [1P:foundation\op-proxy\src\lib.rs:150] selected HTTP proxy to use
ERROR 2021-11-16T09:32:08.118 tokio-runtime-worker(ThreadId(5)) [1P:op-app\src\app\backend\signin.rs:304] error signing in from data layer: UnableToCreateClient(HttpError(IoError(IoError(error sending request))))
ERROR 2021-11-16T09:32:08.118 tokio-runtime-worker(ThreadId(5)) [1P:C:\builds\dev\core\core\op-signin\src\lib.rs:421] error signing in from data layer: other error
ERROR 2021-11-16T09:32:08.118 tokio-runtime-worker(ThreadId(5)) [1P:C:\builds\dev\core\core\op-ui\src\signin\handlers.rs:363] Error signing in: other error


1Password Version: 8.04 (from logs)
Extension Version: 2.1.4
OS Version: Windows 10 x64

48 replies

January 12, 2022

Glad I stumbled upon this thread. Having the exact same issue, and updating to the Beta release seems to have solved the issue!

Jack_P_1P
1Password Employee
January 12, 2022

Glad to hear switching to the beta sorted it out for you @cbini87! :smile:

January 12, 2022

I attempted to run 1Password 8 on an unsupported version of Windows (W7 64 bits). 1Password 8 requires a 64-bit version of Windows 10.
How embarrassing! Sorry for your time and thank you very much for your kind explanation @1P_Gem.

1P_PeterG
Community Manager
January 12, 2022

Hi @VCarmona, thank you for letting us know - and for sharing that @1P_Gem was able to clear up what was going on there. 👍

March 13, 2022

him just wondered if this was generally available now in the windows version?

1P_PeterG
Community Manager
March 15, 2022

Hi @rorton 👋. We've implemented a few rounds of fixes related to this.

WIth release 8.5, on Feb 7, our developers fixed this issue for the majority of folks who had been encountering it (and as is typical of our approach, the fix was present in Beta versions before this date).

https://releases.1password.com/windows/8.5/

And this is likely to work for you as well!

There is still a smaller number of customers who may encounter issues with their custom network setups (which may include a proxy). We are working one-on-one with with people when this issue comes up, so that we can understand the more specific circumstances that lead to this, and provide solutions for this in future updates.

I'd suggest giving 1Password 8 a try - and if there's anything you need help, we'll be here and happy to help. I hope this is helpful!

March 15, 2022

thank you :) I have since installed, and its working well now in Windows in v8 :)

1P_PeterG
Community Manager
March 15, 2022

Hey, excellent @rorton! Great to know that things are working well for you, and this is another valuable data point for us as well about how the fixes are doing. Thank you for letting us know!

March 21, 2022

Hello,
Testing also this with release 8.6, I'm still not able to connect using our corporate proxy that need authentification:
INFO 2022-03-21T09:25:17.443 tokio-runtime-worker(ThreadId(6)) [status:op-app\src\app\backend\updater.rs:204] No Production updates found for 80600076
INFO 2022-03-21T09:25:59.903 tokio-runtime-worker(ThreadId(20)) [1P:foundation\op-windows\src\windows\network\proxy.rs:127] network proxies discovered: 1
INFO 2022-03-21T09:26:00.130 tokio-runtime-worker(ThreadId(20)) [1P:foundation\op-windows\src\windows\network\proxy.rs:220] proxy connected successfully
INFO 2022-03-21T09:26:00.130 tokio-runtime-worker(ThreadId(13)) [1P:foundation\op-proxy\src\lib.rs:150] selected HTTP proxy to use
ERROR 2022-03-21T09:26:00.183 tokio-runtime-worker(ThreadId(6)) [1P:op-app\src\app\backend\signin.rs:320] error signing in from data layer: UnableToCreateClient(HttpError(/rustc/c8dfcfe046a7680554bf4eb612bad840e7631c4b\library\core\src\result.rs:1897, IoError(IoError(connect error))))
ERROR 2022-03-21T09:26:00.184 tokio-runtime-worker(ThreadId(6)) [1P:C:\builds\dev\core\core\op-signin\src\lib.rs:435] error signing in from data layer: other error
ERROR 2022-03-21T09:26:00.184 tokio-runtime-worker(ThreadId(6)) [1P:C:\builds\dev\core\core\ui\op-signin-ui\src\handlers.rs:587] Error signing in: other error

It seems that the client is able to check if a higher version is available but not to connect to the account.
As stated by others above, it was working correctly in release 7.9 giving all the configuration in the proxy settings tab.

1P_PeterG
Community Manager
March 23, 2022

Hi @Olsnonyme, sorry to learn you've encountered this. You're correct that these logs seem to point to a proxy issue too.

Could you send us a brief email at support+windows@1Password.com? Over there, we can discuss the specifics of your network setup, which will allow me to loop in our development team as well to make sure we fully understand the issue that's arising in the context of your proxy configuration and what we can do to help. Be sure to include a link to this discussion so we know it's you and can take things the next step. 👍

Thanks - I'll keep an eye out for your message!