Closed
Bug 884174
Opened 11 years ago
Closed 11 years ago
Can't access myMakes in thimble
Categories
(Webmaker Graveyard :: Thimble, defect)
Webmaker Graveyard
Thimble
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: brett, Assigned: jon)
References
Details
Attachments
(1 file)
32.96 KB,
image/png
|
Details |
May be due to DNS propigation or what not, but I'm not able to access myMakes in thimble. See screenshot
Reporter | ||
Comment 1•11 years ago
|
||
This is making it impossible to republish thimble makes, which is point people to the wrong server
Blocks: 884173
Severity: normal → blocker
this looks like a first time login issue. if I log for the first time, 'my makes' won't work because webmaker.org doesn't have a persona session cookie set yet, and the 'my makes' data comes from webmaker.org/me?app=thimble... If I go to webmaker, which auto logs me in, and then reload thimble and hit 'my makes', it works. Can we do an iframe-load for the base webmaker.org site so that the webmaker.org-local-cookie gets set on a firs time login?
Comment 3•11 years ago
|
||
Not sure if this helps, but I'm not seeing my makes, and I've logged in and out multiple times. I just tried to publish a make I'd already tried to publish and got an error: http://imgur.com/Sy40WZ5 but I don't see this in mymakes.
Comment 4•11 years ago
|
||
Jon, this has to do with "www" appearing for webmaker.org, which is throwing off our audience params.
Assignee: pomax → jon
Assignee | ||
Comment 5•11 years ago
|
||
Alright, I need a forced redirect from www.webmaker.org to webmaker.org . :jp I did this by creating a new instance, putting the following ngxinx config on it: server { listen 80; rewrite ^(.*) https://webmaker.org$1 permanent; } Then spinning up a new ELB (www-webmakerorg-production) with our san webmaker cert on it. Quick hacks ftw!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•11 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=884174#c5 has a mess that needs a cleanup.
You need to log in
before you can comment on or make changes to this bug.
Description
•