Closed
Bug 334860
Opened 19 years ago
Closed 19 years ago
Can not login as Administrator
Categories
(Bugzilla :: Administration, task)
Tracking
()
VERIFIED
DUPLICATE
of bug 328108
People
(Reporter: Russ, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: bugzilla 2.20.1
I just install Bugzilla 2.20.1 and I have not been able to login as the administrator yet. Is there a default username and password or is there a file I can look in? Also, the manual talks about the edit parameters , Maintainer and http://you-havent-visited-editparams.cgi-yet/index.cgi. Are they links I should see when I get logged in? Lastly are the MySQL usernames and password the same as Bugzilla?
Reproducible: Always
Steps to Reproduce:
can't login
Comment 1•19 years ago
|
||
Creating a adminitrator was part of ./checksetup.pl. Did you run that? It asks for an email address and password.
Comment 2•19 years ago
|
||
do you mean that you're redirected to
http://you-havent-visited-editparams.cgi-yet/index.cgi ?
perhaps it's Bug 328108 ?
Comment 3•19 years ago
|
||
(In reply to comment #2)
> do you mean that you're redirected to
> http://you-havent-visited-editparams.cgi-yet/index.cgi ?
> perhaps it's Bug 328108 ?
>
That's how I understand this bug too. This problem has been fixed already.
A workaround till 2.20.2 is released is to use the "Log In" link in the footer to log in the first time, then go to editparams.cgi and change this http://you-havent-visited-editparams.cgi-yet/ URL in the urlbase parameter to your real intallation. Then the login form on index.cgi will work correctly.
*** This bug has been marked as a duplicate of 328108 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Someone else ran the checksetup.pl and I don't know what happened from there. How can I start over? Also, if I use the "Log In" link in the footer
to log in the first time, how do I get to the editparams.cgi?
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Comment 5•19 years ago
|
||
(In reply to comment #4)
> Someone else ran the checksetup.pl and I don't know what happened from there.
> How can I start over? Also, if I use the "Log In" link in the footer
> to log in the first time, how do I get to the editparams.cgi?
>
That's not the right place for support questions. Anyway, if the problem you have is as described in comment 2, then this bug is a dupe of bug 328108. You access editparams.cgi using the "Parameters" link in the footer of the page, after being logged in as described in comment 3.
The problem is I can not login to do any of these steps. How do I create New Admin account if i can't login?
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → WONTFIX
Updated•19 years ago
|
Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---
Comment 7•19 years ago
|
||
This is still a duplicate.
Go to editparams.cgi and log in. If you can't log in from that page, then there's some other problem that would require support assistance. For support resources, you can see:
http://www.bugzilla.org/support/
*** This bug has been marked as a duplicate of 328108 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → DUPLICATE
Even when you change the maintainer and urlbase and submit changes the changes are not saved. then what?
(In reply to comment #8)
Could someone please respond? After using the Login on the footer and change the maintainer and urlbase and submit changes the changes, the changes are not saved.
Status: RESOLVED → VERIFIED
Comment 10•19 years ago
|
||
(In reply to comment #8)
> Even when you change the maintainer and urlbase and submit changes the changes
> are not saved. then what?
That would be a different bug. We have it filed somewhere--it happens to Windows users. It's a permissions problem.
*** This bug has been marked as a duplicate of 328108 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → DUPLICATE
Comment 11•19 years ago
|
||
Could we stop reopening this bug? It's a dupe. Period. Reread comment 7 if you need support.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•