500 Internal Server Error for IPAddress/Omeka/install/install.php

Question

OS: Windows 10Server: Putty Ubuntu 14.04.3 These were the instructions I was given to follow in setting up Omeka through my server. sudo cp .htaccess.changeme .htaccess $ sudo nano .htaccess move down to where you see this ------------- Rewrite Rules ------------- RewriteEngine on If you know mod_rewrite is enabled, but you are still getting mod_rewrite errors, uncomment the line below and replace “/” with your base directory. RewriteBase / change the line "# RewriteBase /“ so that it says “RewriteBase /Omeka” save and close the file now, go to http://[YOUR SERVER’S IP ADDRESS]/phpmyadmin/ in your web browser log in to phpmyadmin with whatever you set your login info to once you’ve logged in, click “databases" type Omeka into the box, and click “create” now, go back to your server in Putty $ sudo nano /etc/apache2/apache2.conf press control button + w ^^ that is the command to search if you correctly hit the command to search you should see this… Type “AllowOverride” into the search box and hit enter use your arrows to move down to find this part… Options Indexes FollowSymLinksAllowOverride NoneRequire all granted (edited) edit the line that says “AllowOverride None" so that it says “AllowOverride All” save and close the file $ sudo service apache2 restart now, go to your web browser and go to http://[YOUR IP ADDRESS HERE]/Omeka/install/install.php set the options to whatever you want set the ImageMagick path to /usr/bin/ I still get the 500 error when I enter my IP/Omeka/install/install.php .

Jonathan Tittle · Answer

@jz2332

To use phpMyAdmin or run the installer, you shouldn’t need an .htaccess file, so to make sure that the .htaccess file is not the cause of the error, download a copy (as a backup) and delete the current. Now refresh the page and see if the error persists.

Does the error persist?
Does a new error display? If so, what’s the error?

In either case above, are you seeing anything in your error logs? If so, copy and paste the last 10-20 lines and let’s see what the web server is logging. Since PHP should also create an error log, it’d be best to also look at the PHP error log too. The web server often will not log scripting errors, so the PHP error log is where we’d need to look to see if it’s a scripting error.

If removing the .htaccess file fixes the issue, there’s something wrong with the .htaccess file. This is one file that can be very finicky. As an example - an extra space in the configuration can (and most often does) result in one or more errors or a blank page.