Thread Starter
accer
(@accer)
My hosting company has thoroughly investigated the issue and it is not them. Here is their response:
We have checked your concern and we are also able to replicate the issue from our end. Unfortunately we are unable to find any issue in the server which causes this issue. We have tried by disabling the plugins and themes in your server, but it didn’t fixed the issue. We are also unable to find any redirect rule set for the login page. Please note that there is no rule set for preventing the login to the wordpress login credentials. We are expecting that the issue is related the coding in wordpress.
So I am now back with not knowing what to try.
I have not tried reinstalling all of WordPress. What is the best way to do that? How do I do that so as not to loose all the work that has gone into the site?
Any help would be appreciated?
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
I suddenly can’t login to one of my WordPress sites. When I enter login details, it simply recycles to the login page and there is no error message.
…
I have not tried reinstalling all of WordPress.
Hold off on that for now. Start with the basics: what’s the URL of that one site that’s not letting you in?
Thread Starter
accer
(@accer)
Thanks for the response.
It’s but the site works fine. The control panel login is . It loads fine, but will not let me login, just recycles with NO error message such as one indicating the password is wrong.
Thread Starter
accer
(@accer)
Okay not sure why the links didn’t post
They are:
accertruth.com
&
http://accertruth.com/wp-login.php
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
It loads fine, but will not let me login, just recycles with NO error message such as one indicating the password is wrong.
Right, I got that. I wanted to see if your site was compromised which often becomes apparent when you look at the URL. If you don’t want to share the URL that’s fine.
Edit: Laughter. Thanks for posting them, I’m taking a look.
Something’s interfering with the login process so let’s see if you can identify it using the process of elimination.
Using FTP or whatever filemanagement tools your host has provided you with navigate to the wp-content directory and rename plugins to plugins-old.
Don’t delete anything just rename that plugins directory. Then clear your browser’s cookies and cache and revisit http://your-wordpress-URL/wp-admin/ to login.
See if that does it or not.
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
OK so your site is coming up clean so that’s good.
http://sitecheck.sucuri.net/results/accertruth.com/
Try that plugin advice and see if you can get in after that.
Thread Starter
accer
(@accer)
I have removed the plugins (by renaming the folder) several times and so did my hosting company.
Please note my original post that I have tried everything on the post
http://codex.wordpress.org/Login_Trouble
So just to be specific, I have already tried:
1. Enable Cookies (and cleared them)
2. Disabled Plugins
3. Deactivate Themes
4. Uploaded a New Login File
5. Edited Users Table (for password)
6. Confirmed the siteurl value in the wp-options in the database.
I guess I could go through those steps a third time, but I did the list twice with no results.
Thread Starter
accer
(@accer)
Now that I have more clearly listed what I have already tried, I am not getting any advice on what to do next. But I still can’t login.
It seems to me that something in WordPress must have become corrupted, so that I need to reinstall WordPress, but how do I do that without loosing the content of my site? Are there any directions available for doing this?
Or are there other specific WordPress files that I should try to replace one by one to see if I can find the problem. What files get accessed during the login process?
The content of the site is stored in the database and in the wp-content/uploads folder.
Your login page shows a script running for plugins/portfolio-slideshow. That shouldn’t be there. Also it show wp-super cache is used on the site. You can’t just rename that plugin, you need to uninstall it as it has made changes to the .htacess file.
Delete the wp-includes and wp-admin folders. DO NOT delete the wp-content folder. Down load a fresh copy of WordPress and unzip it. Using ftp or the file manager program provided by your host, upload the unzipped folders wp-includes and wp-admin.
Thread Starter
accer
(@accer)
Thanks so much for your help! I am confused by the plugin issues:
Your login page shows a script running for plugins/portfolio-slideshow. That shouldn’t be there. Also it show wp-super cache is used on the site. You can’t just rename that plugin, you need to uninstall it as it has made changes to the .htacess file.
How do I uninstall those two plugins without the dashboard? I can of course just delete them via FTP, but do you mean something else?
I also know I will need the database info from the current wp-cofig file. Is there any other file with info in that I will need? I will of course backup before I change anything.
Otherwise, what you describe is very clear and within my capabilities.
The script that is on your log in page just shouldn’t be there. Reinstalling the wp-admin and wp-includes folder will hopefully fix it. You can just rename that plugin using ftp.
Two ways tp handle wp-super cache. One, just leave it turned on. It probably isn’t causing the problem. The other is to rename it and then delete all the entries it made in the .htaccess file.
I also know I will need the database info from the current wp-cofig file.
You are not deleting any files in the root directory just the folders wp-includes and wp-admin so that file should be fine but it is never wrong to have copies/backups of active files like that one and htaccess.
Thread Starter
accer
(@accer)
Well, this is a frustrating one.
I reinstalled before I saw your note. So I reinstalled wp-includes and wp-admin and also the wp files in the root directory with the exception of wp-config. I also took care of the two plugins and so there is no script showing up in the login page.
However, same result. It still just recycles when I try to login.
Two more clues/things to consider.
1. I tried putting the wrong password in and I get the same recycle–no error message about incorrect password. So it does not seem to send the login details at all, it just recycles the page.
2. How can this issue be isolated to this one WP site? I have 45 other WP sites on the server and I can login to them with no issues?
Any further ideas would be welcome. Thanks!!!!
Thread Starter
accer
(@accer)
Any other ideas on what to try.
My hosting company says there is nothing on the server causing this. So WordPress looked like the culprit. But having re-installed WordPress that does not seem to be the case.
I am really at a loss as what to try or to search for. But I still can’t login. Any ideas would be much appreciated.
Thread Starter
accer
(@accer)
Well I was finally able to solve the problem, but have no idea what was causing it. Previous attempts should have solved the problem if the final solution did. But they didn’t, so I will post what I did so that others who face the same problem can try it.
I first downloaded (backed up) everything: Basically download via FTP the 3 folders, WP-Admin, WP=Content & WP-Includes plus all the individual files (not other folders) in my root directory. Also I printed out the contents of my wp-config file as that data is needed later.
Next I deleted via FTP everything mentioned in the previous paragraph.
Third, I made what was now a new install of WordPress via Fantasico including letting it create a new database inside of cPanel. I could now login.
Fourth, I edited my WP-Config file replacing the new database info with the old database info from the printout of my old WP-Config file.
Fifth, I uploaded via FTP the content of my old WP-Content folder. I did this folder by folder (ie each plugin and theme separately) checking that I could still login after each folder was uploaded. But I had no issues all the way through, so if you are brave, try it all at once.
Perhaps this will help someone in the future with similar issues. But at least for me it is fixed (if not solved or understood).
