Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
Former Member
4 years agoiPassword 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_Gem
1Password Team
Hi @mxw! It's great to hear that the latest Nightly release has gotten things working for you on Mac - thanks for letting us know! š
- Former Member
As of NIGHTLY channel release 1Password for Mac 8.10.7 (81007019) this is now fixed for me.
I use automatic proxy configuration using PAC file URL within the system settings.
In the log files, I now see "selected HTTP proxy to use" rather than "skipping proxy returned by PAC since we couldn't connect to it"
- ag_mike_d
1Password Team
Hi @dh4,
Work had continued through 2022 with regard to sign in issues and the use of proxies with 1Password 8. I'm sorry to hear you're still seeing issues. We'd like to investigate further and ask if you could create a diagnostics report from the device causing you troubles:
Sending Diagnostics Reports
Attach the diagnostics to an email message addressed to
support+forum@1password.com
.With your email please include:
- A link to this thread: https://1password.community/discussion/comment/667850/#Comment_667850
- Your forum username:
dh4
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks!
- Former Member
Was this ever resolved? I still have this issue with my account.
- ag_mike_d
1Password Team
Hello @amaltson,
Thanks for your message and sorry to hear of the troubles you've been experiencing when trying to sign in with 1Password 8.
I've included the instructions again here and ask if you could send a diagnostics report to us at support+forum@1password.com so we can take a look. Please do not post these details in the forums:
- Open 1Password and attempt to sign in to your 1Password account again. This should fail as it has.
- In Terminal, run
export OP_UNREDACT_LOGS=1
- Run
/Applications/1Password.app/Contents/MacOS/1Password
- Select the vertical ellipsis (
ā®
) on the sign in screen after you have attempted the sign in, to open the settings menu and generate diagnostics report.
Can you also include a link to this thread in your email, along with your forum handle so that we can "connect the dots" when we see your report in our inbox.
Thanks!
ref: dev/core/core#15728
- Former Member
Hello all,
I'm trying 1Password 8.8.0 also behind a corporate proxy and I'm getting a "We weren't able to sign in to your account. Maybe there's a typo? Check your sign-in details and try again.". However, 1Password 7 works fine. This is also an M1 MacBook Pro, so not sure if the Mac and/or ARM version is different. Thanks in advance!
- ag_mike_d
1Password Team
Hello @MichaelA, please excuse the delay in response and sorry to hear of the problems you've been experiencing with your system's proxy setting and 1Password8 on Mac.
You've reached reached the Windows forums but we have had a few cases reported and I would like to direct you to email us at support+forum@1password.com so we can get some additional details to help investigate. Please do not post these details in the forums:
1. Open 1Password and attempt to sign in to your 1Password account again. This should fail as it has.
2. In Terminal, runexport OP_UNREDACT_LOGS=1
3. Run/Applications/1Password.app/Contents/MacOS/1Password
4. Select the vertical ellipsis (ā®
) on the sign in screen after you have attempted the sign in, to open the settings menu and generate diagnostics report.Can you also include a link to this thread in your email, along with your forum handle so that we can "connect the dots" when we see your report in our inbox. Thank you!
ref: dev/core/core#15728
- Former Member
I have the same issue. 1Password 8 is not using the system's proxy settings. I am on 1Password for Mac 8.7.1. Did not have this issue with 1Password 7.
- 1P_PeterG
Community Manager
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!
- Former Member
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 errorIt 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.