This is driving me crazy. I'm hoping someone has seen this problem and may have a clue how to fix it. Last night, I was doing some work on my threads database and I was logging into my DB using PhPMyAdmin. It was working fine.. Later, I went back into PhPMyAdmin and tried to log in, but now it just keeps giving me the login screen again and will not take me to my DB. I tried clearing cookies and temp internet files, etc., but still no luck. Has anyone else run into this problem and do you have any idea what to do to fix it? Like I said, it had been working earlier and I did not change anything with respect to my security settings, etc.<br /><br />Thanks in advance for any help,<br />Basil

You can change the authentication method in the config-inc.php file of phpmyadmin - turn it to "config" while you are using it - sounds like it's currently using cookie authentication.

I did the same thing. I deleted all the cookies and it still was acting up. I really got upset and just turned off my computer and walked away...<br /><br />About 2 hours later I decided to go back and it worked fine.

I had something like that happen under phpmyadmin 2.5.5 and it went away when I updated to 2.5.6 so you may want to give that a shot as something may have changed in the last updates to internet explorer or something.

Set it to http and you'll need to use the username and password for the database. FYI, be smart put it in a dir with a different name. Don't use phpmyadmin, or any variation. Give the dir a name only you would readily know.

I call mine wuzzywuzzywigglywoo no one will ever guess that

[]scroungr said:<br />I call mine wuzzywuzzywigglywoo no one will ever guess that [/]<br /><br />Yep, noone will ever guess that. Of coarse, now they can just google for it. <img src="http://www.ubbdev.com/forum/images/graemlins/smirk.gif" alt="" /> <img src="http://www.ubbdev.com/forum/images/graemlins/devil.gif" alt="" />

[]scroungr said:<br />I call mine wuzzywuzzywigglywoo no one will ever guess that [/]<br /><br />LMAO!

Hi.<br />Verify date and time on server. My server was dated feb 16, while current date was mar 22... and this generate expired cookies on client.