Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
iPassword 8 - error signing in when using proxy
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
1P_PeterGCommunity Manager
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!
- 1P_PeterG
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!
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.
Jack_P_1P1Password Team
Glad to hear switching to the beta sorted it out for you @cbini87! :smile:
1P_GemModerator
Hi @VCarmona! Just to let you know, we've received your email and will continue the conversation over there :) ref: IAF-22913-952
