Install DirectAdmin on a newly provisioned, supported Linux VPS—not on a server that already has a control panel or hosting stack. Verify the license, connect as root over SSH, run the official setup.sh installer, then open the panel on port 2222.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
What DirectAdmin installation on a VPS requires
DirectAdmin is a server control panel that installs and configures its own hosting stack, including web, database, FTP, PHP and mail services. The safest installation is therefore a clean operating-system deployment dedicated to DirectAdmin. The installer is not intended to retrofit an existing production server with another control panel or a collection of preinstalled services.
As an Amazon Associate I earn from qualifying purchases.
DirectAdmin’s installation guidance says, “Make sure DirectAdmin is being installed on a clean server that runs one of the supported Linux distributions.” Treat that as a prerequisite rather than a suggestion. A clean image also makes it possible to rebuild the VPS if an OS, architecture or network-interface mismatch is discovered during setup.
Minimum technical requirements
| Requirement | What to provision or verify | Why it matters |
|---|---|---|
| Memory | At least 4 GB RAM | The documented minimum for the panel and its services. |
| Swap | At least 4 GB swap | DirectAdmin lists swap separately from physical memory; confirm it exists on the VPS. |
| Disk | At least 2 GB free after Linux is installed | This is free space for the DirectAdmin installation, not the provider’s advertised raw disk size. |
| CPU architecture | amd64/x86-64 or arm64 | The installed OS and the DirectAdmin license must target the same supported architecture. |
| Operating system | A currently supported RHEL-compatible distribution, Debian or Ubuntu release | Exact releases and end-of-life dates change, so check DirectAdmin’s current OS policy before ordering the image. |
| Privileges | Root SSH access | The installer must write system files, create services and configure networking. |
| Network | At least one static IPv4 address | The panel and hosted services need a stable address; some DNS-control arrangements require two IP addresses. |
| Quotas | Kernel and filesystem quota support | Quota support is part of DirectAdmin’s documented server requirements and may depend on the VPS platform. |
These figures are vendor requirements, not a performance benchmark. A busy multi-user server, large mail installation or sizeable application portfolio may need substantially more resources; the documented minimum only establishes a starting point for installation.
Choose and provision the VPS image
Select a supported Linux release
Choose a current image from one of the supported families: a RHEL-compatible distribution such as AlmaLinux or Rocky Linux, Debian, or Ubuntu. Do not assume that every version offered by a VPS company is supported. Distribution support and end-of-life dates change, and DirectAdmin can restrict installation to particular releases.
Before creating the server, compare the image’s exact release with DirectAdmin’s OS policy. Record the release name and version; you will use that information if the installer reports an architecture, loader or license mismatch. Select amd64/x86-64 or arm64 hardware according to the image and the architecture covered by your license.
Start with a clean operating system
Deploy the provider’s minimal or clean OS image. Do not install another control panel first. Do not preinstall Apache, PHP, MySQL, FTP daemons, mail components or similar hosting services unless DirectAdmin’s documentation for your chosen path explicitly requires them. DirectAdmin installs and manages those components itself, so an existing stack can create port conflicts, duplicate configuration files and incompatible package versions.
Confirm VPS platform features
Check that the VPS exposes a real root account or allows you to obtain a root shell, provides SSH access, assigns a static IPv4 address and supports the quota behavior required by your chosen filesystem and virtualization model. Ask how the provider exposes network interfaces: a conventional device such as eth0, an alias such as eth0:1, a virtual device such as venet0:0, or another name. This matters if the installer cannot automatically associate the server address with an interface.
Also verify how snapshots and backups work. A snapshot made before installation is useful for a clean rollback, while a backup made after configuration protects the completed panel. Backup retention, restore speed and whether the provider backs up attached volumes are provider-specific; DirectAdmin’s requirements do not establish a standard policy.
Pre-install checks from the root shell
Once the VPS is provisioned, connect over SSH using the server’s static address:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →ssh [email protected]If you receive a non-root shell, obtain a root shell before running the installer. The following checks expose the values that most often cause a failed installation:
whoami
uname -m
cat /etc/os-release
free -h
swapon --show
df -h
ip awhoamishould identify the root account.uname -mshows the running architecture; compare it with the license and OS image./etc/os-releaseidentifies the exact distribution and release.free -handswapon --showlet you confirm physical memory and configured swap.df -hshows whether the root filesystem still has the required free space after the OS image is installed.ip alists the complete interface and address names that may be needed later.
Do not continue if the image is not the release you selected, the license targets another OS or architecture, SSH access is incomplete, or the VPS lacks the required address and quota support. Rebuilding a new clean VPS is usually safer than trying to remove a partially installed control panel from a server that already contains applications.
Verify the DirectAdmin license before installing
Sign in to your DirectAdmin client account and confirm that the license status is both Active and Verified. An unverified or inactive license can prevent the installer from completing even when the VPS itself is correctly configured.
Check that the license’s operating-system and architecture selection matches the image you actually deployed. Keep the license key available if you plan to perform the installation entirely from the command line. If you use the browser-assisted flow, the script will provide a URL for the remaining setup steps.
Free tools Windows power users keep installed
One-click scans. No signup required.
Run the DirectAdmin installer
Browser-assisted installation
From the root shell on the clean VPS, run:
sh <(curl -fsSL https://download.directadmin.com/setup.sh)The command downloads and executes DirectAdmin’s setup script. The script performs the initial setup and prints a URL for continuing in a browser. Copy that URL exactly, including the protocol, address and port, and open it from your workstation. Follow the prompts to finish the initial configuration.
Keep the SSH session open while the installer runs and watch for errors rather than assuming that a returned shell means success. Installation time depends on the VPS CPU, disk and package mirrors. When the process completes, record the administrator username, generated password and login URL before closing the session.
Command-line installation with a license key
For an unattended or terminal-based start, pass the license key as the argument to the same script:
sh <(curl -fsSL https://download.directadmin.com/setup.sh) 'YOUR_LICENSE_KEY'The command-line path uses DirectAdmin’s default configuration unless you define options in advance. Protect the shell history and any automation logs that might contain the key. If your environment records commands centrally, use the provider’s or DirectAdmin’s documented secret-handling method rather than leaving the key in an accessible transcript.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What the installer changes
The setup process installs DirectAdmin and the services it manages, configures its service files and prepares the panel for web access. Because those changes are system-wide, do not run the script inside an existing hosting stack or from a non-root account. If the process stops with a package, network, license or architecture error, preserve the error text; it identifies whether the correction belongs on the VPS, in the license account or in the selected OS image.
Find the credentials and open the panel
At completion, the installer prints the administrator credentials and a login address. DirectAdmin also saves the credentials in:
/usr/local/directadmin/conf/setup.txtRead that file from the root shell if the terminal output has scrolled away, then store the credentials in a secure password manager and restrict access to the file. Do not publish the file contents in a ticket, chat transcript or public repository.
Open the address shown by the installer. The conventional HTTP form is:
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallhttp://server.ip.address:2222The installer may instead provide an HTTPS URL. Use the displayed protocol and hostname rather than changing it arbitrarily. Port 2222 is DirectAdmin’s panel port; if a provider firewall or VPS security group blocks it, allow the port according to that platform’s controls before testing again.
If the page does not load, first confirm that the VPS is running, the address is the one assigned to the server and the network policy permits the panel port. Then check DirectAdmin’s service state and logs from SSH. A browser timeout indicates a network path or firewall problem more often than an incorrect password, while a visible login page confirms that the web service is reachable.
Prepare repeatable or customized installations
DirectAdmin supports unattended configuration through environment variables and configuration files. Define variables before invoking setup.sh when the same values should be applied consistently across servers.
| Variable | Purpose |
|---|---|
DA_HOSTNAME |
Sets the server hostname used during setup. |
DA_EMAIL |
Sets the administrative email address. |
DA_NS1 |
Sets the first nameserver value. |
DA_NS2 |
Sets the second nameserver value. |
DA_CHANNEL |
Selects the DirectAdmin download channel. |
DA_OS_SLUG |
Targets a platform-specific OS build. |
For example, an automation system can export the values, verify that they are non-empty, and then call the installer in the same root session. Keep secrets out of source control and mask them in CI or provisioning logs.
For deeper CustomBuild configuration, create the files before running setup.sh:
/usr/local/directadmin/custombuild/options.conf
/usr/local/directadmin/conf/directadmin.confoptions.conf can define web-server, PHP, download and related CustomBuild settings. directadmin.conf holds DirectAdmin configuration values, including network-interface settings. Ensure the directories exist on the clean image and validate the syntax expected by the DirectAdmin release you are installing; a malformed option can make an otherwise valid installation fail.
Fix VPS network-interface detection problems
Some VPS platforms present the server address on an interface name that DirectAdmin does not select automatically. The symptom is an installer or service message saying that it cannot identify the interface that owns the server IP, or a panel configuration that binds to the wrong device.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Run
ip aas root. - Find the interface containing the VPS’s static IPv4 address.
- Copy the complete device name exactly, including any alias suffix.
- Set that value in
/usr/local/directadmin/conf/directadmin.conf.
The setting has this form:
ethernet_dev=eth0:1The correct value may instead be venet0:0, eth1 or another name shown by ip a. Do not substitute a generic name from another VPS. Save the file, then restart the DirectAdmin service or rerun the installation procedure specified by the troubleshooting guidance. An incorrect interface value can make the panel appear installed while leaving it unreachable on the assigned address.
Resolve architecture and loader errors
If the DirectAdmin binary fails with an architecture or loader error, compare three values: the hardware architecture reported by uname -m, the OS release in /etc/os-release and the operating-system selection attached to the DirectAdmin license. They must describe the same platform.
Do not try to repair a mismatched binary by copying libraries from another distribution. Verify the license and image selection, then rerun setup.sh on a new clean installation as directed by DirectAdmin’s troubleshooting documentation. A rebuild removes packages and configuration left by the failed attempt and gives the installer a consistent base.
Useful commands after installation
The main DirectAdmin binary is located at:
/usr/local/directadmin/directadminDirectAdmin also provides a /usr/bin/da symlink for common administration commands:
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteda login-url
da version
da license
da updateda login-urlprints the current panel login URL.da versionreports the installed DirectAdmin version.da licensedisplays license information available to the server.da updatestarts the supported DirectAdmin update process.
If the service is stopped, start it with:
systemctl start directadminUse these commands from a root shell while troubleshooting or documenting the server. Keep a record of the installed version, selected OS release, hostname and network-interface value so a later rebuild can reproduce the working configuration.
How to compare VPS offers for DirectAdmin
Provider marketing often emphasizes CPU cores or headline disk capacity, but those figures do not answer the installation question. Compare offers against the operational criteria below and verify each item in the provider’s current documentation or control panel.
| Comparison point | Questions to ask before ordering |
|---|---|
| OS image and lifecycle | Is the exact AlmaLinux, Rocky Linux, Debian or Ubuntu release supported by DirectAdmin, and how long will the provider keep that image available? |
| Root SSH access | Can you log in as root or obtain a complete root shell without provider intervention? |
| Static IPv4 | Is at least one dedicated, persistent IPv4 included, and can a second address be added if your DNS arrangement needs it? |
| Quota support | Does the VPS virtualization and filesystem combination expose the quotas DirectAdmin requires? |
| Memory, swap and disk | Can the plan meet the documented RAM, swap and post-install free-space minimums without relying on an overcommit policy you cannot control? |
| Network-interface model | Will the VPS expose a conventional interface name, an alias or a virtual device, and can you configure it if automatic detection fails? |
| Backups and snapshots | Can you snapshot a clean server before installation and restore the panel’s data later? |
| License arrangement | Is a DirectAdmin license bundled, or must you purchase and verify one separately? Pricing and bundle terms are not established by the technical requirements and can change. |
A bundled license does not mean the VPS is endorsed by DirectAdmin, and DirectAdmin does not supply the underlying VPS. Treat the license, server rental and backup service as separate operational dependencies unless your provider’s current contract explicitly combines them.
A first-login checklist
After the panel opens successfully, complete a short handover checklist before hosting accounts or applications:
- Confirm that the login URL uses the intended hostname or address and the expected panel port.
- Save the administrator credentials outside the VPS and protect the local copy of
setup.txt. - Record the OS release, CPU architecture, installed DirectAdmin version and license status.
- Confirm that the server’s static IPv4 address is attached to the interface DirectAdmin is using.
- Verify that swap, free disk space and quota behavior remain available after installation.
- Take the planned post-install snapshot or backup and document how to restore it.
- For an automated fleet, preserve the environment-variable values and configuration-file versions used to create the server.
With those checks complete, the VPS has a documented and reproducible DirectAdmin baseline. Future changes can be tested against that baseline instead of troubleshooting an undocumented mixture of operating-system packages, network aliases and panel settings.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
