Can't Post After 3.5.2 Upgrade (ModSecurity Problem)

  • Resolved macfenway

    (@macfenway)


    12 years, 10 months ago

    After upgrading my site to version 3.5.2 a few days ago I now have a problem where I can’t create new posts or preview posts. And once I try to publish a post, I then can’t log back into my Admin panel for a while. (I have seen others reporting similar behavior following the 3.5.2 upgrade.)

    After enabling error log collection on my server, it looks like this is a ModSecurity problem – for some reason when I try to create a post, it thinks that I am “bot” and then blocks my IP address from logging in through the Admin page for a while. Here is an example from my server error logs:

    [Tue Jul 09 10:33:19 2013] [error] [client 173.197.98.2] ModSecurity: Access denied with connection close (phase 3). Pattern match “block” at TX:evalaction. [file “/web/httpd2/modsecurity.d/activated_rules/modsecurity_gd_07_post_guardian.conf”] [line “25”] [id “10705”] [msg “BLOCKED – Bot detected! Score: 44”] [hostname “mcmikephoto.com”] [uri “/wp-admin/post.php”] [unique_id “UdxJX7iomGYAAAMt2yEAAAA6”]
    [Tue Jul 09 10:33:38 2013] [error] [client 173.197.98.2] ModSecurity: Access denied with connection close (phase 3). Pattern match “block” at TX:evalaction. [file “/web/httpd2/modsecurity.d/activated_rules/modsecurity_gd_07_post_guardian.conf”] [line “25”] [id “10705”] [msg “BLOCKED – Botnet IP found!”] [hostname “mcmikephoto.com”] [uri “/wp-admin/admin-ajax.php”] [unique_id “UdxJcriomGYAAG7nS78AAAC5”]

    My provider is GoDaddy (which from what I have seen is not a good thing when it comes to problems like this.) Any suggestions on what I should ask GoDaddy to do would be much appreciated. (Unfortunately, I a m on a shared server so don’t have control over everything on the server.)

    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • gopalb123

    (@gopalb123)

    12 years, 10 months ago

    I have the same problem … its godaddy server problem, they told me they will work on it and it will be fixed with 72 hours. how fanny they are. Last four days my site are down. And they miss guide me its problem with wordpress and my code. please contact godaddy and booked your support ticket.

    Thread Starter macfenway

    (@macfenway)

    12 years, 10 months ago

    Hi Gopalb123,

    Yes, I filed a support ticket several days ago and finally was able to convince GoDaddy that this was not a problem with my code. Standard install of 3.5.2 WordPress, and I have the same problems even with all plugins disabled.

    They have handed my support case off to their Advanced Technical Support team to look at the server, etc., so I am hoping that results in the problem getting fixed.

    mthoney

    (@mthoney)

    12 years, 10 months ago

    I have run into the same problem. I have spent several hours on the phone with GoDaddy as well and got the same answer last Thursday, “We have escalated this to Advanced Technical Support.”

    Not only does this shut down access to WP admin, but it also shuts down access to several other non-WP applications that have /login or other similar URL Profiles.

    This morning I was blocked again. I have requested a move to their new cloud hosting in hopes this will correct the problem. At present, our hosting solution is on the legacy platform.

    Thread Starter macfenway

    (@macfenway)

    12 years, 10 months ago

    It looks like GoDaddy fixed this problem for me. After several attempts with their Customer Support they eventually sent me an email saying that they had whitelisted my IP address on the server running my WordPress instance and that seems to have solved the problem.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Can't Post After 3.5.2 Upgrade (ModSecurity Problem)’ is closed to new replies.