Closed Bug 654143 Opened 14 years ago Closed 14 years ago

Can't login to Admin panel

Categories

(Websites Graveyard :: markup.mozilla.org, defect, P1)

x86
macOS
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: lmesa, Assigned: adam)

References

()

Details

Unable to login to https://markup.allizom.org/accounts/login/ Even with the password on the wiki, you get the login prompt and then it fails.
Any updates? This is blocking testing.
I just encountered this locally as well, but I was getting a "no site found" error. To fix it, I added a row to the django_site table with the appropriate values for my local host.
Actually I think what you reported was different from what I was seeing locally. I just checked this again and was able to login just fine.
Ok, thats strange. We can't login at all. Just getting a blank white page. Would a screencast help?
(In reply to comment #4) > Ok, thats strange. We can't login at all. Just getting a blank white page. > Would a screencast help? The blank white page is caused by the old sessionID triggering an error state. Which returns the following within html source <!-- shouldn't really get here... --> You can resolve this issue by clearing your cookies for the site. This will show you the admin page, but the credentials still don't work.
The admin password changed. Ping laura for the correct new password.
The password ending in ro is the correct password. However, something is definitely odd. I'm able to login just fine, but our other sec guy can't login at all.
Maybe only one person can login at a time? I still can't login.
Update--I can login with Chrome, but not Firefox. Maybe Firefox is having trouble with the cache and cookies?
Laura, I just confirmed this is working on FF4 :) I can give you hand if you need :)
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
mbrandt: i am also having a problem logging on. it keeps responding to me like the password is bad.
:rforbes - this might be a silly question, but are you using the correct password?
:mbrandt: heh, i would like to think so :) i tried it about a bajillion times, so i can't imagine i fat fingered it that many times.
Sorry, always gotta ask the obvious ;) its always what bites me ... I don't know what to say, the authentication details in the wiki are working for me. https://intranet.mozilla.org/MarkUP_Campaign#Admin.2FModeration
TBG--Can you comment if only one person can be logged in at a time? Still seeing issues.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Pretty sure you can have more than one person logged in at a time, even if both are using the same account. I was able to login to the admin in safari and firefox at the same time using the same account on my localhost.
:mbrandt: do you have time for a phone call to talk about this?
Depends on: 654575
No longer depends on: 654575
Depends on: 654575
I can now login--Raymond, does it work for you?
Chatting with rforbes on irc. Seems to be working for him now. :) Yay! Bumping this to FIXED. Please reopen if necessary.
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
TBG-- In our meeting Tuesday you mentioned you would provide us with the login steps to make sure admins can always login. Please add them here.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
1.) Clear Cache and Cookies 2.) Navigate to http://markup.allizom.org/ 3.) Authenticate with basic credentials (if you haven't done so already) 4.) Navigate to http://markup.allizom.org/accounts/login 5.) Login with with admin credentials 6.) Navigate to http://markup.allizom.org/#/moderate 7.) Moderate 8.) Navigate to http://markup.allizom.org/accounts/logout
Thanks Chris-- Even with the directions I get a 500 error. Good news is the 500 error template works--bad news is that we're getting one. Matt, can you give more details?
Hi Chris, Here's what we're seeing. Let me know what additional information I can provide if it would be useful. Unfortunately we're not receiving tracebacks so I'm unable to provide that info at the time. http://screencast.com/t/XJfDuh2ddf Env: Firefox 4.0.1, OSX Steps to reproduce: 1. Clear your browsers cache 2. Go to /accounts/login/ 3. Login Expected: After logging in, the page re-directs to /#/moderate/ Actual: A 500 ISE is returned: [10:02:28.131] "[Thu May 05 2011 10:02:28 GMT-0700 (PDT)]" "runRoute" "get #/moderate" [10:02:28.170] GET https://statse.webtrendslive.com/dcs9dibiiuz5bdj1562ysppji_6g1s/dcs.gif?&dcsdat=1304614948109&dcssip=markup.allizom.org&dcsuri=/en-US/&dcsref=https://markup.allizom.org/accounts/login/&WT.tz=-7&WT.bh=10&WT.ul=en-US&WT.cd=24&WT.sr=1920x1200&WT.jo=Yes&WT.ti=Mozilla%20Firefox%20Mark%20Up&WT.js=Yes&WT.jv=1.8&WT.ct=unknown&WT.bs=891x679&WT.fv=10.1&WT.slv=Not%20enabled&WT.tv=9.3.0&WT.dl=0&WT.ssl=1&WT.es=markup.allizom.org/en-US/&WT.vt_f_a=2&WT.vt_f=2 [HTTP/1.1 200 OK 166ms] [10:02:28.216] GET https://markup.allizom.org/en-US/moderate_sammy.html [HTTP/1.1 200 OK 76ms] [10:02:28.665] GET https://markup.allizom.org/media/assets/images/playback.gif [HTTP/1.1 200 OK 10ms] [10:02:28.671] GET https://markup.allizom.org/media/assets/js/vendor/country_codes.json [HTTP/1.1 200 OK 11ms] [10:02:28.706] GET https://markup.allizom.org/requests/marks_by_flagged?offset=0&max=20 [HTTP/1.1 500 INTERNAL SERVER ERROR 23ms] [10:02:28.773] GET https://markup.allizom.org/media/assets/images/light_overlay.png [HTTP/1.1 200 OK 20ms] [10:02:28.779] GET https://markup.allizom.org/media/assets/images/loader_light.gif [HTTP/1.1 200 OK 20ms]
The 500 error is because there's no flagged marks in there right now. Can we close this bug and open a new bug specific to that problem? The error message should be fixed for the moderate page like we did on the regular visualization.
Comment 24 spun off as bug 655125. The original behavior in comment 0 has been resolved.
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
Closing out this bug as VERFIED. I believe the original intent has been resolved.
Status: RESOLVED → VERIFIED
Product: Websites → Websites Graveyard
You need to log in before you can comment on or make changes to this bug.