Can't log into Manager directly after installing

Hi,

I’ve just installed Modx into the directory public_html/contents on a site that already has quite a bit of data on it. The install runs cleanly, but once it’s finished I am unable to log into the manager. I keep getting an "Incorrect user name or password entered" error.

I have double-checked and even reset the admin password through MySql, re-uploaded the files and reinstalled several times, and even even deleted the Modx subdirectory and installed version 0.9.6.2, but I keep getting the same bug.

Suggestions?

Here are some things to check:

Do you have an index.htm or index.html file that could be taking precedence over the MODx index.php file?

Does the login screen look like a MODx login screen (green bar at the top, MODx copyright notice)?

Is there an .htaccess file in the MODx root directory (/contents)?

No index.html or index.php taking precedence. In fact, the front end loads just fine.

The login screen is most definitely from modx. It’s identical to the admin login from the other modx site I administer.

No .htaccess file in the modx root directory, just ht.access.

Try setting a new password using this method:

http://modxcms.com/forums/index.php/topic,28992.0/topicseen.html

When you’re doing that, verify the name of the main admin user (it’s case-sensitive).

Nope, that doesn’t work either. I’m still getting the same message: "Incorrect username or password entered!" followed by the directory in which the error occurred.

I appreciate your taking time to help me with this, Bob. I’ve been wracking my brains trying to figure out what might be unique about this server, but it’s just your typical shared Linux box running phpSuExec.

Interestingly, I can get into the manager using the link from the "Forgot Your Password" email. Once there, I can access everything and even create new users, but I’m not able to log in with any of the newly created user accounts either.

Ok, this is utter weirdness:

I added a few echo statements to login.processor.php to try to track the problem, then removed said echo statements... and the login option is now working perfectly. I haven’t the faintest notion why.

But thanks again for your assistance, Bob. I very much appreciate the time you took to help.

That’s about as weird as it gets.

It kind of smells like a session problem or something weird with left-over cookies from a previous install. I’m glad it’s working because I was out of ideas.

You don’t happen to be using eAccelerator or any other opcode caching systems on this configuration do you?

Nope, no opcode caching systems.

I think Bob’s right and it was a leftover cookie problem. Either way, I’m just happy that it’s gone