• So we are having the following issue:

    When testing the REST API, an unexpected result was returned:

    REST API Endpoint: /wp-json/wp/v2/types/post?context=edit
    REST API Response: (500) Internal Server Error

    We are running on 8 GB on an isolated server so I don’t think it is a server issue in terms of capacity/memory.

    I’ve tried the following: Disabling all of our plugins, activating them one at a time, clearing my cache and refreshing the site cache, updating the permalinks/refreshing (whatever you call it), using a plugin to disable the RESTful API, uninstalling that plugin and using a plugin to “extend the JSON”, when that didn’t work I disabled that plugin.

    To make this more complex, we are using a reverse proxy configuration (we have to because of our business) – Reverse Proxy Guide – Apache HTTP Server Version 2.4. If I don’t edit ANYTHING in WordPress, the site works fine, but when I try to modify a page in the backend I’m booted out after like a minute and then this 500 error renders. Luckily I have a backup of the database but I’m wondering if anyone has any advice?

Viewing 1 replies (of 1 total)
  • Moderator t-p

    (@t-p)

    I’ve tried the following: Disabling all of our plugins, activating them one at a time

    If that does not resolve the issue, try switching to the default theme for your version of WordPress to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

    If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.

    If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message.

    Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

Viewing 1 replies (of 1 total)
  • The topic ‘Internal 500 error’ is closed to new replies.