Closed
Bug 1042039
Opened 11 years ago
Closed 11 years ago
[stage] http://beta.123done.org/ is stuck on loading
Categories
(Cloud Services :: Server: Identity, defect)
Cloud Services
Server: Identity
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: AndreiH, Assigned: relud)
References
()
Details
(Whiteboard: [fromAutomation])
Attachments
(1 file)
62.08 KB,
image/png
|
Details |
#STR:
1. Go to http://beta.123done.org/ and inspect site
#Expected results:
Persona should be available for login.
#Actual results:
Persona is stuck at loading.
No errors are seen in the console.
Reporter | ||
Updated•11 years ago
|
Whiteboard: [fromAutomation]
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Comment 1•11 years ago
|
||
Comment 2•11 years ago
|
||
Confirmed, can reproduce.
Seems to be an issue with static.login.anosrep.org, all the connections to that service aren't completing (but they aren't timing out in a period of time short enough for me to care waiting for, either).
Component: Extensions: Persona → Server: Identity
Product: bugzilla.mozilla.org → Mozilla Services
Version: Development/Staging → unspecified
Comment 3•11 years ago
|
||
https://static.login.anosrep.org/ is serving the wrong SSL certificate. (*.anosrep.org does not cover *.*.anosrep.org).
Comment 4•11 years ago
|
||
Ya, this was a mistake when DNS was moved from dynect to route53
Comment 5•11 years ago
|
||
Daniel, would you CNAME these names
static.login.anosrep.org.
verifier.login.anosrep.org.
to
w-login-anosrep-org-0721-2030746466.us-west-2.elb.amazonaws.com
instead of
w-anosrep-org-0721-656503154.us-west-2.elb.amazonaws.com
Assignee: nobody → dthornton
Assignee | ||
Comment 6•11 years ago
|
||
Sorry, this was a misunderstanding when I updated the staging stack. It's been fixed.
Assignee | ||
Comment 7•11 years ago
|
||
And beta.123done.org looks working to me now.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 8•11 years ago
|
||
(In reply to Daniel Thornton [:relud] from comment #7)
> And beta.123done.org looks working to me now.
Thanks, verified FIXED
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•