500 Internal Server Error

  • Resolved banyo

    (@banyo)


    7 years, 10 months ago

    Hi there,

    tried this plugin as it looked really good and despite the Comodo SSL being installed on the server, Chrome still pointed to insecure content on the frontend of https://www.generalmings.com, while wp-admin was completely secure.

    I did add

    define(‘FORCE_SSL’, true);
    define(‘FORCE_SSL_ADMIN’,true);

    to the wp-config

    Testing of plugin indicated that SSL was working fine and when checking the frontend, wham, 500 internal server error. First disabled, the plugin, the removed it. Still 500.

    What changes the plugin makes on the site actually remain after removal?

    This is worst case so any ideas much appreciated.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author webaware

    (@webaware)

    G’day Banyo,

    The plugin makes no changes to the website, so deactivating it stops its effect.

    Try removing the new defines you added to your wp-config.php file.

    Also check your website logs to see what is breaking. If you have trouble finding your website logs in your hosting control panel, you can turn on WP_DEBUG and WP_DEBUG_LOG (and turn off WP_DEBUG_DISPLAY) in your wp-config.php file so that logs go to the file wp-content/debug.log:

    https://codex.www.ads-software.com/Debugging_in_WordPress

    cheers,
    Ross

    Thread Starter banyo

    (@banyo)

    Hey Ross,

    apologies for my late reply.

    Internal server error was apparently due to a caching error. Your plugin did not change anything on the site as you said.

    Resolved the issue by adding

    RewriteCond %{ENV:HTTPS} !on [NC]
    RewriteRule ^(.*)$ https://www.yoursite.com/$1 [R=301,L]

    to the .htaccess and removing any modifications from the wp-config.

    https://www.whynopadlock.com/ the was very useful to dtect any insecure content.

    Cheers,

    Banyo

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘500 Internal Server Error’ is closed to new replies.