• Resolved Jaye

    (@dravenloft)


    Facts:
    Running latest update of WordPress
    Have installed latest version of Jetpack
    Have attempted disabling my security plugins.
    xmlrpc.php present and accounted for in root directory of site where it has always been.

    I had contacted my host who had stated that they had temporarily blocked XML-RPC due to an influx of DDOS and other hack efforts directed at that service with no ETR.

    When asking for an ETR I was told that there was a new update that allowed me to control my PHP version and services. i’ve tried PHP 5.4 – 5.6 (think I’ve got it on 5.5 at the moment) and there’s a field to enable XML-RPC.

    Still getting a 404.

    It has been suggested by my hosting tech support that this is a coding error in WordPress or Jetpack and I should create this thread in order to pinpoint the issue.

    https://universal-nexus.com/xmlrpc.php

    Jetpack is not the only service impacted by the XML-RPC 404 so I seriously doubt the issue is within that plugin. i, for example, cannot access my blog via the WordPress mobile app, nor use any online services that interact with the site via the XML-RPC.

    As my understanding of the causes of a 404 error in this situation are all server-side with the hosting firewall options I’ll admit to being at a loss what information would be helpful in this matter, but please just ask for it and I’ll happily supply because I’m rather tired of not having full function on my blog.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator t-p

    (@t-p)

    I had contacted my host who had stated that they had temporarily blocked XML-RPC due to an influx of DDOS and other hack efforts directed at that service with no ETR.

    did it work before your host took this action? Yes? then its a host side issue.

    Thread Starter Jaye

    (@dravenloft)

    Actually, turns out it’s my .htaccess

    I don’t get the error if I have no .htaccess, but if I have this one I get the xmlrpc 404 error.

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On

    #rewriting wordpress stuff to the root
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} ^/wp-((content|admin|includes)|((cron|login)\.php))

    #rewriting everying that can’t be found to index.php
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^index\.php$ – [L]

    # uploaded files
    RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L]

    #rewriting everything else to index.php
    RewriteCond %{REQUEST_FILENAME} -f
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ – [L]
    RewriteCond %{REQUEST_URI} !^/wp-(content|admin|includes|login|cron)(\.php)?
    RewriteRule . index.php [L]
    </IfModule>

    # END WordPress

    I’m not entirely sure what to do to fix this.

    Moderator t-p

    (@t-p)

    I am not sure either. Hope someone who knows chimes in.

    Thread Starter Jaye

    (@dravenloft)

    This .htaccess worked. Which is odd, because I’d switched to the other one because this used to make my sub-domains’ images quit working:

    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]

    # uploaded files
    RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

    # add a trailing slash to /wp-admin
    RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ – [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
    RewriteRule . index.php [L]

    Moderator t-p

    (@t-p)

    Glad to know it ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘XML-RPC 404 Error’ is closed to new replies.