If you need to go back to apache 1.3 after installing apache 2, you’ll need to do the following: 1) Restore the old httpd.conf file: cp -f /etc/httpd/conf/httpd.conf.1.3.backup /etc/httpd/conf/httpd.conf 2) Get DirectAdmin to use the old httpd.conf files for the users. Edit the /usr/local/directadmin/conf/directadmin.conf file and change apache_ver=2.0 to apache_ver=1.3.
If you are unable to access your server via https://1.2.3.4:2222, then 1 of 3 things is likely happening: 1. DirectAdmin might not be running or 2. You have a firewall blocking port 2222. Number 2. is easy to check by simply running (only on redhat systems): /sbin/service iptables stop /sbin/chkconfig
If you need to go back to apache 1.3 after installing apache 2, you’ll need to do the following: 1) Restore the old httpd.conf file: cp -f /etc/httpd/conf/httpd.conf.1.3.backup /etc/httpd/conf/httpd.conf 2) Get DirectAdmin to use the old httpd.conf files for the users. Edit the /usr/local/directadmin/conf/directadmin.conf file and change apache_ver=2.0 to apache_ver=1.3.
Cron is the tool used to control the update frequency of the stats. You can easily change the frequency by modifying the cron job. Cron file for RedHat: /etc/cron.d/directadmin_cron Cron file for FreeBSD: /etc/crontab Edit the cron file and locate the line that looks like the following: 10 0 *
Setup SSL Certificates for Direct Admin: This step is only required if you wish to use DirectAdmin through SSL. You will also have to change set SSL=1 in the directadmin.conf file. ( /home/directadmin/directadmin.conf ) # openssl req -new -x509 -keyout /usr/local/directadmin/conf/cakey.pem.tmp -out /usr/local/directadmin/conf/cacert.pem # openssl rsa -in /usr/local/directadmin/conf/cakey.pem.tmp -out /usr/local/directadmin/conf/cakey.pem
Step 1) Do you meet the system requirements? – Clean OS install: Redhat 7.2, 7.3, 8.0, 9.0, Fedora (any version), CentOS (any version). PS :- The setup file for Redhat also works for Fedora and CentOS (any version). – At least one external IP address (NAT/LAN-based systems will NOT work).
Collectively, preinst, postinst, prerm, and postrm files are all executable scripts which Debian automatically runs before or after package installation. Along with a file named control, all of these files are part of the “control” section of a Debian archive file. The individual files are: preinst This script executes before
On a server with CPanel, you can log into the WHM and install it there. If that for some reason doesn’t work for you, you can log into the shell as root and install it via the command line. Once logged in, from any directory, type: echo “HTML::Template” | /usr/local/cpanel/whostmgr/bin/perlmod
RedHat, as well as other distributions, contain the AutoFS utility. This will allow you to mount your NAS share automatically in a directory. There are only a couple things that you need to do to have this setup correctly. First, you will need to make sure that autofs is starting
Udev provides users with a dynamic device directory containing only the files for actually present devices. It creates and removes device node files usually located in the /dev/ directory, and renames network interfaces. As part of the hotplug subsystem, udev is executed if a kernel device is added or removed
Need to change your access permissions using only the command line? Thankfully, a utility called CACLS.EXE comes standard with Windows, and can be used from the command prompt to do just that. For more information check the help documentation included with the CACLS.EXE program (cacls /?). Using the Command