Hi there, @junction058,
When Jetpack reports 500 errors, they indicate there is something at the server’s end that needs to be addressed.
The first thing to try is to increase the memory available to WordPress, though I highly recommend reporting this to your hosting provider dierctly:
https://docs.woocommerce.com/document/increasing-the-wordpress-memory-limit/
If that doesn’t work, can you check your error logs to see what exactly is going wrong? Your host can help you find them if you need help. If that’s the case, please share them via contact form – please include a link to this thread so we can connect the dots 🙂
Let us know what you turn up!
Hello @junction058,
Do you have updates about the above? We usually close inactive threads after one week of no activity, but we want to make sure we’re all set before marking it as solved. Thanks!
Hi there,
Increasing the memory limit didn’t solve the problem. Also, no errors are showing up in the error log, even with debug mode on.
Hi @junction058,
Thanks for getting back to us.
At this point, I recommend reaching out to your hosting provider and asking them to specifically check the server logs for any errors related to the 500 Internal Server Error you’re seeing when connecting Jetpack. They may be able to identify server-side issues that aren’t visible from within WordPress. We’re limited in what we can see from our side, as this error is occurring at the server level.
Let us know what they find or if you need further assistance!
Hi there, @junction058,
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!
