Can’t read xmlrpc.php at all

WordPress’ XML-RPC file is safe. The fore-mentioned security exploits were plugged in v1.5.1.3. As for your XML-RPC file, make sure that it is world-readable with permissions set for at least 644. If that doesn’t work, try 666.

if I am supplying the same login to the security setting in Ecto, as the one I use to be me, the owner, why would the world premission matter?

btw- the permissions are already set to -rwxr–r–

the wordpress folder is drwxr–r-x

still fails, Forbidden 403

to prove this point, I changed xmlrpc.php permissions to -rwxrw-rwx

still fails, Forbidden 403

?

Well, I can say that your problem is unique. XMLRPC is only supposed to return a 403 if your server denies access to the file, or if you use the wrong login/password combination. So, the problem is definitely on your end.

the only file I edited outside of the theme files is the config… I just replaced every other file in the 1.5.1.3 update, so I know this is true. btw- I never found anything called .htaccess (or close to that)

The admin pleads ignorance.

here is the config
—
<?php
// ** MySQL settings ** //
define(‘DB_NAME’, ‘wordpress’); // The name of the database
define(‘DB_USER’, ‘admin’); // Your MySQL username
define(‘DB_PASSWORD’, ‘psswd_not’); // …and password
define(‘DB_HOST’, ‘127.0.0.1:4004’); // 99% chance you won’t need to change this value. Yes, this is changed.

// Change the prefix if you want to have multiple blogs in a single database.
$table_prefix = ‘wp_’; // example: ‘wp_’ or ‘b2’ or ‘mylogin_’

// Change this to localize WordPress. A corresponding MO file for the
// chosen language must be installed to wp-includes/languages.
// For example, install de.mo to wp-includes/languages and set WPLANG to ‘de’
// to enable German language support.
define (‘WPLANG’, ”);

/* Stop editing */

define(‘ABSPATH’, dirname(__FILE__).’/’);
require_once(ABSPATH.’wp-settings.php’);
?>

Try asking the Ecto Support forums. There are no cases similar to yours, and I have to stand firm by the fact that XML-RPC is only supposed to return a 403 if your server denies access to the file, or if you use the wrong login/password combination. Hopefully someone with Ecto support has encountered something like this.

thank you for looking at this – I’ll keep going…

ecto support here. I’m dealing with this user’s issue on my forum as well. I’m baffled as it’s neither WP nor ecto. Even if the login/password combination is wrong, this user should still be able to access the file. He should then see “XML-RPC server accepts POST requests only.” if he were to access the file via the browser or using curl or whatever.

One thing comes to mind: do you have any plugins activated for your WP blog? If so, which plugins?

OK, this should be sorted now. For anyone else with the same issue, make sure your server’s httpd.conf file doesn’t contain:

<Files ~ “xmlrpc\.php$”>
Order deny,allow
Deny from all
</Files>

One easy way to find out is to rename xmlrpc.php to like xmlrpc2.php.

I’m having the same issue with my site. I was trying to get it to work with flock and flock just hangs at “Just double checking that your account is set up correctly…”

I try to go to the xmlrpc.php file in my browser and I just get a 403 forbidden. I tried renaming it I get the same thing. I even deleted and downloaded wordpress again and extracted the file to my server. I get the same thing.

It may be that my host is blocking any file named xmlrpc.
I tried typing https://inyourgrill.org/xmplrpc and https://inyourgrill.org/xmlrpc23467.php. Even though the file didn’t exist I got a 403. I renamed the file test.php and went to it and got the expected “XML-RPC server accepts POST requests only.”

I tried to submit a post to my hosts ticket system. It appears they are blocking the word xmlrpc anywhere in the post data. I couldn’t even submit the trouble ticket without spelling xmlrpc like this x m l r p c.

The company I’m hosted with is https://www.page-zone.com. I’ve been with them for like 3 years, but if they don’t fix this I will be switching very soon.

I have had exactly the same issue trying to get Flock to submit to my XMLRPC interface. I tried loading the file by hand into a browser, and got a 403 error.

My fix was to rename the file to something else (for instance remotepost.php) and point Flock there.

My guess is that the httpd.conf is blocking the file as suggested above, but my server arrangement will not allow to find out for sure.

??