$conf, $runtime; function_exists('chdir') AND chdir(APP_PATH); $r = 'mysql' == $conf['cache']['type'] ? website_set('runtime', $runtime) : cache_set('runtime', $runtime); } function runtime_truncate() { global $conf; 'mysql' == $conf['cache']['type'] ? website_set('runtime', '') : cache_delete('runtime'); } register_shutdown_function('runtime_save'); ?>Wordpress HTTP 500 Error|Programmer puzzle solving
最新消息:Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)

Wordpress HTTP 500 Error

matteradmin9PV0评论

I'm getting a HTTP 500 Error on my website. Not sure what it could be. But when I refresh the page, everything works correctly. Here goes the exact error

The www.brothas.online page isn’t working

www.brothas.online is currently unable to handle this request. HTTP ERROR 500

Usually it happens when trying to login or access the back end of the website. Any help or questions would be much appreciated. Thanks

I'm getting a HTTP 500 Error on my website. Not sure what it could be. But when I refresh the page, everything works correctly. Here goes the exact error

The www.brothas.online page isn’t working

www.brothas.online is currently unable to handle this request. HTTP ERROR 500

Usually it happens when trying to login or access the back end of the website. Any help or questions would be much appreciated. Thanks

Share Improve this question edited Nov 27, 2016 at 5:37 fuxia 107k39 gold badges255 silver badges461 bronze badges asked Nov 27, 2016 at 1:41 gshustlegshustle 211 silver badge7 bronze badges 1
  • in your wordpress root folder find file wp-config.php in that file make define('WP_DEBUG',true); and check what is the error – GKS Commented Nov 27, 2016 at 3:29
Add a comment  | 

2 Answers 2

Reset to default 0

You've got an SSL certificate on the site.

So start by telling people to go to https://brothas.online instead of the link above ;)

More importantly:

Second go 'Settings' -> 'General' and set both 'WordPress Address (URL)' and 'Site Address (URL)' to 'https://brothas.online'

Then go to 'Settings' -> 'Permalinks' and save you settings again.

This should fix the redirect error.

If those steps don't fix it, you may have an issue with your .htaccess file. Rename it and save your Permalinks again.

Here are a few popular articles for more in-dept support:

https://www.elegantthemes/blog/tips-tricks/how-to-fix-the-500-internal-server-error-on-your-wordpress-website

http://www.wpbeginner/wp-tutorials/how-to-fix-the-internal-server-error-in-wordpress/

I encourage you to try my tricks before going down the rabit hole.

Thanks I appreciate your response. I actually had both 'WordPress Address (URL)' and ' Site Address (URL)' saved as https://brothas.online . Tripled checked. Although it did not really start happening until I did get my SSL Certificate installed. Renamed the .htaccess file on FTP. Then went into 'Settings' -> 'Permalinks' and clicked saved. Got a error from a plugin I used (Really Simple SSL) the error was "Your .htaccess does not contain the Really Simple SSL redirect to https, and could not be written, so a javascript redirect is currently added. For SEO purposes it is advisable to use .htaccess redirects. Set the .htaccess file to writable and visit the settings page to write it again, or copy the code lines from the settings page."

Deactivated the plugin Really Simple SSL, which removed the error and since I renamed the .htaccess file and went to 'Settings' -> 'Permalinks' and saved it looks like it fixed the issue. Thank you so much. Been trying to figure this issue out for the longest.

Articles related to this article

Post a comment

comment list (0)

  1. No comments so far