Closed
Bug 442289
Opened 16 years ago
Closed 16 years ago
s.m.c returning HTTP code 502 for some new registrations
Categories
(Cloud Services :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
0.2
People
(Reporter: anant, Assigned: anant)
Details
Some users have reported 502 (Bad Gateway) status codes while trying to create a new account - this should not happen. Opening a bug, so we can investigate.
Comment 1•16 years ago
|
||
Happens to me too (userid: billimek, email: jeff@billimek.com) "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0" 2008-06-27 13:26:02 Chrome.Wizard INFO Initializing setup wizard 2008-06-27 13:26:16 Chrome.Wizard INFO Wizard: Showing welcome page 2008-06-27 13:26:19 Chrome.Wizard INFO Wizard: Showing username/password creation page 2008-06-27 13:26:52 Chrome.Wizard INFO Wizard: Showing passphrase/email page 2008-06-27 13:27:00 Chrome.Wizard INFO Wizard: Showing captcha/license agreement page 2008-06-27 13:27:29 Chrome.Wizard INFO Error: received status 502. Account not created. 2008-06-27 13:27:34 Chrome.Wizard INFO Incorrect Captcha response. Account not created. 2008-06-27 13:27:51 Chrome.Wizard INFO Error: received status 502. Account not created. 2008-06-27 13:28:03 Chrome.Wizard INFO Incorrect Captcha response. Account not created. 2008-06-27 13:28:23 Chrome.Wizard INFO Error: received status 502. Account not created. 2008-06-27 13:28:29 Chrome.Wizard INFO Incorrect Captcha response. Account not created. 2008-06-27 13:28:45 Chrome.Wizard INFO Error: received status 502. Account not created. 2008-06-27 13:30:21 Chrome.Wizard INFO Incorrect Captcha response. Account not created. 2008-06-27 13:30:39 Chrome.Wizard INFO Error: received status 502. Account not created. (all times EST)
Comment 2•16 years ago
|
||
I've been periodically trying over and over and it eventually worked (not sure if it was my persistence or something got changed/fixed on the server side).
Assignee | ||
Comment 3•16 years ago
|
||
We made a change on the server-side that hopefully fixes the issue, but we're going to wait a little before closing the bug just to see if someone else hits the issue now.
Comment 4•16 years ago
|
||
I think it's safe to close this now. Reopen if it comes up again!
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•15 years ago
|
Component: Weave → General
Product: Mozilla Labs → Weave
Updated•15 years ago
|
QA Contact: weave → general
You need to log in
before you can comment on or make changes to this bug.
Description
•