Well, issue one of those commands to learn more!
Also look at
/var/log/apache2/error.log
The configuration can be
syntactically correct –*which is all that
configtest looks for – but incorrect with regards to its content.
You should
also be aware that some SSL problems will cause the
sudo service apache2 start command to succeed, but Apache will thereafter immediately stop.
Probably the most common problem is some kind of mismatch between the domain-name of the
<VirtualHost> and the information that is actually contained in the certificate.
Mattias Gerniar wrote a very nice write-up on the subject of how to retrieve and interpret certificate information in
this post on his blog.