How to install DirectAdmin and launch your first site

A successful DirectAdmin installation should end with a working test website and a recoverable backup, not just a panel login. Use a separate server when migrating an existing site.

1. Prepare the server

This example uses a clean Debian 12 server with root access and a static IPv4 address. The published baseline includes 4 GB RAM and 4 GB swap; allocate additional storage for content and backups. Confirm your license is active and verified. Check the current system requirements before choosing the image.

Record the starting state:

bashcat /etc/os-release
hostname -f
free -h
df -h /

Do not run the installer over another control panel. If you find unexpected services or little free disk space, resolve that before continuing.

2. Set a hostname

Choose a dedicated name such as panel.example.com and point its A record at the server. Replace this example with your own domain:

bashsudo -i
apt update
apt upgrade -y
apt install -y curl ca-certificates
hostnamectl set-hostname panel.example.com

Reboot during your maintenance window if a kernel update requires it, then reconnect. Keep the provider console available as a recovery path.

3. Install DirectAdmin

From the root shell:

bashcurl -fsSL https://download.directadmin.com/setup.sh -o /root/directadmin-setup.sh
sh /root/directadmin-setup.sh

The official installer may print a browser setup URL. Restrict that temporary port to your own IP and keep the URL secret. Enter your license in the wizard and securely save the resulting administrator credentials.

4. Access the panel and separate accounts

The panel uses port 2222. If HTTPS is not ready, reach the HTTP interface through an SSH tunnel from your computer:

bashssh -N -L 2222:127.0.0.1:2222 root@SERVER_IP

Open http://127.0.0.1:2222 and configure the hostname certificate before switching to direct HTTPS access.

Create a separate user for the first website. Admin handles global settings, Reseller manages customer accounts, and User manages a site. The first steps documentation explains these roles and hostname TLS.

5. Verify the website

Change records at the authoritative DNS provider. Creating a zone inside the panel does not change the public delegation. An AAAA record must also point to working IPv6. Request a site certificate, then check:

bashcurl -I https://site.example.com

If the panel is unreachable, inspect the listener and provider firewall before reinstalling. If another website appears, compare the domain definition and DNS target. Failed certificate issuance calls for DNS and validation checks, not disabling certificate verification.

6. Prove recovery works

Create a test file and database, export the account, and restore it into a separate test account. Keep another copy off the server. Follow the backup strategy for retention and the reseller guide when adding customers.