Can’t Login AFTER its been running fine

Yeah, I just found the same problem (can’t log in) and came up with the same solution as elfi, it was the COOKIEPATH that was being set wrong. It has something to do with me having the blog in a different directory than the wordpress installation.

Well, I have one question for you all: What browser are you using?
I almost always use Safari (on my Mac), and occassionally I find that I am not able to login, or that I get that redirected page that links to nowhere. I’ve found that if I use Mozilla when this happens, I can login in just like usual with no problems.
Has anyone else experienced something like this?

I very nearly always use Mozilla. I pretty much only open IE for testing…and I’m on a PC, no Mac for me…So, nope, not experiencing that problem (login didn’t work in IE either, if I recall correctly).
Elfie

Thanks sexygirlgeek. I was about to dump the whole thing and reinstall and you fixed the problem. Excellent work; give your dad and coworker a pat on the back!

Thanks for the help sexygeekgirl. All is well now!

All is well but now I can’t log out?

I’m having the same problem, and none of the fixes here work for me. Interestingly, when I click “Lost Password,” and enter my user name and it emails it to me with my password, it says that my username is blank, but gives me a new password.

The blank username should be fixed by #3 here:
https://www.ads-software.com/support/3/7091

Ok, I got back onto mine… I’m 99% certain it has to do with the blog being at a different address than the wp install, but there’s a way to get back on using phpMyAdmin.
You can use the guide that podz created as a general guide as to how to change the values of a field. Assuming that you did not change the prefix for the tables, do the following:
1. Go into your WordPress database (or whatever you named it)
2. Open the wp_options table
3. Click on Browse at the top
4. Copy the siteurl address from option_id 1, which should be the top record visible.
5. Go to Page 3 using the drop box near the top.
6. Scroll down to option_id 105, which has the option_name value home. If your blog install is at a different address than your wp install, this will show the Blogaddress.
7. Using the technique podz shows, change the value here to be the exact same as the siteurl value from option_id 1.
8. Click Go.
9. Login to wordpress.
10. Go to Options >> General in the wp admin pages and change the BlogAddress back to the location of the blog.
In my case, I have https://www.publichealthcenter.com as my siteurl. I changed my home value from https://www.publichealthcenter.com/archives/ to match my siteurl. I logged in and immediately went to options and changed it back. Everything works normally now.
I hope this helps. It is obviously not a long-term solution for the problem, but it will get you back into your admin pages if you cannot access them.

Sexygirlgeek rocks!!!!

I’ve just installed WP and ran into the problems described in this thread. Like sexygirlgeek, I have 2 installations of WP in two completely different directories. In both cases, the blog (index.php) and wp-* are in the same directory. The second installation was done yesterday and all I’ve done so far is added a few users (they registered themselves). Today, I have been locked out of admin. I created another user and got locked out of that too!
At this time, my first WP installation is still working fine.
So, I asked a friend to login with my admin password and she could get in fine. But, still, it didn’t work for me so it seemed to suggest it’s a problem with my cookies rather than the login code itself. I deleted all my cookies and emptied the browser’s cache. Applied to fix from sexygirlgeek’s code, and now it all works.
Just wanted to let you guys know that this is a recurring problem, and that the issue most likely seems to be related to the cookies since someone else could login while I couldn’t. Thanks very much for the help, sexygirlgeek. It is very much appreciated. ??
– kielenn

Did you put a different prefix on the tables for the second install of WP?

SEXYGIRL! THANK YOU! THANK YOU! THANK YOU! THANK YOU!

And yes, agreed – this IS a recurring problem. This should be listed in a standard FAQ section.
By the way, is there any thought to putting a standard FAQ together for the common bugs like this? I spent nearly 2 hours trudging through all the posts that relate to this – and this is the only one that worked.

Actually a better solution might be to use:
define('COOKIEPATH', preg_replace('|https://[^/]+|i', '', get_settings('siteurl') . '/' ) );
… since siteurl is the path to the WP installation, which is probably the only place these cookies are set and used.
Does anyone know why cookie paths exist? Is this a security thing?