Websites not working - internal server error

12 posts / 0 new
Last post
#1 Mon, 01/14/2013 - 09:19

Websites not working - internal server error

I'm having problems getting websites to work - getting a 500 internal server error.

I'm running the latest Virtualmin on an Amazon Linux server. Install went ok but can't get past this issue.

I'm guessing it's something to do with the Apache virtual server configuration though checking in Webmin it appears to be ok;

default server - any address any port - server name set to domain name used for Virtualmin - doc root ok virtual server - any address port 443 - as above - doc root ok virtual server - private IP address of server port 80 - server name correct - doc root ok

No errors in the Apache log.

I thought that everything was being mapped to the default server but this doesn't appear to be the case as I uploaded a file to it's www root and got the same error.

Any ideas?

Mon, 01/14/2013 - 10:22


Anytime Apache generates a 500 error, it should always explain the error message in the Apache logs.

Which logs were you looking at -- were those the ones in the Virtual Server home directory, $HOME/logs/error_log?


Mon, 01/14/2013 - 14:16

Checked the log files in /var/log/httpd/.

Nothing in the access or error log.

Should I be looking somewhere else?

From the server domain I get a response on port 443 and (obviously) port 10000, but not on port 80 - that gives a 500 internal server error as well.

Mon, 01/14/2013 - 15:27


You'd want to take a peek at the logfile I mentioned above, $HOME/logs/error_log. That's the domain's logfile, which would contain any errors for that domain.

The logs in /var/log/httpd/ wouldn't actually show those, and would contain system errors that weren't related to individual domains.

Let us know what errors you see in $HOME/logs/error_log, and we can assist in deciphering those.


Fri, 06/24/2016 - 17:53 (Reply to #4)

Is 3 years too long too?

I was not able to open those directories but I did find the file in /var/logs/virtualmin. htaccess was the culprit. But my question here is why cant I view the error directory. ownership is correct and perm is 777

Mon, 01/14/2013 - 15:48

Had a look at the log file. Looks like the request is getting through, not sure what the error means though; - - [13/Jan/2013:23:12:58 +0000] "GET /index.php HTTP/1.1" 500 534 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17"

Same error response for all requests. No other messages either.

Mon, 01/14/2013 - 16:21


That appears to be the access_log, rather than the error_log.

Could you paste in the contents of your error_log, in $HOME/logs/error_log?



Mon, 01/14/2013 - 17:36

All fixed - many thanks for the help.

Was caused by +FollowSymLinks in the (Drupal) .htaccess, changed to +SymLinksIfOwnerMatch and all good.

Should have probably said I was trying to install Drupal on the site, as it appears to be a known issue.

Also should have realised I wasn't looking at the correct log files to begin with.

Mon, 01/14/2013 - 22:20

Super, I'm glad you got that working, thanks for letting us know how you fixed it!

Fri, 02/07/2014 - 03:59

I had the same problem installing an Elgg server on Virtualmin. Thanks to this thread I managed to solve it.

In $HOME/logs/error_log:

[Thu Jan 23 20:32:37 2014] [alert] [client] /home/com/public_html/elgg/.htaccess: Option FollowSymLinks not allowed here

I changed in .htaccess:

Options +FollowSymLinks


Options +SymLinksIfOwnerMatch

This solved the problem.

Tue, 11/22/2016 - 16:56

No help.

Really, Tired, Of, Coming, To, Viirtualmin and getting no help, or trolls....

The page isn’t working is currently unable to handle this request. HTTP ERROR 500

On a new install. og the os, and v-min, restoring backups i saved................................................


Fri, 12/02/2016 - 15:50
unborn's picture

hi miker1029, on my end its working.. is working.. see the the screenshot here: here

Configuring/troubleshooting Debian servers is always great fun

Topic locked