Internal Server 500 Error when connected

Resolved arjunsinghal
(@arjunsinghal)

4 years, 11 months ago

I have installed Jetpack on my personal blog website. Every time I establish the connection with WordPress.com, I am unable to edit the posts and I start receiving Internal 500 Server error, while the site is still working from the front-end. I don’t know if other features are getting affected too, but I am unable to edit the posts, or delete them or restore deleted ones. I have a scheduled post for tomorrow, so I do not know if that will be affected, and if Jetpack will email my subscribers. <- this is the feature I mostly use Jetpack for.
I checked online for the 500 server errors with Jetpack, and tried the following steps – to no avail:
Disable other plugins – I have only a few active ones.
Uninstall Jetpack
Delete the Jetpack folder and reinstall
Connect Jetpack again – but doesn’t work

I removed the .htaccess file and saved permalinks again also. But unable to figure this out. Request help. Thanks

The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)

Plugin Author

(@jeherve)

Jetpack Mechanic 🚀

Could you try to enable WP_DEBUG on the site, and let us know what errors come up you see 500 errors in the editor?
https://gist.github.com/jeherve/e6acfc973c07cb500836804e1044d12a

Thank you.

Thread Starter

arjunsinghal

(@arjunsinghal)

4 years, 11 months ago

Hi Jeremy

Thanks for the quick response.

I got the following PHP Notices.

[12-Apr-2021 12:08:31 UTC] PHP Notice:  map_meta_cap was called <strong>incorrectly</strong>. The post type product is not registered, so it may not be reliable to check the capability "read_post" against a post of that type. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 4.4.0.) in /home/customer/www/r7un.com/public_html/wp-includes/functions.php on line 5313
[12-Apr-2021 12:08:31 UTC] PHP Notice:  map_meta_cap was called <strong>incorrectly</strong>. The post type product is not registered, so it may not be reliable to check the capability "edit_post" against a post of that type. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 4.4.0.) in /home/customer/www/r7un.com/public_html/wp-includes/functions.php on line 5313
[12-Apr-2021 12:08:35 UTC] PHP Notice:  map_meta_cap was called <strong>incorrectly</strong>. The post type product is not registered, so it may not be reliable to check the capability "read_post" against a post of that type. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 4.4.0.) in /home/customer/www/r7un.com/public_html/wp-includes/functions.php on line 5313
[12-Apr-2021 12:08:35 UTC] PHP Notice:  map_meta_cap was called <strong>incorrectly</strong>. The post type product is not registered, so it may not be reliable to check the capability "edit_post" against a post of that type. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 4.4.0.) in /home/customer/www/r7un.com/public_html/wp-includes/functions.php on line 5313
[12-Apr-2021 12:08:35 UTC] PHP Notice:  map_meta_cap was called <strong>incorrectly</strong>. The post type product is not registered, so it may not be reliable to check the capability "read_post" against a post of that type. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 4.4.0.) in /home/customer/www/r7un.com/public_html/wp-includes/functions.php on line 5313
[12-Apr-2021 12:08:35 UTC] PHP Notice:  map_meta_cap was called <strong>incorrectly</strong>. The post type product is not registered, so it may not be reliable to check the capability "edit_post" against a post of that type. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 4.4.0.) in /home/customer/www/r7un.com/public_html/wp-includes/functions.php on line 5313

EOF

Thread Starter

arjunsinghal

(@arjunsinghal)

4 years, 11 months ago

Based on the PHP Notices, I also installed WooCommerce, to enable “Product” post-type. Based on the Site Health recommendations, since I do not use WooCommerce, I had removed the plugin earlier.

I must add, that few weeks ago, I was facing issues connecting Jetpack to WordPress.com, if I did so using Opera (Browser). I do not get connection issues while using Safari to connect.

I do not get any 500 errors in the Debug.log file. But if I try to delete / restore any posts, then I get a 500 error on the screen. I can press back to open wp-admin again, and browse through the posts, but unable to perform any changes.

Plugin Author

Jeremy Herve

(@jeherve)

Jetpack Mechanic 🚀

4 years, 11 months ago

Did you have any Fatal errors happening since you enabled debugging? Those are notices, most likely created by one of the plugins on your site, but none of those should cause any 500 errors.

If you haven’t had any Fatal errors happening yet, could you leave debugging on until that happens, and then check your log file again?

Thank you.

Thread Starter

arjunsinghal

(@arjunsinghal)

4 years, 11 months ago

Debug is on

I am able to navigate to WP Admin, and check things.

But the moment, I click “restore” on a Deleted Post in Trash, or I try to Trash another post, I get the Internal 500 Server Error.

The Debug log is as follows now:

