Dear Wiki user, You have subscribed to a wiki page or wiki category on "Httpd Wiki" for change notification.
The "CommonMisconfigurations" page has been changed by JamieKitson. http://wiki.apache.org/httpd/CommonMisconfigurations?action=diff&rev1=7&rev2=8 -------------------------------------------------- In the case of multiple Listen directives, Apache will bind to port 80 the first time and then try to bind to port 80 a second time. This yields a nice "Could not bind to port" error on start up. This seems to happen with newbies and Debian based distros, where Debian based distros have Listen 80 defined in ports.conf. Newbies don't realize this and create another Listen 80 line in apache2.conf.<<BR>><<BR>> - Multiple !NameVirtualHost lines will yield a "!NameVirtualHost *:80 has no !VirtualHosts" warning. Apache will ignore the second directive and use the first defined !NameVirtualHost line, though. This seems to happen when one is using multiple virtual host configuration files and doesn't understand that you only need to define a particular !NameVirtualHost line once.<<BR>><<BR>> + Multiple !NameVirtualHost lines will yield a "!NameVirtualHost *:80 has no !VirtualHosts" warning. Apache will ignore the second directive and use the first defined !NameVirtualHost line, though. This seems to happen when one is using multiple virtual host configuration files and doesn't understand that you only need to define a particular !NameVirtualHost line once. As above, this can occur in the debian ports.conf file, especially after an upgrade.<<BR>><<BR>> ==== Multiple SSL name based virtual hosts on the same interface. ==== Example:
