使用Wamp部署Magento遇500 Internal Server Error，无法进入安装页面

Hey, sorry to hear you're stuck with this frustrating 500 error while trying to load Magento's setup page—generic solutions can miss the mark sometimes, so let's dive into targeted checks that often resolve this:

• Get the actual error details first (don't rely on the 500 page)
  Servers hide detailed errors by default for security, but you can uncover them quickly:

  • Edit your Magento root index.php: Find ini_set('display_errors', 0); and change it to 1, then add error_reporting(E_ALL); right above it. Refresh the setup page, and you'll likely see a specific error (e.g., missing PHP extension, file permission issue).
  • Check your server's error logs too—Apache's error.log or Nginx's error.log will have granular details about what's failing, like a fatal PHP error or permission denial for a specific directory.

• Fix file permissions and ownership (Magento is picky about this)
  Installation requires write access to key directories, so run these commands (replace www-data with your server's web user if different):

  # Set standard file/directory permissions
  find . -type f -exec chmod 644 {} \;
  find . -type d -exec chmod 755 {} \;
  chmod +x bin/magento
  # Assign ownership to the web server user
  chown -R www-data:www-data .
  

  If you're on shared hosting and can't use chown, double-check that var/, pub/, generated/, and app/etc/ directories are writable (most hosts let you adjust this via cPanel or FTP).

• Verify your PHP setup meets Magento's requirements
  A lot of 500 errors stem from misconfigured PHP:

  • Confirm your PHP version matches the Magento version you're installing (Magento 2.4 requires PHP 7.4, 8.1, or 8.2—older/newer versions will break things).
  • Set memory_limit in php.ini to at least 2G (installation uses more memory than a running store).
  • Ensure all required PHP extensions are enabled: intl, mbstring, soap, gd, curl, json, zip, bcmath, and sockets (for 2.4+). Create a phpinfo.php file with <?php phpinfo(); ?> to check these.

• Wipe auto-generated files and cache
  Residual cache or generated files can block the installer. Run these commands from your Magento root:

  rm -rf var/cache/* var/page_cache/* generated/code/* generated/metadata/*
  

  If you've tried installing before, delete the var/installed_version file (if it exists) to force the setup wizard to start fresh.

• Check SELinux (for CentOS/RHEL servers)
  SELinux often blocks Magento from writing files on Red Hat-based systems. Temporarily disable it to test:

  setenforce 0
  

  If the setup page loads after this, don't leave SELinux disabled—instead, configure the proper policy rules to allow Magento's file operations (focus on granting the web server write access to Magento's core directories).

内容的提问来源于stack exchange，提问作者Dragoon Shimizu