Server Status: 400 -Bad Request

  • Resolved jenjohn

    (@jenjohn)


    8 years, 8 months ago

    I saw this same issue on a post that is 5 months old but it had no resolution.

    The plugin suddenly stopped working – there have been no WP, theme or plugin updates since the last time it worked. So it’s possible there’s been a change on the hosting side, but I need something more concrete if I am going that route. Is there any debugging or other mechanism for getting more details? The error I get is:

    Server Status: 400 -Bad Request
    Error Message:
    The page you are trying to access is restricted due to a security rule.

    If you believe the security rule is affecting the normal operation of your website, contact your host support team and provide detailed instructions how to recreate this error.
    They will be able to assist you with rectifying the problem and adjusting the security configuration if needed.

    https://www.ads-software.com/plugins/duplicator/

Viewing 15 replies - 1 through 15 (of 16 total)

  • Hey Jenjohn,

    That is definitely an issue you would need to ask your host about. As far a log for the installer there is a link in the upper right corner of the installer called installer-log.txt. It will also be visible via FTP in the same directory you placed the installer.php file.

    Thanks~

    Thread Starter jenjohn

    (@jenjohn)

    It doesn’t even get that far. There is no installer log created nor a failed package. But thanks anyway, I will pursue with my host.

    Yeah that looks like a permission issue as well. Normally browsing to the installer should generate a log file…

    Thread Starter jenjohn

    (@jenjohn)

    Not sure it’s a permission issue. The folder permissions for /wp-snapshots are 755. The json file gets created fine in the tmp subfolder too. It just doesn’t get any further than that. A log file does not get created at all, but three files do: dtoken.php, index.php, and robots.txt.

    What other permissions does the plugin need?

    Thread Starter jenjohn

    (@jenjohn)

    My hosting provider resolved the issue. Had to disable a rule in mod_sec. It’s working again.

    Thanks for posting your solution!

    Thanks also jenjohn, at least we know where to look for.

    I’m also having this issue with our hosting provider. Any way you could let us know which rules they disabled on your side?

    Thread Starter jenjohn

    (@jenjohn)

    No, sorry. I punted the issue to my hosting provider. Gave them access to the admin to run the plugin. They saw the problem right away. Since it was working until recently my guess is that they figured out some mod sec rules they changed recently and updated them. Your provider should be able to do the same. Good luck.

    Thanks for letting me know. I will follow up with them on this then. Cheers! ??

    Hi @jenjohn

    I just recently started experiencing this same issue and wondering what server host you are with?

    Not Siteground by chance are you?

    Funny enough, I’m on Siteground experiencing this issue.

    Kick up a chat with support.
    They added a snippet of code to my .htaccess file which bypasses the mod_security component that they changed.

    I asked him if it would be possible to copy paste the code to my other sites but he said ‘be extremely careful because it may be a different number on a different site’s environment – it’s better to chat to us for each site’.

    So naturally, I tried it on one of my other sites and it fixed it fine. Use at your own risk:

    # Added by Siteground Support Team
<IfModule mod_security.c>
SecFilterRemove 001838
</IfModule>
    Thread Starter jenjohn

    (@jenjohn)

    Hi @jatacid,
    Yes, it’s Siteground. Glad you worked it out with them. Their support is pretty responsive.

    Hi @jenjohn,

    Yeah good support. But that’s so bad of them to disable a core functionality like that. New server environments should only be applied for new customers only imo.

    Pfff… Thanks Jatacid, it worked. So glad my car not yet has to update every morning. But that day will come, god help us.

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘Server Status: 400 -Bad Request’ is closed to new replies.