This page provides some technical information and guidelines about using our products for network administrators, server admins, and web hosts.
Here are helpful Jetpack troubleshooting links particularly relevant for hosting providers:
- How to install Jetpack: https://jetpack.com/support/installing-jetpack/
- Getting Started: https://jetpack.com/support/getting-started-with-jetpack/
- Debug a Site: https://jetpack.com/support/debug
- Error Messages Deciphered: https://jetpack.com/faq-errors
- Troubleshooting Tips: https://jetpack.com/faq-troubleshoot
- Known Issues: https://jetpack.com/faq-issues
- Fixing Jetpack Connection: https://jetpack.com/support/getting-started-with-jetpack/fixing-jetpack-connection-issues/
- Common WordPress Errors: https://codex.wordpress.org/Common_WordPress_Errors
- Support Docs: https://jetpack.com/support
- Help Forums: https://wordpress.org/support/plugin/jetpack
Download a printable PDF of these Jetpack links.
Jetpack-Specific System Requirements
Read more about Jetpack’s Server Requirements. Don’t worry—it is virtually the same as what WordPress expects.
XML-RPC Support: WordPress.com and Jetpack
XML-RPC is used by Jetpack to connect sites to WordPress.com. Some hosts and plugin developers believe that blocking access to
/xmlrpc.php will stop various hacking attempts. However, XML-RPC support has been built into WordPress core since version 3.5 and is a stable tool.
Jetpack, much like other plugins, services, and apps (like our mobile apps), relies on the XML-RPC API to communicate with WordPress.com. If this is blocked, your Jetpack connection will not work correctly. To learn more about how Jetpack uses XML-RPC, see our support article about Jetpack and XML-RPC.
You should be able to protect a site’s XML-RPC file without having to allowlist specific IP ranges. The most popular hosts out there use tools like fail2ban or ModSecurity, for example. If you opt to allowlist our IP addresses, please see our instructions on how to add our IPs to an allowlist for Jetpack and VaultPress.
In order for a blog or forum to use Akismet to check spam, it needs to be able to make outgoing TCP connections to servers at Akismet.com. If your network normally blocks outgoing connections from your public web servers, you’ll need to add a firewall rule permitting connections to Akismet.
If your security filters allow exceptions based on hostnames, you should permit connections on port 80 to these:
Most Akismet API calls will be made to a hostname of the form api_key.rest.akismet.com, where api_key is an alphanumeric string that is different for each website owner.
If your security filters only allow IP-based rules, please refer to the Akismet Hosting FAQ for the list of current IP addresses.
Akismet Specific System Requirements
Akismet is a spam filtering service. It’s most commonly used with WordPress but is often used with other blog platforms, forum applications, contact forms, and similar web apps. It’s a centralized service, so TCP connectivity to servers at Akismet.com is required for it to work.
System requirements for the WordPress plugin are the same as for WordPress, plus:
gethostbynamelfunctions must not be disabled (they are enabled by default in PHP).
- TCP connectivity to akismet.com
System requirements for other Akismet plugins and implementations vary, but TCP connectivity is always required.