xmlrpc 406 error issues (with mod_security disabled)

  • inspiredmind

    (@inspiredmind)


    7 years, 9 months ago

    Hello,

    Since moving all my sites to a new host (about 6 months ago), I’ve been unable to use any desktop application for posting to my sites. Until then, that was my primary way of posting content to these sites.

    I’ve tried the WordPress.com App, Blogo, and MarsEdit. MarsEdit is what I typically use for publishing content from the desktop (on Mac OS X). None work.

    I get a 406 error when I try to upload a new post. The WordPress.com app doesn’t even manage to download existing posts. It appears to get some stats (directly from WordPress servers, I suspect), but can’t retrieve or send posts/pages.

    Logs on the host server indicated mod_security was producing the 406 error. The host has since disabled mod_security on the server. But I still get the 406 errors, and can’t access the site from a desktop client.

    When I try to access the Settings for a blog, within the WordPress.com App, I get this error in red… There was an error retrieving your site settings. Make sure your Jetpack is up to date

    Yes, Jetpack is up-to-date.

    I run a test on the xml-rpc endpoints over on: http://xmlrpc.eritreo.it/

    Here are the results…

    OK wp.getOptions
    OK wp.getPostFormats
    OK wp.getCategories
    OK wp.getTags
    OK wp.getPostStatusList
    FAIL wp.getComments — 406 Not Acceptable
    OK wp.getPageList
    FAIL metaWeblog.newMediaObject — 406 Not Acceptable

    As you can see, most of the endpoings are fine. But wp.getComments and metaWeblog.newMediaObject both`receive a 406 error.

    I don’t know much about xml-rpc or mod_security. So, I am seeking some guidance on how I might resolve this issue, or at least identify the cause.

    I’ve already tried disabling mod_security locally, by adding the following to the .htaccess file in /wp-admin and root. It made no difference.

    <IfModule mod_security.c>
    SecFilterEngine Off
    SecFilterScanPOST Off
    </IfModule>

    I would really like to get to the bottom of this. Any suggestions are much appreciated.

    Thanks,

    Jonathan

Viewing 1 replies (of 1 total)
  • Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    7 years, 9 months ago

    mod_security can be controlled on the user level and the server level.

    With mod_security disabled on the user level, are the logs still reflecting a mod_security block?

    If you’re using Jetpack, a really quick way to check is to add ?for=jetpack to the end of the xmlrpc.php URL, so example.com/xmlrpc.php?for=jetpack

    If mod_security is still blocking it, Jetpack’s report will reflect that.

Viewing 1 replies (of 1 total)
  • The topic ‘xmlrpc 406 error issues (with mod_security disabled)’ is closed to new replies.