Hi there @thomasekkkk – Thank you for reaching out!
I understand you are facing issues with your Jetpack connection, let’s sort this out!
I took a closer look at your site, and while your site is publicly accessible, it seems that your XML-RPC file is currently inaccessible. This file is key for Jetpack to function properly, and if it’s blocked, that’s likely what’s causing the issue.
Step 1: Check Your XML-RPC File
To confirm the issue, let’s check your site’s XML-RPC file:
- Visit this https://example.com/xmlrpc.php (replace example.com with your site URL):
- The file should return this message:
XML-RPC server accepts POST requests only.
For reference, you can see how this should look on a working example here:
If your site doesn’t display the expected message and instead shows an error (e.g., a 403 or 404), the XML-RPC file is being blocked.
Step 2: Fix Access to the XML-RPC File
If the file is blocked, here’s how you can fix it:
- Check if any security plugins are blocking access. If so, try disabling them temporarily.
- Review your .htaccess file for any rules that might block the xmlrpc.php file.
- If the above doesn’t help, contact your hosting provider to ensure the file isn’t being blocked server-side. Our requests look like the following:
File: https://yourdomain.com/xmlrpc.php
User-agent header: Jetpack by WordPress.com
IPs: https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/
Please ask them to allow the IP addresses listed above. 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 allowing specific IPs, although with some hosts, it may be the only option.
Step 3: Reconnect Jetpack
Once the XML-RPC file is accessible, try reconnecting Jetpack by following these steps:
If you’d like to learn more about XML-RPC and how it interacts with Jetpack, you can find more details here:
Looking forward to your update!
