The EXACT same thing is happening to me, except the frequency is closer to every 10 minutes. The front end of my site looks and works fine–I’m just completely locked out of the dashboard. I get the same message that you get and when I type in the URL of my WordPress admin panel I get a 403 error.
Please help, I basically cannot edit my WordPress as a result of this issue.
Well I ended up sending that info to my web host and they seem to have fixed it. So far it is working fine. I had the same issue. No access except I got 404 page redirects.
Is your web host iPage? Because I have a ticket in with them and I’m still waiting to hear back.
If it turns out that you do use iPage, would you mind sending me the ticket number so that they can use it for there reference on my ticket?
Yes it is. But that’s not too hard to figure out from the system message above so because I don’t know you I will refrain from revealing my Ticket# just for now.
But you can quote the warning message above and tell them you found it here and it reveals they are the host for a domain experiencing the same problem as you.
Ok, thanks.
Two more questions though:
1. From the time that you submitted your ticket to the time the issue was resolved, how long did it take?
2. When iPage said it was fixed, how were you able to confirm that it was fixed?
Are you sure you don’t work for ipage? 🙂
Sorry I should have updated this b4 I replied. At 11pm AEST I was told by ipage it was fixed. At midnight I tried to log in but was denied access.
I updated my ticket b4 I went to bed with:
As of 10 minutes ago my login page http://onli…/wp-admin/ reads
Access Denied
Forbidden
You don’t have permission to access /wp-login.php on this server
And this morning I read my ticket:
We are glad to know that your issue has been resolved. We value your business and are looking forward to work with you in your future ventures.
Sometimes I wonder about Ipage. They may be cheap but their support really sux at times. Although I must say some of my support requests have been a little flimsy too so it’s forgive and forget.
I’m not getting email replies from Support either so I am having to logging in to follow my support case. Try live chat and ask them why so slow on the reply.
Oh and if you do work for iPage (you only signed up here yesterday) ask them to do follow up emails for support tickets 😉
Good Luck My Friend. We both need it. I’m running Exploit Scanner at the moment and see if any unusual activity might be present. I heave never used it but another thread on this W3TC hack suggested it. I had a Spam Filter plugin but somehow people were getting around it and I allowed some comments that were a little strange but I figured it was a language thing. It could have been a SpamBot though.
Nope, I don’t work for iPage–I’m just a customer trying to use WordPress on a website hosted through them. I’ll be sure to let you know what happens.
Well I have had some success so far. My .htaccess file in the root directory had been written to by W3 Total Cache. The fact iPage stuffed around with it did not help either. They wrote another file and changed the extension to text for the one that had been written to.
Anyway I had a backup on my drive I used and so far so good. Fixed all the things to prevent a hacker getting in (as far as I can go anyway) and now I haven’t had problems after 5 hours logged in.
I bought a ebook with heaps of cool stuff to make it difficult for a novice hacker to get in but if someone reaelly good wants to get in it’s hard to stop in my opinion. Let us know how you are getiing on with iPage. If you want more info on this book it was the best $30 spent I reckon.
I got an email from iPage a couple of days ago, saying that everything had been fixed. I haven’t had time to check out any of the files in my directory or even mess around on WordPress, however it appears that after whatever fix they did everything is back to normal.
Does anyone have steps to duplicate this or can you submit a bug submission form from the support tab of the plugin for testing?
Sorry can’t help you Fred. I am reactivating W3 on another blog as a test when I get enough courage to try it. This may have been a server related problem I can’t be sure. I do know I carried out the update using the version reported as corrupt from this site but only activated it on one blog.
I have downloaded the version from your site and hopefully it will be clear. I hope so as many files reside on Amazon for both my sites.
Sorry for the trouble, please submit a bug submission form from the support tab of the plugin if you like.
