Google Chrome macOS sync: connection failed (-102)
Reported by
david.st...@gmail.com,
Dec 19
|
|||||||
Issue descriptionChrome Version : 71.0.3578.98 (Official Build) (64-bit) OS Version: OS X 10.14 I am getting errors with Google Chrome's sync feature. Here is how far I went: - Uninstall Chrome (delete "/Applications/Google Chrome.app" as well as "~/Library/Application Support/Google") - Reinstall latest version of Chrome (I also tried Canary) - Immediately try to setup sync (see GIF) I keep getting this error -102. I've tried many times, and actually with three different Google accounts (two personal accounts, and my professional account on G Suite), they all get the same error. I even tried to "Reset Sync" here: https://chrome.google.com/sync, and it still doesn't work. Now I lost all my synced data and still not working... I also tried setting chrome://flags/#account-consistency to both "Disabled" and "Enabled Dice (fix auth errors)", and none fixed my problem... What is the expected result? Google Chrome sync should be connected to my account, and bookmarks, extensions, etc should start syncing. What happens instead of that? Usually I get an error -102. With "Enabled Dice (fix auth errors)" I get no error but sync stays off. Please provide any additional information below. Attach a screenshot if possible. I attached a GIF of what I'm doing. I usually use two different Chrome profiles (personal and professional). The personal one was synced to my personal email address and working, while the professional one recently changed from "sync failed" to "sync paused". I always assumed sync didn't work on this one because the feature was not enabled in G Suite. I have yet to try on a different computer. Hope I can get some help! David
,
Dec 19
,
Dec 20
I tried on another computer, and I had no problems. I noticed though, that Chrome's welcome screen was different. I attached screenshots for both. Can something be wrong with my OS?
,
Dec 20
``` sudo rm -rf /Library/Caches/com.google.* /Library/Google/ /Library/Application\ Support/Google/ rm -rf ~/Library/Caches/com.google.Chrome ~/Library/Caches/Google/Chrome ~/Library/Google ~/Library/Preferences/com.google.* ~/Library/Saved\ Application\ State/com.google.Chrome.* ~/Library/WebKit/com.google.Chrome ~/Library/Application\ Support/Google/Chrome /Applications/Google\ Chrome.app ``` Now I get the welcome screen seen on chrome-sync-works.png above, but still get error -102...
,
Jan 1
Tried testing the issue on reported chrome version #71.0.3578.98 using Mac OS 10.14 by following below steps. Steps: ===== 1.Uninstalled the chrome (deleted from "Applications" and "Library" as well). 2.Reinstalled chrome. 3.Clicked on three dot menu. 4.Clicked "Turn on Sync" button. 5.Signed into account to sync and observed that the Chrome sync is successfully done. Note: Tried with G suite account as well and observed the same behaviour as mentioned above. Attached screencast for reference. @reporter: Could you please review attached screencast and let us know if anything is being missed from our end. Thanks.!
,
Jan 4
Thanks for your reply! As I mentioned in one of the comments above, I tried again with the same account on another laptop, and wasn't able to reproduce the issue. Seeing how my issue can be reproduced with multiple accounts, but not on other machines, I guess the problem is coming from my laptop. Would you please have any advice to help me debug the situation further, and eventually find out what's wrong with my computer, that prevents Chrome to sign me in the sync service? For starters, what is the cause of an error -102? I also tried to enable logging, and I could attach the chrome_debug.log file here if that is of any help, and if you can confirm it does not include any personal detail. Thanks in advance for your help!
,
Jan 4
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 7
I think this is a sign-in problem not a sync problem. Assigning to sign-in team for proper triage.
,
Yesterday
(38 hours ago)
--Chrome Identity automated triaging-- This bug is Unconfirmed and has gone two weeks without any activity, so it is being closed as WontFix. Please re-open if this is still a valid and reproducible bug or feature request and mark it as Available. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Yesterday
(33 hours ago)
Nothing has changed from my perspective... I'd be happy to dig further and provide more info about my setup if someone could help me understand 1. what "error -102" means, 2. where I can find logs telling me what's happening under the hood...
,
Today
(17 hours ago)
This looks indeed like a bug and there is a bunch of information in this bug. Re-opening it. -102 connection error corresponds to a connection attempt that was refused (per https://cs.chromium.org/chromium/src/net/base/net_error_list.h?rcl=895888689c9d9e506ce307089bd38af477044f80&l=132 ) I expect you get this error when Chrome attempts to exchange an authorization code (that is obtained after the sign-in flow) for an refresh token. Chrome uses the following URL to do this exchange https://www.googleapis.com/oauth2/v4/token. Could you please check whether this URL is accessible from Chrome on this machine?
,
Today
(6 hours ago)
Oh my god thank you so much, this is all I needed to solve my problem! I feel like such an idiot now... I had an entry in my /etc/hosts file that prevented www.googleapis.com to work. I don't know how long it's been there, but it might have been months before the problem showed up... Anyway, turns out, as expected, the issue was on my side, and I just needed a little help to troubleshoot. Thank you very much for all your help, and sorry for being a distraction... 🙇♂️ |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by lgrey@chromium.org
, Dec 19