DirectAdmin
How to disable SSL2.0 in apache
by admin on Jan.11, 2012, under DirectAdmin
To disable the SSL2.0 protocol (thus forcing 3.0),
for apache 1.3, find the line:
#SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
and change it to:
SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:!SSLv2:+EXP:+eNULL
Note the 2 changes: a) remove the # character at the beginning of the line, and b) change +SSLv2 to !SSLv2
For apache 2.x, do the same thing, but instead it will be in the /etc/httpd/conf/ssl.conf file, or for the new apache system, /etc/httpd/conf/extra/httpd-ssl.conf (if you have both files, just change it in both).
Error: Cannot find SSL binaries under /usr
by admin on Jan.09, 2012, under DirectAdmin
This happens with the configure script for apache cannot find the "openssl" (or "ssleay") binaries in any of
/usr/bin/openssl
/usr/sbin/openssl
/usr/apps/openssl
The usual location for "openssl" is /usr/bin/openssl
On a debian system, run
apt-get install openssl
Incoming search terms:
ssl binariesHow to forward a website to another url
by admin on Jan.06, 2012, under DirectAdmin
There are several ways to accomplish this task, but the simplest to understand is to use php.
To do this, you need to create the page that will do the forwarding. This can be any page, as long as it ends in ".php". If you are trying to redirect a domain, you’d create "index.php" inside the public_html directory.
Once you decide which page you will use, then create the file and enter the following text:
<?php
header("Location: http://whereyouwant.com/to/go.html");
?>
Where http://whereyouwant.com/to/go.html is the location that you want the page to forward to. You can use local values, ie: /page.html, or full urls as in the above example (http://..etc.)
Apache won’t start after update on FreeBSD
by admin on Jan.04, 2012, under DirectAdmin
An issue with php/apache is causing apache not to start in FreeBSD. It segfaults and core dumps, logged in the /var/log/httpd/error_log.
Try removing –with-openssl from your configure.php file and recompile php.
cd /usr/local/directadmin/customapache
vi configure.php
#remove –with-openssl from the file, save, exit.
./build clean
./build php n
Possibly a mod_perl issue. Edit the /etc/httpd/conf/httpd.conf
change:
AddModule mod_perl.c
to
#AddModule mod_perl.c
and then restart apache. If you don’t have "AddModule mod_perl.c", then don’t worry about this entry.
Remove the "LoadModule perl_module /usr/lib/apache/mod_perl.so" if you have it as well.
This won’t affect files in the cgi-bin (I’ve seen very few people actually making use of mod_perl itself).
more info:
Previous workaround for the problem is to remove thp php flags from the httpd.conf files:
cd /usr/local/directadmin/data/templates
cp virtual_host*.conf custom
cd custom
perl -pi -e ‘s/php_admin/#php_admin/’ *
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
/usr/local/directadmin/dataskq d
/usr/local/etc/rc.d/httpd restart
One user reported that installing zend solved this problem as well, so try:
cd /usr/local/directadmin/customapache
./build zend
Possibly have to downgrade zend to 2.5.7 from 2.6.2 as well as the zend binaries may not be backwards compatible.
To downgrade to apache 1.3.33 and php 4.3.11, run:
cd /usr/local/directadmin/customapache
./build clean
perl -pi -e ‘s/1.3.34/1.3.33/’ build
perl -pi -e ‘s/1.3.34/1.3.33/’ configure.apache_ssl
perl -pi -e ‘s/2.8.25/2.8.24/’ build
perl -pi -e ‘s/4.4.1/4.3.11/’ build
./build update_data
./build all d
Incoming search terms:
free bsd apache check subdomainCannot use SSH with old system accounts after Installation
by admin on Dec.27, 2011, under DirectAdmin
For all SSH accounts created with DirectAdmin, it adds the "AllowUsers" option to the /etc/ssh/sshd_config file. When DirectAdmin is installed, it will add "root" and "admin" to that file under the AllowUsers option. Any other users who have had SSH account on the system will also require to be added to that file in order to access the server via SSH.
*IMPORTANT: For systems who require the use of "su" to access the root account, but do not use "admin" to do it, that usename *must* be added to the /etc/ssh/sshd_config before logging out or else they will not be able to login and and turn won’t be able to su to root any longer. This isn’t as relevant for RedHat systems, because the default is to enable root login, but for most FreeBSD systems, su is required, and the starting use *must* be in the wheel group, which a newly created "admin" would not be.
