ispCP - Board - Support
[SOLVED] Admin Login not working - Printable Version

+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: System Setup & Installation (/forum-32.html)
+--- Thread: [SOLVED] Admin Login not working (/thread-7375.html)



[SOLVED] Admin Login not working - d4f - 08-03-2009 05:19 PM

Hi,

I've just completed the x'th installation (but first installation on 1.0.0 stable) of Ispcp.
After following the installation instructions for the latest stable version for Debian Lenny to the note, I could not login to the admin panel.
Strangely when looking into the database I found out that the admin username was not (as specified during install) "admin" but rather a part of the password...
I tried to login with that new username and the specified password - didnt work.
So I updated through command-line the username to "admin" - still didnt work.
Afterwards I tried multiple times to resend the password. Works fine, I'm receiving the confirmation-email and the new admin token.
Login with the new details? Nada... doesnt work...

When taking a look at the database I see a strange thing:
the password seems to have been resettet to md5 instead of that fancy new encryption?

First password:
$1$G/T1Hy2M$6w5mS9LZzMootcMoj1Uym/ (some random characters replaced)
Current "token"-password:
cf9b57220cb6f4e45a5759c3b7622f2d


Now the big question - why? (doesnt login work)



PS: who enforced the 30sec cooldown between logins? It's driving me crazy (havent found the corresponding database setting yet Big Grin )


RE: Admin Login not working - joximu - 08-03-2009 05:27 PM

md5 is ok - at least it also should work...

you can use pma to reset the admin user...

ispcp-lib.php:Config::set('BRUTEFORCE_BLOCK_TIME', 30);

/J


RE: Admin Login not working - d4f - 08-03-2009 05:45 PM

Unfortunately I couldn't get into PMA as the login doesn't work Sad
I'm currently doing everything per command-line.

I fixed the problem by reinstalling everything (the Installer seems to have missed 1/2 the database without the frontend complaining about it...)
The second time he got it right and _finally_ everything works Smile

Many thanks anyway for the very quick reply Smile

Btw: isn't block time the 30min interval between 3 unsucessful logins?
I've overriden that with "update login set login_count = 0, captcha_count=0;"