Can't get GUI to work
I know this is a really general issue but I need help and I don't even have a clue where to start looking for what is wrong. After setting everything up (Piler 0.1.23) I get
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Apache/2.2.22 (Debian) Server at 10.11.2.40 Port 80
I've changed the default for the piler configuration file that Piler ships for Apache but I changed some stuff that Apache needed me to include:
#### IMPORTANT!!!
####
#### Fix the hostname
####
<VirtualHost *:80>
ServerName mailpiler-test.${MYDOMAIN}.com
ServerAdmin webmaster@localhost
DocumentRoot /var/www/mailpiler
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
<Directory /var/www/mailpiler>
Order allow,deny
Allow from all
AllowOverride all
</Directory>
ErrorLog ${APACHE_LOG_DIR}/mailpiler-test.${MYDOMAIN}-error_log
CustomLog ${APACHE_LOG_DIR}/mailpiler-test.${MYDOMAIN}-access_log common
Include /etc/phpmyadmin/apache.conf
</VirtualHost>
In which files should I be looking for miss configured files?
Than you!
EMILIO!
Comments (3)
-
repo owner -
Thanks for the quick answer!
Oops! I get this kind of error
[Fri Aug 16 09:55:48 2013] [alert] [client *.*.*.*] /var/www/mailpiler/.htaccess: Invalid command 'RewriteEngine', perhaps misspelled or defined by a module not included in the server configuration
all I needed to do was to enable rewrite module
a2enmod rewrite service apache2 restart
and now finally, after 10 days of ripping my hair off my head because I couldn't making work, it's working!!!!
Thank you very much for your help. Stay tune, now I need to configure everything else :P
EMILIO!
PS: You can change to SOLVED, accidentally I created the issue anonymously.
-
repo owner - changed status to resolved
OK, I'll stay tuned :-)
- Log in to comment
Check the apache error log as the error message suggest. I think it might be an apache configuration issue.