1P7 connection issues with macOS application
I upgraded from 1P6 to 1P7 and do not have access to the internet anymore (sync not working, update fails with error). I am behind a proxy; in a browser I can use 1password.com without issues. I have set a system proxy authentication and 1password 6 did not have this issue. http / https / rsync access works with other applications. What protocol do you use for updating / syncing?
Console output:70004001 [SYNC:(Main Thread):<B5ServerNotificationMonitor: 0x608000a46810>] E webSocket:didFailWithError: | Socket for account User Account 1 - Session Id:CMOCS6DJ2VDC3JMTR53O3LHS5M did fail with error Error Domain=kCFErrorDomainCFNetwork Code=2 "(null)" UserInfo={_kCFStreamErrorDomainKey=12, _kCFStreamErrorCodeKey=8, kCFGetAddrInfoFailureKey=8}. Attempting reconnect in 8 seconds.
To me, this looks like a DNS resolution failure. Please advise.
I also generated a bug report as described (https://support.1password.com/diagnostics/) which I can send to you if necessary.
1Password Version: 7.0.4 (70004001)
Extension Version: 4.7.1 (Safari)
OS Version: macOS 10.12.6 Build 16G1408
Sync Type: 1password.com
Comments
-
@dbm14: I'm sorry for the trouble, and for the delay getting back to you. Indeed, that does sound like the server simply cannot be resolved. 1Password doesn't handle any of that, so it will be something external, either with 3rd party software or settings, the OS itself, or your network. I've had similar issues when I forgot to allow 1Password in Trip Mode, which I use to limit data usage; but another time DNS inexplicably broke in macOS for me and I had to reinstall. The latter is unlikely, and is the most Windows-like experience I've had on a Mac ever. I suspect it's something much simpler in your case. If you disable the proxy, does it work then?
0 -
@brenty Thank you very much for your answer. Today I could not reproduce the error and 1P7 behaves as expected. It seems to have been some issue with my companies DNS server (they run their own). Outside of the company network I did not encounter this problem (but of course I rely on different DNS servers there). Maybe the 1P7 update address was not yet cached on the server and a high latency at the same time might have caused a timeout for the sync / update request. For now, everything works fine and the ticket can be closed. Have a nice day!
0 -
Ah, gotcha. That makes sense. That can be maddening, but I'm glad that it's working for you normally now. And we're here if you need us. I hope you enjoy your data as well! :chuffed:
0
