Jetpack crashed my website

Hi @fondueski

If you deactivate all the plugins, and then activate only Jetpack, does it still crash? If not, that would indicate another plugin is conflicting with Jetpack.

A couple other things to check:

I ran some tests on your site, and it seems that although your domain has a valid SSL certificate, it is still possible to access your site via HTTP. Your visitors and search engines can use either HTTP or HTTPS to access your site.

This is an issue for search engines, since it often causes confusion and duplicate content, but it is also an issue for your site’s communication with Jetpack, as our system does not know whether it should connect to your site via one or the other address.

To solve this issue, I would recommend that you change your site’s URL to HTTPS (you can do so under Settings > General in your dashboard), and then ask your host for help redirecting all traffic from HTTP to HTTPS.

If your host is unable to help with that, you can follow the instructions here to do so:

https://www.wpbeginner.com/wp-tutorials/how-to-add-ssl-and-https-in-wordpress/

Also, when Jetpack is trying to connect, we’re seeing an error message here:

https://www.socalspeedscene.com/xmlrpc.php?for=jetpack

That error message means that your hosting provider is blocking some kind of requests to their servers (where your site is located). We see this oftentimes when the server has modsecurity enabled, and the host just needs to open it so Jetpack can connect.

Thanks for the reply, Bruce. Yes, when I disable all plugins and Jetpack is the first activated, it breaks the site. Years ago I switch to https and I believe I did all the htaccess and other changes properly, but I will double check. Here is the error details I got today when I once again disabled all plugins and then activated Jetpack:

Error Details ============= An error of type E_ERROR was caused in line 222 of the file /hermes/walnacweb04/walnacweb04aa/b177/moo.socalspeedscenecom/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/legacy/class-jetpack-signature.php. Error message: Uncaught Error: Call to undefined function ctype_digit() in /hermes/walnacweb04/walnacweb04aa/b177/moo.socalspeedscenecom/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/legacy/class-jetpack-signature.php:222 Stack trace: #0 /hermes/walnacweb04/walnacweb04aa/b177/moo.socalspeedscenecom/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-client.php(201): Jetpack_Signature->sign_request(‘kjUmYK%3h7oXDXJ…’, 1729972297, ‘vvCXOjrZwH’, ‘QKmIj0XH3cvJF6e…’, ‘POST’, ‘https://public-…’, ‘{“jpsq_sync-172…’, false) #1 /hermes/walnacweb04/walnacweb04aa/b177/moo.socalspeedscenecom/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-client.php(42): Automattic\Jetpack\Connection\Client::build_signed_request(Array, ‘{“jpsq_sync-172…’) #2 /hermes/walnacweb04/walnacweb04aa/b177/moo.socalspeedscenecom/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-client.php(475): Automattic\Jetpack\Connection\Client::

Hi @fondueski

Thanks for sending the error over. The key bit that I pulled out of there is this:

Call to undefined function ctype_digit()

The error “Call to undefined function ctype_digit()” is occurring because the PHP ctype extension is not enabled on your server. This extension provides functions for checking character types, including ctype_digit(). This issue affects Jetpack functionality and can also impact core WordPress features that rely on the ctype extension.

I would recommend contacting your hosting provider and ask them to enable the ctype extension for PHP. If you have access to server configuration, you can try enabling it yourself:

• For cPanel users: cPanel > Select PHP Version > Extensions > Check the box for ‘ctype’ > Save.
• For other setups: Edit php.ini and add “extension=ctype.so”, then restart the web server.

Hey @fondueski,

Do you have updates about that, do you still need help? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!