unable to connect to wordpress.com

Hi there,

The chief problem is that your site’s xmlrpc.php file is not responding correctly. While your site is publicly accessible, we cannot access your site’s XML-RPC file. I can’t tell where exactly it’s located, but in both attempts to load up the file in my browser, I got a 403 Forbidden error message and a redirect to your homepage.

Jetpack, WooCommerce, and other plugins and apps use this file to connect to your site. It must return the following message:

XML-RPC server accepts POST requests only.

You can see a working example here: https://wp.cloud/xmlrpc.php

I would recommend that you check the following:

1. Can you see the /xmlrpc.php file at the root of your WordPress installation when accessing your site via FTP? If you don’t, then please try re-installing WordPress. You can do this by going to the Dashboard -> Upgrades page, then clicking the “Reinstall” button.
2. Do you use any security plugins that may block access to this file? If so, could you try to disable them? You might also want to check your site’s .htaccess file for any rules blocking access to the xmlrpc.php file.
3. Does your hosting provider block access to this file? If you don’t find any plugin that may block access to your site’s file, I recommend that you get in touch with your host.

Hi @imagostudio

Is WordPress installed on a subdirectory of your site, rather than in the root? If so, can you let us know where it is installed so we can check things on our end?

Thanks!

Hi @bruceallen

Yes, it is installed on a subdirectory.

https://www.imagostudio.at/imagostudio/

– the xmlrpc file in in this subdirectory
– in my htaccess I cannot find any entries with “xmlrpc”
– I use wordfence, but xmlrpc blocking is not active/and deactivating wordfence does not change my attemts to connect to wordpress.com

https://cloudlogin03.world4you.com/index.php/s/61hNTNS8wdT5UV2

Thanks!
Andreas

Hi @imagostudio

The XMLRPC file at https://www.imagostudio.at/imagostudio/xmlrpc.php is restricted – showing a 403 error.

I’d suggest contacting your hosting provider and asking them to allow our IP addresses listed here:

– https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/

Please note that these IP addresses could change (or more could be added) at any time, which could break your connection to Jetpack. For this reason, we actually discourage whitelisting specific IPs, although with some hosts it may be the only option.`

Hi @bruceallen

I did some homework:

– my hosting provider does not block rpc
– I use wordfence and a xmlrpc pingback plugin, but deactivating them changes nothing
– I did not set any restrictions in my functions.php or any other place

In fact, everything was working fine before using WP Stagging to check some woocommerce payment issues.
– I was connected to wordpress.com
– My iPhone was connected to the woocommerce app
– I did not change any relevant plugin or code since then

Any other ideas? Why my xmlrpc is blocked?
Thanks!
Andreas

@bruceallen

…I do not use jetpack.
I installed it to check if I am able to connect via this plugin…but no result. So jetpack is deinstalled at the moment.

Thanks
Andreas

Hi Andreas,

I’m not sure why https://www.imagostudio.at/imagostudio/xmlrpc.php is showing the 403 error. If you look on that page, it links to your host’s FAQs, which say:

The website visitor receives this error message if they do not have permission to access the website they are visiting. This may well be what the administrator wants. If not, the problem may be with your website. Please note the following problem descriptions and possible solutions:

You don’t have index.htm , index.html or index.php on your webspace.

Your website’s startup file is not in the root directory.

Directory listing has been disabled.

The .htaccess file on the web space blocks the website.

The web space is blocked. In this case, please contact the support on my.world4you.com under Your package > Help / Support .

Your web content files and folders may have the wrong permissions. Most FTP programs allow this change. In most cases, permissions are 755 for static content, for folders, 644 for dynamic content and 700 .

Based on these, it does seem your host is the best place to find out why and how this file is being blocked.

• This reply was modified 2 years, 4 months ago by Bruce (a11n).

Hi @bruceallen

My hosting provider asked me to ad some code into my htaccess file. Now another message appears visiting the url of my smlrpc.php.

But there are some questions:

1) Isn′t it possible anymore to ad a self hosted site to wordpress.com without a subscription?
2) If I try to connect the woocommerce app in my iphone to my store, this app seems to find my store now (it was not before adding the code I mentioned above). But then the app asks me to use jetpack. So using the woo-app is not possible without using jetpack?
3) Then try to activate jetpack on my site still returns an error “An error occurred. Please try again.”

…so I guess the code I added did not solve any issue.
thats frustrating, because everything worked (until the testing of woo-payments on my stagged site).

Thanks for further help!
Andreas

Hi Andreas

1) Isn′t it possible anymore to ad a self hosted site to wordpress.com without a subscription?

Yes, you can still connect a site to WordPress.com without a subscription.

2) If I try to connect the woocommerce app in my iphone to my store, this app seems to find my store now (it was not before adding the code I mentioned above). But then the app asks me to use jetpack. So using the woo-app is not possible without using jetpack?

Correct, Jetpack is required for the Woo app. You can read about that in the FAQ at the bottom of this page:
https://woocommerce.com/mobile/

3) Then try to activate jetpack on my site still returns an error “An error occurred. Please try again.”

Your site’s xmlrpc.php file is working correctly now.

The connection error I’m currently seeing should be resolved by deleting and reinstalling the Jetpack plugin. Please try that and let us know if you still have trouble.

Hi @imagostudio,

Since it’s been more than a week since we’ve heard from you, I’m going to mark this thread as Resolved. If you still need help, please feel free to reach back out here and mark the thread as not resolved.

Thanks!