Note: If you want the latest version of php and apache, it’s recommended you use custombuild:
http://files.directadmin.com/services/custombuild/1.1
The following guide is only to be used if if you still want to use the old apache versions… basically, only if you still need FrontPage.

---

To update to php5, the build script will still work. All that you need to do is swap out the version, compile normally and make a few modifications to your /etc/httpd/conf/httpd.conf file.
1) download the php-5.2.4.tar.gz from php.net into your customapache directory:

cd /usr/local/directadmin/customapache
wget http://files.directadmin.com/services/customapache/php-5.2.4.tar.gz

2) change your build script for the new version:

nano build

change: PHP_VER=4.4.4
to: PHP_VER=5.2.4
3) build php normally:

./build clean
./build php n

If you’re using apache 2.x, use

./build clean
./build php_ap2 n

instead.
4) edit /etc/httpd/conf/httpd.conf
Remove any referce of:

LoadModule php4_module modules/libphp4.so

and make sure they’re replaced with:

LoadModule php5_module modules/libphp5.so

Remove any reference of:

AddModule mod_php4.c

and replace with:

AddModule mod_php5.c

5) find this piece of code:

<IfModule mod_dir.c>
DirectoryIndex index.html index.htm index.shtml index.php index.php4 index.php3 index.phtml index.cgi
</IfModule>

replace with:

<IfModule mod_dir.c>
DirectoryIndex index.html index.htm index.shtml index.php index.php4 index.php5 index.php3 index.phtml index.cgi
</IfModule>

Find this:

<IfModule mod_php4.c>
AddType application/x-httpd-php .inc .php .php4 .php3 .phtml
AddType application/x-httpd-php-source .phps
</IfModule>

(it might have AddHandler instead of AddType)
replace with:

<IfModule mod_php5.c>
AddHandler application/x-httpd-php .inc .php .php5 .php4 .php3 .phtml
AddHandler application/x-httpd-php-source .phps
</IfModule>

Then restart apache.
If you get the following error while compiling php:

checking whether to enable LIBXML support… yes
checking libxml2 install dir… no
checking for xml2-config path…
configure: error: xml2-config not found. Please check your libxml2
installation.
*** There was an error while trying to configure php. Check the configure.php file

Then edit the configure.php file (or configure.php_ap2 if you’re using apache 2), and change:

–with-xml \

to:

–disable-libxml \
–disable-dom \
–disable-xml \
–disable-simplexml \
–disable-xmlreader \
–disable-xmlwriter \

or else install the missing rpms/packages for xml. (libxml2-dev and libxml2-utils on debian). Redhats:

yum -y install libxml2-devel libxslt-devel

FreeBSD:

pkg_add -r libxml2
pkg_add -r libxslt

On debian systems if using apt-get to install libxml2-dev and libxml2-utils doesn’t work, then install from source:

wget http://files.directadmin.com/services/customapache/libxml2-2.6.30.tar.gz
tar xvzf libxml2-2.6.30.tar.gz
cd libxml2-2.6.30
./configure
make && make install

then recompile php as usual.

Incoming search terms:

php-5 2 4 tar gz

Note this is an old guide. It was for apache 1.3 with customapache. The current boot script we provide shouldn’t have this issue.
If apache is not completely shutting down, consider trying graceful restarts (see related link below) and also ensure your system is updated such that you don’t have any outdated php scripts on the server.

---

[crit] (98)Address already in use: make_sock: could not bind to port 8090
or
[crit] (98)Address already in use: make_sock: could not bind to port 443
or
[crit] (98)Address already in use: make_sock: could not bind to port 80
If you see this error in your /var/log/httpd/error_log, it would mean that apache isn’t shutting down completely before trying to restart. This means that the new process won’t be able to bind to the given ports because they’re still being used by the old copy of apache that wasn’t completely shut down.
To solve this, use a different boot script that will wait for all apache processes to stop before starting the new one:

cd /usr/local/directadmin/customapache
rm -f httpd*
./build update

Once you have the new scripts downloaded, you need to install them:
RedHat:

cp httpd /etc/init.d/httpd
chmod 755 /etc/init.d/httpd
chkconfig httpd reset

