+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Development Area (/forum-1.html)
+--- Forum: General discussion (/forum-11.html)
+--- Thread: [Solved] Login Error 500! (/thread-1671.html)
[Solved] Login Error 500! - 2471 - 10-31-2007 09:01 AM
I get a 500 error when logging in, the page seems to load about halfway then errors out with:
Error 500!
/admin/index.php
Internal Server Error!
If I close the browser and reopen to the login page the control panel is wide open at the default screen.
RE: Login Error 500! - 2471 - 10-31-2007 10:00 PM
The changeset 593 fix took care of this problem.
login-functions.php
RE: Login Error 500! - BeNe - 10-31-2007 10:30 PM
Which Version do you use ?
Can´t confirm this in the latest trunk.
Greez BeNe
RE: Login Error 500! - 2471 - 11-01-2007 02:18 AM
Spoke too soon, that didn't fix the problem.
Once I get the 500 error if I wait about 1 minute and hit the refresh button I get the panels default opening page, but sometimes it works from there and sometimes it 500 error's out again.
Seems to be a session problem as I get an email saying I logged in then right after that I get an email saying session could not be found or terminated (something like that).
Happens on pma login too.
rc2
build: 2007-04-18
BeNe Wrote:Which Version do you use ?
Can´t confirm this in the latest trunk.
Greez BeNe
RE: Login Error 500! - ephigenie - 11-01-2007 02:30 AM
2471 Wrote:Spoke too soon, that didn't fix the problem.
Once I get the 500 error if I wait about 1 minute and hit the refresh button I get the panels default opening page, but sometimes it works from there and sometimes it 500 error's out again.
Seems to be a session problem as I get an email saying I logged in then right after that I get an email saying session could not be found or terminated (something like that).
Happens on pma login too.
rc2
build: 2007-04-18
Please take a look if your phptmp dir is writeable and your session.save_path points to the right folder ...
RE: Login Error 500! - 2471 - 11-01-2007 03:54 AM
That appears to be ok, directory is 755 and there are new files in there by date.
ephigenie Wrote:2471 Wrote:Spoke too soon, that didn't fix the problem.
Once I get the 500 error if I wait about 1 minute and hit the refresh button I get the panels default opening page, but sometimes it works from there and sometimes it 500 error's out again.
Seems to be a session problem as I get an email saying I logged in then right after that I get an email saying session could not be found or terminated (something like that).
Happens on pma login too.
rc2
build: 2007-04-18
Please take a look if your phptmp dir is writeable and your session.save_path points to the right folder ...
RE: Login Error 500! - scoutsniper - 11-01-2007 04:35 AM
I have same problem too before 1 month I installed and use the panel and there was no problems after 10 days whats going on :O BIG PROBLEM i can't login anywhere in my panel admin,resseler,user etc...Then i format anything because i was VERY angry.But now i will install on fresh image..Will see...
P.s Sry for the bad english.
RE: Login Error 500! - 2471 - 11-03-2007 11:46 PM
I am installing this for a friend on his new VPS, after looking through the login scripts to see how login works and not being able to find a problem ... it hit me like a ton of bricks to check the server time, sure enough it was off by about 6 hours.
Changed the server time and login seems to work now, could this become a problem for people like resellers and domain users that are in different time zones than the server itself? Developers might want to investigate this.
The actual time setting should not be a factor, its the length of time, ip address and not the actual time itself that the session routine should rely on for authentication. Buts that my opinion...
The difference between client time (cookie) and server time (mysql login table) should not be a factor, what if someones computer clock is way out of wack?
You should get away from cookie authentication anyway, you can do it without cookies and it would be more secure if done properly. Many people block cookies and this would cause problems and unnecessary tech support requests for a host.