Issue 430126 in chromium: Chrome Sync: "service unavailable, try again later"

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Pri-2 Via-Wizard Type-Bug OS-Windows

New issue 430126 by zombie86...@gmail.com: Chrome Sync: "service
unavailable, try again later"
https://code.google.com/p/chromium/issues/detail?id=430126

UserAgent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/38.0.2125.111 Safari/537.36

Steps to reproduce the problem:
1. Open Chrome
2. Sign in
3. Receive error "service unavailable, try again later"
4. Open Setting no signed into chrome.
5. Try to sign in again via settings option same error
Still unable to sign into Chrome can not sync

What is the expected behavior?
To be able to sign in and sync my google account

What went wrong?
Unable to sign into Chrome to Sync my google account.

Did this work before? Yes Months ago

Chrome version: 38.0.2125.111 Channel: stable
OS Version: 6.2 (Windows 8)
Flash Version: Shockwave Flash 15.0 r0

Steps taken: Uninstalled Chrome
Cleared cookies and cache
tried creating new profile under add new user

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Labels: Cr-Services-Sync Needs-Feedback

Comment #1 on issue 430126 by smok...@chromium.org: Chrome Sync: "service

unavailable, try again later"
https://code.google.com/p/chromium/issues/detail?id=430126

Unable to reproduce the issue on Windows and Chrome: 38.0.2125.111, please
review attached screenshot.

Can you create a new profile from chrome://settings and then try logging in
to browser. Update the bug with your findings.

Attachments:
430126.jpg 221 KB

[chro...@googlecode.com]

Updates:
Status: WontFix

Comment #3 on issue 430126 by z...@chromium.org: Chrome Sync: "service

unavailable, try again later"
https://code.google.com/p/chromium/issues/detail?id=430126

Sounds like it was a proxy/firewall issue? Out of curiosity, what fixed it?

Closing this out.