Bruce (a11n)

Thanks for the 5-star review!

Cheers!

Merci pour la note de 5 étoiles !

Santé !

Hi @paulogoncalves

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!

Danke für die 5-Sterne-Bewertung!

Prost!

Thanks for the 5-star review!

Cheers!

Hi @jenmini

Do you happen to be using Cloudflare’s Rocket Loader? It is currently not compatible with Jetpack Likes, Site Stats, some shortcodes, and other Jetpack features using JavaScript. You’ll consequently need to disable this feature in your Cloudflare settings.

If no, 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!

Hi @blakoleander

Could you please post your sites URL’s 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!

Hi @aclassifier,

Good news – we’ve identified the root cause of these warnings. They’re related to how Jetpack Protect Status handles certain API responses. This has been fixed in Jetpack 14.3.

To resolve the warnings:

1. Update to Jetpack 14.3 from your WordPress dashboard
2. Clear your site’s cache after updating

If you still see the warnings after updating, please let us know.

Regarding the HTTP/HTTPS access: While both protocols currently work on your site, we recommend enforcing HTTPS for better security. However, this is separate from the warning messages you’re seeing.

@greentp

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!

Hi @greentp

Looking at your stack trace, we can see the deprecation notice is triggered during WordPress core initialization (through wp-settings.php) when Jetpack’s geolocation module is loaded. You mentioned this doesn’t occur during normal WordPress operation but only when using wp-load.php directly.

To help diagnose this, would you be able to check your PHP error logs during normal WordPress operation? This would help determine whether this is an initialization difference or just a difference in error display.

Hi @greentp

This error occurs because Jetpack 14.3 deprecated the Jetpack_Geo_Location class, but your application is still trying to use it. Here are two solutions:

1. Quick fix: Add this to wp-config.php to suppress the deprecation notice:

error_reporting(E_ALL & ~E_DEPRECATED & ~E_USER_DEPRECATED);

2. Better solution: Since you’re using WordPress authentication, switch to WordPress’s native geolocation functions instead of Jetpack’s deprecated class. The geoip_detect2 plugin provides similar functionality.

The error isn’t breaking functionality – it’s just a warning that this feature will be removed in a future version.

Hi @aclassifier

So what this means is that your site loads on both of these addresses:

https://www.teigfam.net/oyvind/home/

https://www.teigfam.net/oyvind/home/

This is a security issue for your site, but may not be the direct cause of the errors you reported. If you temporarily deactivate Jetpack Boost do you still get the errors?

Hi @aclassifier

One thing I noticed is 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/

Once that’s done, try to reconnect your site to Jetpack once again.

Hi @peblogger

Thanks so much for letting us know how our tools have worked for you! We appreciate you!

Hi @eizzumdm

Thank you for reaching out about the Jetpack identity crisis issue affecting your Princeton University sites. I’ve successfully restored the stats and subscribers for the University Archives site (universityarchives.princeton.edu). You should now be able to access all historical data prior to January 22 and see your complete subscriber list.

Regarding the other affected sites under the account, I understand your concern about the ongoing issues. While disconnecting and reconnecting Jetpack has resolved the problem for some of your most active sites, it’s understandable that you’re looking for a more efficient solution for the remaining sites.

Your decision to switch to Jetpack Offline Mode for development environments is a smart one, given the issues you’ve experienced with Safe Mode. This should help prevent similar problems in the future.

If you’re continuing to have issues with other sites, feel reach out to 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!