Troubleshooting Jetpack Error and Could not Connect to WordPress.com

Jetpack error

Troubleshooting Jetpack Error and Could not Connect to WordPress.com

At one time I have problems about Troubleshooting Jetpack Error and Could not Connect to WordPress.com, there was a problem and there is an inscription “Jetpack site inaccessible 403 error with XML-RPC.php” when will enable it to connect to WordPress.com. The usefulness of this plugin a lot of benefits, in addition to prevent spam, there is also a CDN service on wordpress.com, and other features that I can not write here.

This problem makes me confused, until finally I was dealing with an .htaccess file page, cpanel, and the problem was completed, and then how to solve problems with Jetpack plugin in WordPress? Previously I will review about the xml-rpc.

What is XML-RPC?

XML-RPC.php is the file dealing with the Remote Procedure Call or RPC on your server, and this is very important for a WordPress website in order to function properly. This allows the operating system that runs in different environments to make procedure calls over the internet, here call the procedure means that there is a piece of software on the internet somewhere on the web, and call other software functions at several different locations. There is a function in it, which helps in writing XML-RPC client and server. In addition there are some functions in it that you can use. Check the full list here http://php.net/manual/en/book.xmlrpc.php. In the case of this error, file xmlrpc.php not accept the traffic correctly, so Jetpack ending error.

How do I Resolve The Error?

Several methods have been tried. And, here is one way that works in my case. We simply edit the .htaccess file and add a code, it is advisable to be very careful in changing the contents of the .htaccess file, because this is the main file to call all of the contents of the data in a MySQL database, it is advisable to back-up your data first. This method is risky and dangerous way, so you should immediately return it to its original position so that things that are unwanted not the case. Risk is allowing web you have holes security holes that can be used by people who are not responsible.

(See also: How to increase the speed at wordpress)

  • To edit the .htaccess file just open cPanel and then select File Manager.
Troubleshooting Jetpack Error on WordPress
Cpanel V3
  • Then select the Web Root (public_html / www) and tick the option Show Hidden Files (dotfiles). Click the Go button.
Jetpack Error on WordPress
Show Hidden Files on cPanel
  • Then select the .htaccess file in page file manager, right-click, and then click Edit Code option.
Troubleshooting Jetpack Error
Edit .htaccess on cPanel
  • Then it will open a new tab. Immediately add the following code to the last line.
<FilesMatch “xmlrpc\.php$”>
Satisfy Any
Allow from all
</FilesMatch>
  • Then click the Save button.
Troubleshooting Jetpack Error
Edit file .htaccess on cPanel

Extra change this code should be accompanied by the use of plugins Disable XML-RPC Pingback. Do not use the addition of the above code without using this plugin, because it will not function normally, it is advisable to download the plugin and change the .htaccess file.

Immediately after the .htaccess file was changed. Log back in to the WordPress Dashboard page then please direct Jetpack plugin enabled. Activate by pressing the Connect button to connect to it with WordPress Jetpack, and see the results.

Conclusion

Problems in Jetpack due to problems in the XML-RPC.php, file dealing with the Remote Procedure Call or RPC on the server, and this is very important for a WordPress website in order to function properly. And with the permission requests .htaccess everything goes well. May be useful, and if there are still problems, please comment.

Troubleshooting Jetpack Error and Could not Connect to WordPress.com
4.5 (90.37%) 81 votes

Follow Me

Asep Ulchre

This website written by single admin, he's like coffee, like the python programming language and art lovers.
Follow Me
%d bloggers like this: