Closed
Bug 444480
Opened 17 years ago
Closed 17 years ago
Weave Login verification failed Error code: 502 - Cannot sign in
Categories
(Cloud Services :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: chris.heinbokel, Unassigned)
References
(
URL
)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
After Weave seemed to successfully sync on one machine I own, I moved to another to begin working on it. When I opened Firefox, Weave prompted me for a sign-in, and upon doing so, attempted to connect to https://services.mozilla.org/user/cheinbokel/, but failed. This led to a 502 error in the activity log, as well as Exception: checkStatus failed, and is preventing my signing in to the service.
Reproducible: Sometimes
Steps to Reproduce:
1. Attempt to sign into Weave using correct user credentials.
Actual Results:
Weave attempts to sign in, then fails, prompting the sign-in screen.
Expected Results:
Weave successfully signs in and syncs with the server.
Weave Verbose log detailing the error:
2008-07-09 21:30:51 Chrome.Login TRACE Sync login window opened
2008-07-09 21:30:52 Chrome.Window INFO Logging in...
2008-07-09 21:30:52 Chrome.Window INFO User string: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
2008-07-09 21:30:52 Chrome.Window INFO Weave version: 0.2.2
2008-07-09 21:30:52 Service.Main DEBUG Logging in user cheinbokel
2008-07-09 21:30:52 Service.Main INFO Using server URL: https://services.mozilla.com/user/cheinbokel/
2008-07-09 21:30:52 Service.DAV DEBUG checkLogin called for user cheinbokel
2008-07-09 21:30:52 Service.DAV DEBUG GET request for root folder
2008-07-09 21:30:52 Chrome.Login TRACE Sync login window closed
2008-07-09 21:31:33 Service.DAV WARN _makeRequest: got status 502
2008-07-09 21:31:33 Service.DAV DEBUG checkLogin got response status 502
2008-07-09 21:31:33 Service.Util ERROR Login verification failed Error code: 502
2008-07-09 21:31:33 Chrome.Login TRACE Sync login window opened
2008-07-09 21:31:36 Chrome.Login TRACE Sync login window closed
2008-07-09 21:31:36 Async.Generator ERROR Exception: checkStatus failed
2008-07-09 21:31:36 Async.Generator DEBUG Stack trace:
No traceback available.
This exception was raised by an asynchronous coroutine.
Initial async stack trace:
unknown (async) :: WeaveNotifyWrapper-49 (last self.cb generated at module:wrap.js:91 :: WeaveNotifyWrapper)
module:wrap.js:168 :: WeaveLocalLockWrapper
module:async.js:232 :: AsyncGen_run
module:async.js:341 :: Async_run
module:async.js:361 :: Async_sugar
module:service.js:592 :: WeaveSvc_login
chrome://weave/content/login.js:92 :: Login_doOK
chrome://global/content/bindings/dialog.xml:357 :: anonymous
chrome://global/content/bindings/dialog.xml:358 :: _fireButtonEvent
chrome://global/content/bindings/dialog.xml:332 :: _doButtonCommand
chrome://global/content/bindings/dialog.xml:321 :: _handleButtonCommand
Comment 1•17 years ago
|
||
code 502 is bad gateway. This may have been a temporary error.
Updated•17 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•16 years ago
|
Component: Weave → General
Product: Mozilla Labs → Weave
Target Milestone: -- → ---
Updated•16 years ago
|
Component: Weave → General
Product: Mozilla Labs → Weave
Target Milestone: -- → ---
Updated•16 years ago
|
QA Contact: weave → general
You need to log in
before you can comment on or make changes to this bug.
Description
•