Hi there!
I don’t see anything that could be causing this error. Have you just upgraded Jetpack to the newest version?
Could you please try to downgrade to the version 7.9 from this link and let us know if the issue disappeared? It might be a bug we’ll need to investigate. Thanks!
My site is also having problems with the jetpack upgrade. Have deleted jetpack and everything works fine now.
@cnchambers
What particular problems were you having when Jetpack was enabled?
Hello,
Thank you for the reply!
I’ve downgraded to 7.9 unfortunately problem persists. I still get “Error updating settings. Unexpected token < in JSON at position 0” When settings changed in jetpack. Basically anything requires JSON is not running as it should be in both frontend and backend as mentioned in my previous post.
UPDATE:
1. Turns out this is not JetPack Problem. Indeed the problem disappear when JetPack is disabled but looks like my website is running out of resources when Jetpack is enabled hence why JSON does not run smoothly. Apparently JetPack is a bit resources-hungry plugin. When I disable all plugins except Jetpack the problem disappear. Also, disabling all plugins except Jetpack also makes the problem disappear. However enabling all plugins (including JetPack) is when I start seeing problem with JSON. SO WEIRD! Something is exhausting server resources but not sure what is that thing. But anyways just wanted to report that this is NOT Jetpack related problem and I’ll update this post when I become more certain about the source of the problem.
Kind Regards,
Mohammed Kadhim
Plugin Contributor
James Huff
(@macmanx)
Volunteer Moderator
Jetpack isn’t particularly resource-heavy, but it could be the drop that’s overfilling the bucket.
Here are three ways to increase PHP’s memory allocation:
1. If you can edit or override the system php.ini file, increase the memory limit. For example, memory_limit = 128M
2. If you cannot edit or override the system php.ini file, add php_value memory_limit 128M to your .htaccess file.
3. If neither of these work, it’s time to ask your hosting provider to temporarily increase PHP’s memory allocation on your account. Keep in mind that most decent hosting providers allow users to temporarily increase the memory allocation. If your hosting provider won’t accommodate you, perhaps it’s time to find a new hosting provider. We have some recommendations at https://jetpack.com/hosting/
(in the above examples, the limit is set to 128MB)
I too keep getting random 503 errors. At first I called my hosting provider, but they said it wasn’t on their end. I did a console log with my Chrome inspector and it specifically references Jetpack v4 as what’s associated with the 503 service unavailable. I’m just getting rid of the plugin so my customers can get to my site. It’s kind of bad if your website for your web design company throws a 503 when new clients go to check out.
