Question

My new Website doesn't work Error 500 Help please!

Hi,

I have set up many websites on my server however when setting up a new website www.shakirart.co.uk it does not seem to work, when I go into the browser I get an error 500 I have checked all the settings and it is pointing to the right place. I currently have quite a few websites already active on the same server these are:

www.coffeeinnleyton.co.uk www.fatinii.co.uk

and a few others.

Any help will be appreciated have been trying for ages but I can’t see to find the problem.

Thanks in advance for your help.

Regards, Muna

Subscribe
Share

Thanks so much for your help as you can probably tell my attention to detail suck, in one of the configuration files I had forgot to add a ; and hence was getting a syntax error.

@Muntansir - Looks like the configuration is parsed OK (from the first command output “Syntax OK”). However, proper cutting and pasting for the second command should have gotten better results. The command was

sudo apachectl -t -D DUMP_VHOSTS

Note the dash or minus character in front of the D parameter.

muna@Private-Server-Basic:~$ muna@Private-Server-Basic:~$ sudo apachectl -t AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1. Set the ‘ServerName’ directive globally to suppress this message Syntax OK muna@Private-Server-Basic:~$ sudo apachectl -t _D DUMP_VHOSTS Usage: /usr/sbin/apache2 [-D name] [-d directory] [-f file] [-C “directive”] [-c “directive”] [-k start|restart|graceful|graceful-stop|stop] [-v] [-V] [-h] [-l] [-L] [-t] [-T] [-S] [-X] Options: -D name : define a name for use in <IfDefine name> directives -d directory : specify an alternate initial ServerRoot -f file : specify an alternate ServerConfigFile -C “directive” : process directive before reading config files -c “directive” : process directive after reading config files -e level : show startup errors of level (see LogLevel) -E file : log startup errors to file -v : show version number -V : show compile settings -h : list available command line options (this page) -l : list compiled in modules -L : list available configuration directives -t -D DUMP_VHOSTS : show parsed vhost settings -t -D DUMP_RUN_CFG : show parsed run settings -S : a synonym for -t -D DUMP_VHOSTS -D DUMP_RUN_CFG -t -D DUMP_MODULES : show all loaded modules -M : a synonym for -t -D DUMP_MODULES -t : run syntax check for config files -T : start without DocumentRoot(s) check -X : debug mode (only one worker, do not detach) Action ‘-t _D DUMP_VHOSTS’ failed.

@Muntansir - Let’s try again, but with -t instead as a parameter to test the configuration files

sudo apachectl -t
## followed by
sudo apachectl -t -D DUMP_VHOSTS

Usage: apache2 [-D name] [-d directory] [-f file] [-C “directive”] [-c “directive”] [-k start|restart|graceful|graceful-stop|stop] [-v] [-V] [-h] [-l] [-L] [-t] [-T] [-S] [-X] Options: -D name : define a name for use in <IfDefine name> directives -d directory : specify an alternate initial ServerRoot -f file : specify an alternate ServerConfigFile -C “directive” : process directive before reading config files -c “directive” : process directive after reading config files -e level : show startup errors of level (see LogLevel) -E file : log startup errors to file -v : show version number -V : show compile settings -h : list available command line options (this page) -l : list compiled in modules -L : list available configuration directives -t -D DUMP_VHOSTS : show parsed vhost settings -t -D DUMP_RUN_CFG : show parsed run settings -S : a synonym for -t -D DUMP_VHOSTS -D DUMP_RUN_CFG -t -D DUMP_MODULES : show all loaded modules -M : a synonym for -t -D DUMP_MODULES -t : run syntax check for config files -T : start without DocumentRoot(s) check -X : debug mode (only one worker, do not detach)

What’s the output to the following command

sudo apachectl configtest

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

It would appear you were able to get your sites up and running, yea?

Check the issue on your server log, I thought your website have some coding error in your script. Just find and fix the problem.

This comment has been deleted