JS (a11n)

It seems to ONLY allow notification to go the WordPress.com owner if the site is down. My client ALSO requires an email notification to go to him also as he owns the website. How can I achieve this so the notification goes to both of us if a site is down.

Jetpack Downtime Monitor notifications are sent to all connected admin accounts.

It sounds like you’ve connected your WordPress.com account to your WP Admin account on the site, which is why you’re getting those notifications. To enable your client, or anyone else, to also receive those notifications, they can follow the steps in this guide to also connect their WP Admin account to their own WordPress.com account on the site:

https://jetpack.com/support/transfer-your-jetpack-connection-or-plan-to-another-user/additional-users/

How did you add Related Posts to the site? Are you using a Related Posts block, a shortcode, something else?

You can still share your posts to Twitter manually by pasting the post link into the body of your tweet.

You can also contact Twitter directly about their changes here: https://help.twitter.com/en/forms

I’m going to mark this thread as resolved for now.

Could you please post your site URL here so that we can have a look?

If you want it to remain private, you can also contact us via this contact form:

https://jetpack.com/contact-support/?rel=support&hpi=1

If you choose to reach out directly, please include a link to this thread.

Thanks!

Ever since I installed Jetpack, I got like a 1000 notifications in the backend for things to do with it.

You can manage notifications in your WordPress.com account, including disabling them. You can learn more about that here:

• https://jetpack.com/support/notifications/
• https://wordpress.com/support/notifications/

Also, having Jetpack installed actually slowed down my website.

That sounds unusual. Could you please post your site URL here so that we can have a look?

If you want it to remain private, you can also contact us via this contact form:

https://jetpack.com/contact-support/?rel=support&hpi=1

If you choose to reach out directly, please include a link to this thread.

Thanks!

That sounds unusual. Something else on the site may be conflicting with Jetpack and causing the error.

The best way to find out if something is interfering is to test for a theme or plugin conflict. You can do that by following these steps:

1. Temporarily deactivate all plugins except Jetpack, and clear your browser’s cache.
2. Then, try checking the site again. If the site works normally without any errors, then you know another plugin is conflicting here.
3. You can reactivate plugins one by one, checking checking the site after each one to discover which plugin is causing the problem.
4. You can leave that plugin deactivated and/or contact whoever makes that plugin for help resolving the issue it’s causing.

If deactivating plugins doesn’t help, it may be your theme.

1. Temporarily activate a default WordPress theme like Twenty Twenty-One.
2. Then, try checking the site again. If the site works normally without any errors, then you know it’s a problem with the theme. You can contact whoever makes the theme for help resolving the issue it’s causing.

You can also see these theme troubleshooting steps in detail in our Troubleshooting manually guide.

Let us know how that goes!

Due to recent changes introduced by Twitter, certain services like automatic post sharing and Twitter Timeline widgets are not currently functioning

You can still share your posts to Twitter manually by pasting the post link into the body of your tweet.

For help directly from Twitter, we recommend using the options on this page: https://help.twitter.com/en/forms

Could you please post your site URL here so that we can have a look?

If you want it to remain private, you can also contact us via this contact form:

https://jetpack.com/contact-support/?rel=support&hpi=1

If you choose to reach out directly, please include a link to this thread.

Thanks!

If you provide the Jetpack Site Accelerator image URL, we can clear the image in our cache for you. The URL will begin with i0.wp.com, i1.wp.com, i2.wp.com or i3.wp.com.

You can find Jetpack’s scope of support here: https://jetpack.com/support/scope-of-support/

Jetpack cannot access your site’s XML-RPC file, which is causing the problem. This file is used by Jetpack and other plugins and apps 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

Since your site returns a 403 forbidden error for this page, I’d recommend checking the following:

1. Can you see the xmlrpc.php file on your web host server? It should be in the same location as other WordPress files like wp-config.php. If you don’t see the xmlrpc.php file there, please try re-installing WordPress by going to the Dashboard -> Upgrades page and clicking the “Reinstall” button, or contact your web host.
2. Do you use any security plugins that may block access to this file? If so, could you try deactivating them? You might also want to check your site’s .htaccess file for any rules that might be blocking access to the xmlrpc.php file.
3. Does your web host block access to this file? If you don’t find a plugin that may block access to the file, I would recommend contacting your host. If your host only offers XML-RPC access by allowlisting IP addresses, then they will need to allowlist the Jetpack IP addresses listed here: https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/

If you want to learn more details about XML-RPC and how it interacts with Jetpack, you can check out our detailed guide here: https://jetpack.com/support/jetpack-and-xml-rpc

Let us know how that goes!

Glad to hear it. I’m going to mark this as resolved.

Jetpack is not able to connect to the https://northsidelegal.com/ site, which is why stats and other Jetpack features are not working there. Jetpack needs to be connected before doing anything else.

Jetpack cannot access the site’s XML-RPC file, which is causing the problem. This file is used by Jetpack and other plugins and apps 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

Since your site returns a Cloudflare 520 Web server is returning an unknown error message for the XML-RPC page, I’d recommend checking the following:

1. Can you see the xmlrpc.php file on your web host server? It should be in the same location as other WordPress files like wp-config.php. If you don’t see the xmlrpc.php file there, please try re-installing WordPress by going to the Dashboard -> Upgrades page and clicking the “Reinstall” button, or contact your web host.
2. Do you use any security plugins that may block access to this file? If so, could you try deactivating them? You might also want to check your site’s .htaccess file for any rules that might be blocking access to the xmlrpc.php file.
3. Does your web host block access to this file? If you don’t find a plugin that may block access to the file, I would recommend contacting your host. If your host only offers XML-RPC access by allowlisting IP addresses, then they will need to allowlist the Jetpack IP addresses listed here: https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/

If you want to learn more details about XML-RPC and how it interacts with Jetpack, you can check out our detailed guide here: https://jetpack.com/support/jetpack-and-xml-rpc

Let us know how that goes!

The https://angelagoene.nl/ site appears to be hosted with WordPress.com, so they’ll need to reconnect Jetpack for you.

Please log into your WordPress.com account and follow the steps in this guide to contact them: https://wordpress.com/support/live-chat/

The site appears to be only accessible through your local network. You’ll want to move the site to web hosting that makes it available publicly for anyone to access online. Where do you plan on hosting the site?