[12-Apr-2021 12:08:31 UTC] PHP Notice:  map_meta_cap was called <strong>incorrectly</strong>. The post type product is not registered, so it may not be reliable to check the capability "read_post" against a post of that type. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 4.4.0.) in /home/customer/www/r7un.com/public_html/wp-includes/functions.php on line 5313
[12-Apr-2021 12:08:31 UTC] PHP Notice:  map_meta_cap was called <strong>incorrectly</strong>. The post type product is not registered, so it may not be reliable to check the capability "edit_post" against a post of that type. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 4.4.0.) in /home/customer/www/r7un.com/public_html/wp-includes/functions.php on line 5313
[12-Apr-2021 12:08:35 UTC] PHP Notice:  map_meta_cap was called <strong>incorrectly</strong>. The post type product is not registered, so it may not be reliable to check the capability "read_post" against a post of that type. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 4.4.0.) in /home/customer/www/r7un.com/public_html/wp-includes/functions.php on line 5313
[12-Apr-2021 12:08:35 UTC] PHP Notice:  map_meta_cap was called <strong>incorrectly</strong>. The post type product is not registered, so it may not be reliable to check the capability "edit_post" against a post of that type. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 4.4.0.) in /home/customer/www/r7un.com/public_html/wp-includes/functions.php on line 5313
[12-Apr-2021 12:08:35 UTC] PHP Notice:  map_meta_cap was called <strong>incorrectly</strong>. The post type product is not registered, so it may not be reliable to check the capability "read_post" against a post of that type. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 4.4.0.) in /home/customer/www/r7un.com/public_html/wp-includes/functions.php on line 5313
[12-Apr-2021 12:08:35 UTC] PHP Notice:  map_meta_cap was called <strong>incorrectly</strong>. The post type product is not registered, so it may not be reliable to check the capability "edit_post" against a post of that type. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 4.4.0.) in /home/customer/www/r7un.com/public_html/wp-includes/functions.php on line 5313
[12-Apr-2021 12:17:18 UTC] Matomo: Apply 404 tracking changes. Blog ID: 1
[12-Apr-2021 12:23:26 UTC] Matomo: Matomo is now syncing blogId 1
[12-Apr-2021 12:23:26 UTC] Matomo: Matomo site is known for blog (1)... will update
[12-Apr-2021 12:23:26 UTC] Matomo: Changed global option last_tracking_settings_update: 1618230206
[12-Apr-2021 12:23:26 UTC] Matomo: Apply changed settings:
[12-Apr-2021 12:23:26 UTC] Matomo: Changed global option last_settings_update: 1618230206
[12-Apr-2021 12:23:26 UTC] Matomo: Save settings
[12-Apr-2021 12:23:59 UTC] Matomo: Matomo is now syncing blogId 1
[12-Apr-2021 12:23:59 UTC] Matomo: Matomo site is known for blog (1)... will update
[12-Apr-2021 12:23:59 UTC] Matomo: Changed global option last_tracking_settings_update: 1618230239
[12-Apr-2021 12:23:59 UTC] Matomo: Apply changed settings:
[12-Apr-2021 12:23:59 UTC] Matomo: Changed global option last_settings_update: 1618230239
[12-Apr-2021 12:23:59 UTC] Matomo: Save settings
[12-Apr-2021 12:24:07 UTC] Matomo: Matomo is now syncing blogId 1
[12-Apr-2021 12:24:07 UTC] Matomo: Matomo site is known for blog (1)... will update
[12-Apr-2021 12:24:07 UTC] Matomo: Matomo is now syncing blogId 1
[12-Apr-2021 12:24:07 UTC] Matomo: Matomo site is known for blog (1)... will update
[12-Apr-2021 12:27:39 UTC] Matomo: Scheduled tasks uninstall all events
[12-Apr-2021 12:30:36 UTC] Matomo: Scheduled tasks sync all sites and users
[12-Apr-2021 12:30:37 UTC] Matomo: Matomo is now syncing blogId 1
[12-Apr-2021 12:30:37 UTC] Matomo: Matomo site is known for blog (1)... will update
[12-Apr-2021 12:30:37 UTC] Matomo: Matomo will now sync 1 users
[12-Apr-2021 12:30:37 UTC] Matomo: Scheduled tasks archive data
[12-Apr-2021 12:30:52 UTC] Matomo: Scheduled tasks update geoip database
[12-Apr-2021 12:30:57 UTC] PHP Warning:  Invalid argument supplied for foreach() in /home/customer/www/r7un.com/public_html/wp-content/plugins/matomo/app/plugins/GeoIp2/GeoIP2AutoUpdater.php on line 324
[12-Apr-2021 13:12:45 UTC] Matomo: Apply 404 tracking changes. Blog ID: 1

Thanks for the follow up. I hope we can sort this out soon.

Plugin Contributor

Dan (a11n)

(@drawmyface)

4 years, 11 months ago

Can you confirm that you’ve tried deactivating all other plugins at the same time? If you do that, and then try trashing a post, do you still see the 500 error, with only Jetpack activated?

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Internal Server 500 Error when connected’ is closed to new replies.