Update Problem

Cr8t1ve

Verified User
Joined
Aug 29, 2007
Messages
5
Hi... I updated my server with the custombuild script and everything seemed fine... however, I am now getting a "hey it worked! apache" page instead the the proper websites...

Anyone have any ideas on how to fix?
 
Check /etc/httpd/conf/extra/httpd-vhosts.conf if it has the right IP addresses (used not for your sites, but for hostname). After the changes restart apache.
 
I checked and it has local and outside ip addresses.... the outside one was incorrect and I changed them... I restarted httpd and I still get the "hey it worked" page...

Any other ideas?
 
If you want - I can take a look at your server and say where is the problem. PM me with your server details.
 
I get lost when I see posts referring to extra/httpd-vhosts.conf; my systems don't have the extra directory or the file.

I still use customapache. Is this something only in custombuild? If so, what does it do, why is it different, and what are the advantages?

Thanks.

Jeff
 
jlasman, all the config files are listed here:
http://files.directadmin.com/services/custombuild/beta/custombuild/configure/ap2/conf/

For apache 1.3: http://files.directadmin.com/services/custombuild/beta/custombuild/configure/ap1/conf/

extra/httpd-vhosts.conf contains:
Code:
#
# Virtual Hosts
#
# If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
#
# Please see the documentation at 
# <URL:http://httpd.apache.org/docs/2.2/vhosts/>
# for further details before you try to setup virtual hosts.
#
# You may use the command line option '-S' to verify your virtual host
# configuration.

##########################################################
# Use name-based virtual hosting.                        #
# All NameVirtualHost lines are in this file             #
# Don't remove this line or apache will generate errors. #
##########################################################
Include /etc/httpd/conf/ips.conf

#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for all requests that do not
# match a ServerName or ServerAlias in any <VirtualHost> block.
#
<VirtualHost |IP|:80>
    ServerAdmin webmaster@localhost
    AliasMatch ^/~([^/]+)(/.*)* /home/$1/public_html$2
    DocumentRoot /var/www/html
    ServerName localhost"
    ScriptAlias /cgi-bin/ /var/www/cgi-bin/"
    CustomLog /var/log/httpd/homedir.log homedir
</VirtualHost>

<VirtualHost |IP|:443>
    ServerAdmin webmaster@localhost
    AliasMatch ^/~([^/]+)(/.*)* "/home/$1/public_html$2"
    DocumentRoot /var/www/html
    ServerName localhost
    ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"
    CustomLog /var/log/httpd/homedir.log homedir

    SSLEngine on
    SSLCertificateFile /etc/httpd/conf/ssl.crt/server.crt
    SSLCertificateKeyFile /etc/httpd/conf/ssl.key/server.key
</VirtualHost>
 
jlasman said:
I get lost when I see posts referring to extra/httpd-vhosts.conf; my systems don't have the extra directory or the file.

Customapache includes it in /etc/httpd/conf/httpd.conf file.

jlasman said:
I still use customapache. Is this something only in custombuild? If so, what does it do, why is it different, and what are the advantages?
Yes, only custombuild uses httpd-vhosts.conf file. It's used to set-up the main IP for /var/www/html. Why is it different? It's not different, just seperated from the httpd.conf file (for this reason any 3rd party plugin or custombuild (maybe in the future) can rewrite this file and not the whole httpd.conf).
 
Back
Top