FreeBSD:

cp httpd_freebsd /usr/local/etc/rc.d/httpd
chmod 755 /usr/local/etc/rc.d/httpd

Incoming search terms:

(98)address already in use: make_sock: could not bind to address [::]:80,(98)address already in use: make_sock: could not bind to address [::]:443,(98)Address already in use: make_sock: could not bind to address [::]:8888,could not bind to address 80,error: system error 98: address already in use,port 80 already in use,problem with apache 2 make_sock windows 7,when restart apache2 error address already in use

If you wish to change the setup of the VirtualHosts for all domains, you can do so by creating your own custom templates.

cd /usr/local/directadmin/data/templates
cp virtual_host*.conf custom
cd custom

Once you’ve copied the 4 VirtualHost files (or just the ones you want) to the custom directory, you can then edit the new files you’ve just copied. DirectAdmin will always check for the custom file before going to the default ones. Failure to copy the virtual_host*.conf files to the custom directory before modifying them will result in a loss of all changes when DirectAdmin updates itself (the files are overwritten). Note that there are actually 8 virtual_host files, but you only need to worry about the 4 that apply to you. The files with the 2 in them are for apache 2.x. The ones without the 2 in them are for apache 1.3.
Inside the virtual_host*.conf files, you’ll find code that is similar to httpd.conf code, but contains what are known as tokens. These tokens are what will be replaces with specific user data for each domain created.

Available tokens

DOMAIN
the name of the domain. eg: domain.com

IP
the IP address associated with that domain. eg: 192.168.3.4

HOME
The users home directory. eg: /home/gary

ADMIN
The email address of the server admin. webmaster@domain.com

HOSTNAME
The hostname of the server. eg: server.domain.com

SAFE_MODE
ON or OFF if php safe_mode is enabled or not

PHP
ON or OFF if php is enabled or not

CGI
The whole httpd.conf line used to add the Script-Alias

HANDLERS
httpd.conf code holding all apache handlers

MIMETYPE
httpd.conf code holding all apache mime types

USER
the username

GROUP
the users group name (99% of the time, it’s the same as the USER)

DOCROOT
The DocumentRoot of the VirtualHost. This is the path that apache will use to access the data when the ServerName (domain.com) is requested

SUB
for the virtual_host_*sub.conf file, the subdomain name. eg: sub

CUSTOM
custom httpd.conf code to be inserted if the domain.com.cust_httpd file exists. (See Adding custom httpd.conf code the VirtualHost of one domain)

CAROOT
The whole httpd.conf line used to load in the SSLCACertificateFile directive

CERT
The path of the certificate to be used for the domain

KEY
The path of the certificate to be used for the domain

The top of the templates should contain |?CGI=…| and |?DOCROOT=…|. These lines are where the data for the CGI and DOCROOT tokens are set. If cgi is not enabled, this line wil be ignored and the CGI token will be empty. If the domain is suspended, the DOCROOT will be filled the the path of the suspend page. The CAROOT token will be empty unless the User has added a valid CARootCertificate through DA.
You can use tokens when assigning a value to CGI or DOCROOT, just use `TOKEN` instead of |TOKEN|.
Once you are happy with your new virtual_host*.conf files they’ll need to be used in the real httpd.conf files. You can trigger DirectAdmin to rewrite all User httpd.conf files by running:

echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue

The command will be added the the task queue which is checked once per minute, so it may be a few minutes before all httpd.conf files have been rewritten. *Note: the main /etc/httpd/conf/httpd.conf is never overwritten (unless DirectAdmin is reinstalled) so any changes you make will be safe.
Note, that you can also use if-then-else statements if you don’t want all settings to be global. Example, say you want a custom item added, only for 1 domain:

|*if DOMAIN="domain.com"|
#custom item for just this domain
|*endif|

See the if-then-else link for more info on what else you can do with this basic scripting tool.
You can also run actual scripts with database queries, etc… if you wanted using the script portion of the templates.
More info on that here: http://www.directadmin.com/features.php?id=756

Incoming search terms:

cpanel server change virtual host template,custom template cpanel virtual host,direct admin virtual host tutorial,directadmin virtual host template,ign template