debbylevinson

I've been using RBrowser, a Mac file transfer client. I used the import/export plugin to move the data into a fresh ProcessWire install, so I'm sure everything arrived; presumably it all has the correct permissions, since it was a fresh install. The only folders/files whose permissions I changed were the ones in assets, since those had to be 777 to get anything to work at all. There is nothing in the cache folder.

That's the process I used to try resetting the password. Although it's worked for me in the past, I am still getting the same "login failed" error I got before I reset the password, so I don't know if the password reset worked at all. This is why I mentioned I had two possible valid passwords, and wasn't sure which was the correct one. (But I've been trying both, obviously.) I really do appreciate your suggestions, as well as pwired's. But as I mentioned upthread, I'm out of time to diagnose and fix this myself and am really looking for someone to take over here, even if it means reinstalling from scratch.

Yes, I've tried that -- everything in /site/assets is recursively set to 777, and I've re-created the sessions folder from scratch, ensuring that it is also 777.

I can see the login page, so the first link doesn't apply in this case; what's happening is that whenever I attempt to log in, I get "login failed," even though the username is correct, and one of the two passwords I've tried should also be correct. Changing the sessionName and sessionFingerprint values hasn't done the trick either. If it helps, both the old and new server are running PHP 5.3.10. At this point, I'm out of time to fix this myself, not to mention out of my depth. I'm really looking for someone with more expertise than I have to come in and fix this on my client's behalf. If you're interested in this project, please contact me at debby@alum.mit.edu. Thanks.

I've been helping a freelance client migrate a ProcessWire site from one server to another. His hosting provider is migrating all their customers to this new server, which is not configured in the same way as the current one. As a result, I have had to take the slightly unusual step of using an index.php from the 2.3 dev build on top of a regular install. (See http://processwire.com/talk/topic/5317-cant-log-in-this-request-was-aborted-because-it-appears-to-be-forged/ for details.) Although I've gotten all his data migrated, and ProcessWire is running on the new server, I can no longer log into the admin UI. I have the correct username/password, and even tried resetting the password on the off chance that was the problem. (It wasn't.) It's very possible that something about the new server's configuration is confusing ProcessWire, but as I am neither a ProcessWire expert nor a Unix sysadmin, I can't figure out the problem. (None of the solutions I found on the forums for "login failed" seemed to address the issue.) This may be a fast fix for someone who knows what they're doing. It may not. I can't tell. Either way, please contact me at debby@alum.mit.edu so that I can get a sense of your capabilities, your availability, and your rate for this kind of ProcessWire work.

@ryan, you're the lucky winner! Replacing the index.php file with the one from the dev branch allowed me to log in. Thank you! (Now all I have to do is figure out how to migrate my colleague's files from his current ProcessWire installation into this one, heh.) @soma, I did not have to try turning off sessionChallenge, because Ryan's solution fixed it, but will keep this in mind should the problem somehow crop up again in the future. And Martijn, I assume CodeKit scripts are built into ProcessWire? I didn't install anything from CodeKit on my own. One last question, since this problem does seem to have been related to memcached: do any of you know any other places where this might trip up ProcessWire? I'm not a developer -- just someone who knows enough Unix and site coding to be dangerous -- and I have no idea how memcached works or how it might affect ProcessWire's general functions.

I've recently installed ProcessWire on a colleague's server, but cannot for the life of me log into it successfully; I keep getting the error message "This request was aborted because it appears to be forged." I've tried multiple suggestions linked from this post: Confirming there was a /site/assets/sessions/ directory (even to the point of deleting and re-creating it by hand) Making sure everything in /site/assets/ was set to 777 permissions Adding $config->protectCSRF = false; to config.php (which brought on new failure behavior -- the login page would just reload after submission) Changing the sessionFingerprint value to 'false' and turning on debug mode (which yielded what's essentially this error message, modulo some variable capitalization and line number changes I'm sure are due to ProcessWire updates since that post was originally made) Also, when I have debug mode on, I see this error in the footer: Warning: Unknown: Failed to write session data (memcached). Please verify that the current setting of session.save_path is correct (/srv/psa01/stuartdarsch.com/httpdocs/site/assets/sessions) in Unknown on line 0 The path is correct, and as I said, permissions in that directory (as well as its two immediate parents) are set to 777, so the software should be able to write to it. Any suggestions about how to fix this are welcome. Thank you!

Thanks again! I didn't expect to find a CMS at all on this system when I took over, so those upgrade URLs are much appreciated.

Thank you, kongondo! I've located the admin user and have now reset the password.

I've been trying to help a colleague whose web developer abandoned him without any instructions on how to update his ProcessWire site -- not even a login or password. Is there any way for me to create a new admin user from scratch, even if it means doing this via phpMyAdmin? Or is there a way for me to recover the name of the admin user somehow from the database? (I've tried the password-reset API calls described elsewhere in the forums, but without knowing the name of the admin account, resetting the password is a bit futile.) My colleague is running ProcessWire 2.1, as far as I can tell.