|You can switch DirectAdmin to use SSL instead of plain text. -> https instead of http on port 2222.|
Note that this is for the DirectAdmin connection on port 2222, *not* for apache.
If you're tryting to setup a certificate for your domain through apache, use this guide.
Creating a Self-Signed Certificate
If you do not have your own certificates, you'll need to create your own:
/usr/bin/openssl req -x509 -sha256 -newkey rsa:4096 -keyout /usr/local/directadmin/conf/cakey.pem -out /usr/local/directadmin/conf/cacert.pem -days 9000 -nodes
chown diradmin:diradmin /usr/local/directadmin/conf/cakey.pem
Installing a Purchased Certificate
If you already have your own certificate and key, then paste them into the following files:
Edit the /usr/local/directadmin/conf/directadmin.conf and set SSL=1 (default is 0). This tells DA to load the certificate and key and to use an SSL connection.
Ensure your directadmin.conf has the values set:
DirectAdmin needs to be restarted after any changes to the directadmin.conf.
If you also have a CA Root Certificate, this can be specified by adding:
carootcert=/usr/local/directadmin/conf/carootcert.peminto the /usr/local/directadmin/conf/directadmin.conf file (won't exist by default) and by pasting the contents of the caroot cert into that file.
Using the free "Let's Encrypt" tool to secure 2222
As of DA 1.50.0, we've added a new feature that allows you to make use of LetsEncrypt, a tool offering free basic SSL certificates.
We've written the script in such a manner that you can also setup SSL for your hostname and all services in one simple command for your hostname:
NOTE The hostname value, eg: your.hostname.com must match the "servername" value set in the directadmin.conf, or it will not be in hostname mode, but User domain mode instead.
You must then turn on SSL in DA and tell DA to use the carootcert, as well as force the hostname for SSL:
Note, as of 1.30.2, you can set the value of the SSL redirect should a User connect to an https connection with plaintext http.
For 1.33.0, you can force DA to redirect to a specific hostname if you wish the host to match the cert installed:
However, if they connect to https on a different host, they'll first get the ssl warning (since ssl is established before the host is passed), then they'll be redirected to the correct host, where the error would not appear (assuming you've got a valid cert setup)
As of 1.33.3, you can enable a ssl cipher to force SSLv3, and disable SSLv2:
DA 1.48.4 will support HTTP Strict Transport Security (HSTS):
But we recommend you enable both the force_hostname as well as the ssl_redirect_host with a non-apache-used host, like dabox.domain.com, and not www.domain.com, as HSTS doesn't respect only port 2222, it would bleed over to apache, changing http://www.domain.com (80) connections to use https://www.domain.com (443), even though the header was only set on port 2222.
|How to manually create a certificate request (CSR)|
© 2003 JBMC Software, Suite 173 3-11 Bellerose Drive, St Albert, AB T8N 1P7 Canada. Mon-Fri 9AM-5PM MST