WordPress.org

Support

Support » Plugins and Hacks » [Resolved] Apache Error

[Resolved] Apache Error

  • I have a reoccurring appearance of the following in my Apache’s error log that coincides with UpdraftPlus’s backup run. For example,

    [Fri Aug 01 02:26:25 2014] [error] [client 162.144.85.142] exec used but not allowed in /home/mydomain/public_html/500.shtml

    I am utilizing…
    WordPress Version 3.9.1
    UpdraftPlus Version 1.9.17
    VPS hosted by HostMonster

    While I typically run with a heavily-ruled .htaccess, I have confirmed that the error still occurs even with the vanilla WP-provided rules, which are:

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    # END WordPress

    I have configured the backup files to upload to Google Drive.

    Whenever I’ve checked, the contents of the backup files are valid.

    Perusing my UpdraftPlus logs, I do not see any glaring errors.

    I did notice that there is a .htaccess within the UpdraftPlus folder, containing the single line “deny from all”. Is this used to temporarily block site access while UdP does it thing? Might such an attempted file swap be the cause of my error log entries?

    Thanks for your time.

    https://wordpress.org/plugins/updraftplus/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author David Anderson

    @davidanderson

    Hi,

    exec used but not allowed in /home/mydomain/public_html/500.shtml

    The message seems to be saying that you have a file, /home/mydomain/public_html/500.shtml, which includes an ‘exec’ command; but that Apache is not configured to allow exec commands.

    Presumably something triggers an HTTP 500 error to bring that file into play, but it looks like the error is about something internal to your Apache setup.

    Best wishes,
    David

    Hi
    I can restore every thing but plugin. Unpacking fails!!
    Please advice.

    Plugin Author David Anderson

    @davidanderson

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[Resolved] Apache Error’ is closed to new replies.