Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialAaron Smith
19,091 PointsTrying to move from live to local server, but getting a "500 Internal Server Error"
So I'm trying to do the reverse of this video and copy a client's live site onto my local server in order to test a new plugin. However, when I try to navigate to the page in Chrome, I get a blank page, and Developer Tools shows a 500 error.
Here is what I've already done (in order):
1) Exported MySQL database as a zip file, and imported it into a database with the same name on my local server
2) FTP'd the entire Wordpress directory to MAMP's root folder (with the exception of two folders consisting of only audio content, because they total about 8 GB, but I don't think that should matter...)
3) Used SQL to update links in the wp_options, wp_posts, and wp_postmeta tables to point to the local server
4) Updated wp-config.php and set DB_HOST to "localhost", DB_USER to "root", and DB_PASSWORD to "root". Also added defines for WP_HOME and WP_SITEURL and set them to http://localhost/my-folder-name
I'm not sure what to try because I'm pretty new to this. What am I missing? I appreciate any help!
2 Answers
miguelcastro2
Courses Plus Student 6,573 Points500 Error is a general application error. In order to determine what is the root cause you need to check the server log files. For MAMP the log files are stored in All log files are stored in: /Applications/MAMP/logs/.
Aaron Smith
19,091 PointsThanks for the tip, Miguel. Looking through the logs I determined it was a plugin that was causing the error.