Drupal Error 500 With A Correct Server Configuration in VirtualMin

This past week I migrated some sites that were originally on their own server to a cloud server running VirtualMin. After migrating the sites, everything seemed to be in place including the MySQL database, files, DNS, etc. However, I kept getting a 500 Internal Server Error when loading the site. To fix this, I had to change options in the .htaccess file for both the main site and the files directory (sites/default/files): Change Options +FollowSymLinks to # Options +FollowSymLinks Options +SymLinksIfOwnerMatch
Share this


Drupal in the Cloud, Part 3: Installing Virtualmin

Let me preface this section with a caveat: you do not need Virtualmin for Drupal to work. Drupal will work just fine without Virtualmin, provided it gets the three things it does need: Apache, MySQL, and PHP.

For those at home taking notes, this is typically called a LAMP setup- Linux, Apache, MySQL, PHP. LAMP. Get it? Cool, let's continue.

What Virtualmin does is provide an easy interface to manage your server, which is an absolute godsend for those who hate doing things by command line.

There are three things we need to get Virtualmin up and running:

  1. Be on a supported system (CentOS, Debian, Ubuntu LTS, etc.)
  2. Change the hostname to what its final hostname will be
  3. Run the install script

The first requirement is done, provided you have been doing things according to the tutorial.

The second requirement is fairly easy:

Share this


Subscribe to RSS - virtualmin