500 Internal Error When Replying to Posts

Hi @jdalby

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. This could be causing the 500 errors.

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; that should solve your issue.

Hello @jdalby

Do you have updates about that? 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 Joseph. I did not notice the alert of your response. I have just finished with the SSL tips you gave. The 500 error is still happening. I will doublecheck all of the settings.

Thanks for the advice.

It appears that the 500 error is still present when posting replies.

Hi @jdalby, could you ensure that Jetpack isn’t blocked by the server by asking your webhost to allowlist the Jetpack IP addresses listed on this page.

So the 500 error is gone, but instead of loading the comment that is submitted, it now puts the home my site inside the comment window. So a slight improvement.

Hi there. One issue I noticed is that although your site no longer loads at https:// – If you go to the http url, it redirects to your site’s homepage, which is not a WordPress site. I’d suggest making sure that it redirects to your WordPress blog’s home page instead.

Aside from that, it looks like there’s an issue with the site’s XML-RPC file, which may be 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

This file on your site is redirecting to the home page instead of showing the required message, which is preventing Jetpack from connecting.

This is most likely because a plugin, theme, or your site’s wp-config.php file has extra “blank spaces” (new lines, spaces, tabs, …) before the first <?php in the file.

I’d recommend following the troubleshooting steps listed here to fix that:

https://jetpack.com/support/getting-started-with-jetpack/what-do-these-error-messages-mean/blank-lines-xmlrpc/#troubleshooting

Let us know how that goes!