iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
Install DirectAdmin on a newly provisioned, supported Linux VPS with root SSH access, a verified license, at least 4 GB of RAM, 4 GB of swap and 2 GB of free disk space after the operating system is installed. Connect as root, run DirectAdmin’s setup.sh installer, save the credentials written to /usr/local/directadmin/conf/setup.txt, then open the panel on port 2222.
What you need before installing DirectAdmin
DirectAdmin is a server control panel, not an application that should be added to an already configured web server. Its installer configures services including the web server, PHP, database, FTP and mail components. Start with a clean VPS image and let DirectAdmin perform that configuration. Installing it over another control panel or a production server with existing service configurations can cause conflicts and is outside the supported installation model.
Supported operating system and architecture
Choose a current release from one of DirectAdmin’s supported Linux families:
- RHEL-compatible distributions, including AlmaLinux and Rocky Linux.
- Debian.
- Ubuntu.
DirectAdmin’s supported-release policy changes as distributions reach end of life. Check the current operating-system policy when you create the VPS, and select an image whose release is still supported on the date of installation. The VPS must use amd64/x86-64 or arm64 hardware. Do not assume that every image offered under one of those architecture labels is supported; the exact distribution release also matters.
#1 Best Overall
Minimum server resources
| Requirement | Minimum | Qualification |
|---|---|---|
| Memory | 4 GB RAM | DirectAdmin’s documented minimum; busy sites, mail, malware scanning and large databases need more. |
| Swap | 4 GB | Required minimum swap allocation in the current system requirements. |
| Disk | 2 GB free | Free space remaining after Linux is installed; this is not a recommended total disk size. |
| Privileges | Root access | The installer must run from a root shell. |
| Addressing | At least one static IPv4 address | Some DNS-control arrangements may require two addresses. |
| Kernel/filesystem | Quota support | The VPS platform and selected filesystem must allow the quota features DirectAdmin expects. |
The RAM, swap and disk figures are vendor requirements, not a performance benchmark. A 4 GB VPS can install successfully but may become constrained when it hosts several sites, email, databases or resource-intensive applications. Plan capacity from the workloads you intend to run.
Network, access and licensing checks
- Confirm that SSH login works and that you can obtain a root shell. A normal user account with
sudois acceptable only if you use it to enter a root shell before starting the installer. - Reserve a static IPv4 address. Dynamic or frequently changing addresses complicate licensing, DNS and panel access.
- Verify that the VPS provider exposes quota support rather than masking or disabling it in the virtualization layer.
- Confirm that the DirectAdmin license in your client account is marked Active and Verified before running setup.
- Record the server’s public IP, hostname and intended nameservers. Set a fully qualified hostname in DNS when possible; it avoids later certificate and mail-identity repairs.
Provision and prepare the VPS
- Deploy a fresh image. Select a supported AlmaLinux, Rocky Linux, Debian or Ubuntu release for amd64/x86-64 or arm64. Do not select an image that already contains another control panel, web stack or mail stack.
- Allocate the documented minimums. Provide at least 4 GB RAM, 4 GB swap and 2 GB free disk after the OS installation. Leave additional disk for logs, backups, websites, databases and package updates.
- Assign networking. Attach a static IPv4 address and configure reverse DNS if your provider offers it. Note the interface names shown by the VPS rather than assuming the device is called
eth0. - Enable SSH and root access. Test an SSH connection from your workstation and confirm that
id -ureturns0in the shell that will run setup. - Check quotas. Verify with the VPS provider that filesystem or kernel quota support is available. If quotas are unavailable, choose a different VPS configuration before installing; changing virtualization features later can require a rebuild.
- Take a pre-install snapshot if available. The snapshot is useful for returning to a clean image when an interrupted or misconfigured installation must be repeated.
Connect as root and run the installer
Use the browser-assisted installation
From a root SSH shell, run the official setup script:
Recommended Free Tools
sh <(curl -fsSL https://download.directadmin.com/setup.sh)
The script performs initial setup and prints a URL for continuing in a browser. Keep the SSH session open until the installer reports completion. If your terminal disconnects, reconnect and inspect the installer output and service state before starting another run; do not launch multiple installers concurrently.
Use a command-line installation
Pass the active license key as the argument when you want setup to proceed without the browser flow:
sh <(curl -fsSL https://download.directadmin.com/setup.sh) 'YOUR_LICENSE_KEY'
The command-line path uses default configuration unless you define options in advance. Replace YOUR_LICENSE_KEY with the key issued for this server; do not publish the key in shell history, screenshots or support requests. If your shell history records it, restrict access to that history or remove the exposed entry according to your organization’s credential policy.
What happens during setup
DirectAdmin identifies the operating system and architecture, validates the license, installs its panel and configures the associated service stack. Duration depends on CPU, disk and network speed. The process can change package repositories, firewall rules and service configuration, so it should be run on the clean image you prepared rather than on a server carrying production workloads.
Rank #2
When setup finishes, copy the administrator username, password and login URL from the output. The same credentials are saved locally in:
/usr/local/directadmin/conf/setup.txt
Protect that file as a secret. Anyone who can read it may be able to administer the panel.
Open DirectAdmin after installation
- From a trusted workstation, open
http://server.ip.address:2222, replacing the example address with the VPS’s static IPv4 address. - If setup displays an HTTPS URL, use that URL instead. A browser warning can appear until a trusted hostname certificate is configured.
- Sign in with the administrator credentials from the installer output or
setup.txt. - Change the generated administrator password if your operational policy requires a replacement, and store the new credential in an approved password manager.
Port 2222 is DirectAdmin’s panel port. If the page does not load, check the VPS firewall, any provider-level firewall or security group, and whether the DirectAdmin service is running. Do not expose additional administrative ports broadly when a restricted source-IP rule will work.
Verify the installation from the shell
The main executable is /usr/local/directadmin/directadmin, and DirectAdmin also provides the /usr/bin/da symlink. These commands provide a quick health and version check:
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →da version
da license
da login-url
systemctl status directadmin
da version reports the installed panel version, da license shows license status, and da login-url prints a usable panel URL. To start the service explicitly:
systemctl start directadmin
Use systemctl status directadmin and the system journal when a start operation fails. Do not delete configuration files to make a failed service start; first identify whether the cause is licensing, an invalid interface, a missing dependency or a port conflict.
Set repeatable or customized installation options
For repeatable deployments, define environment variables before invoking setup.sh. DirectAdmin supports these variables:
| Variable | Purpose |
|---|---|
DA_HOSTNAME |
Sets the server hostname. |
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 build when the selected operating-system slug requires it. |
Set only values you have decided and tested. For example, a deployment script can export the hostname, email and nameservers, then invoke the same setup command. Keep the script outside public repositories because it may contain license material or infrastructure details.
Windows 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 reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchMore extensive CustomBuild settings can be supplied before setup runs:
/usr/local/directadmin/custombuild/options.conffor web-server, PHP, download and related CustomBuild choices./usr/local/directadmin/conf/directadmin.conffor DirectAdmin configuration, including network-interface selection.
Only use settings documented for the selected DirectAdmin and operating-system combination. A typo in either file can produce a partial installation or an invalid service configuration. Keep a copy of known-good files so a rebuilt VPS can be reproduced consistently.
Fix common VPS installation failures
The installer cannot find the interface holding the server IP
Some VPS network models use device names that differ from the conventional eth0. List every interface and address:
ip a
Find the full device name that owns the public server address, then set that name in /usr/local/directadmin/conf/directadmin.conf. For example:
Rank #4
ethernet_dev=eth0:1
The correct value might instead be venet0:0, eth1 or another name shown by ip a. Use the exact spelling and suffix reported by the VPS. Restart or rerun the affected DirectAdmin operation after saving the setting.
Architecture or loader errors appear
Check that the operating system installed on the VPS matches the operating system selected or licensed for DirectAdmin. An image mismatch can produce binary or dynamic-loader errors even when the CPU architecture appears correct. On a new server, the supported recovery is to provision the correct OS image and rerun setup.sh rather than trying to replace system libraries on the damaged installation.
The panel is unreachable on port 2222
- Run
systemctl status directadminandda login-urllocally. - Confirm that the URL uses the VPS’s current static IPv4 address and port 2222.
- Allow TCP 2222 in the host firewall only as broadly as necessary.
- Check provider-side firewalls, security groups and network ACLs for a conflicting deny rule.
- Verify that another service has not claimed the port and that the VPS has not changed its public address.
The license is rejected
Stop and verify that the license is Active and Verified in the client account, that the server’s IP is the address licensed for use, and that the VPS can reach the licensing service. Correct the account or network problem before repeating setup. Repeated attempts with an unverified license do not repair the underlying issue.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesInstallation stops partway through
Review the terminal output and available disk space, then check the service status and package-manager logs. If the VPS is no longer a clean, known state, restore the pre-install snapshot or deploy a new image and start again. Rebuilding is usually safer than layering a second installer run over half-written panel and service files.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose a VPS that will keep DirectAdmin reliable
The cheapest VPS is not necessarily suitable. Evaluate these dimensions before ordering:
| Decision point | What to verify | Why it matters |
|---|---|---|
| OS image and lifecycle | A currently supported AlmaLinux, Rocky Linux, Debian or Ubuntu release, with a documented replacement path before end of life. | DirectAdmin support depends on both family and release. |
| Root SSH | Full root access or a documented method to obtain a root shell. | The installer cannot run from a restricted hosting account. |
| IPv4 policy | A static IPv4 address and clear reassignment rules. | Licensing, DNS and panel access rely on stable addressing. |
| Quota behavior | Filesystem or virtualization quota support enabled for the selected plan. | DirectAdmin expects quota capability for account resource controls. |
| Capacity | At least 4 GB RAM, 4 GB swap and 2 GB post-install free disk, plus workload headroom. | Minimum install figures leave little room for sites, mail and backups. |
| Network interface model | The interface names exposed by the hypervisor and whether aliases are used. | You may need the ethernet_dev setting. |
| Backups and snapshots | Independent backups or snapshots that can restore a clean server. | A failed customization or upgrade should not require data loss. |
| License arrangement | Whether a DirectAdmin license is included or must be purchased separately, and who handles activation. | A bundled license can have different renewal and IP-assignment rules. |
Provider prices, bundles and licensing terms change. Confirm each item on the provider’s current plan and policy pages before ordering; DirectAdmin’s technical requirements do not endorse a particular VPS company.
Best Value
Security and maintenance immediately after setup
- Restrict SSH and DirectAdmin access to trusted source networks where practical, while preserving an emergency access path.
- Replace generated credentials and protect
setup.txt. - Configure DNS records and reverse DNS before sending production mail.
- Set up backups outside the VPS and test a restore, not just the creation of backup files.
- Monitor disk, memory, swap, certificate expiry and mail queues.
- Use
da updatefor the panel’s update operation when you have a maintenance window and a recoverable backup.
DirectAdmin’s minimum resource figures describe whether installation is supported; they do not guarantee capacity for a particular number of domains or visitors. Increase RAM, CPU, disk or swap as your measured workload grows.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Frequently asked questions
Can I install DirectAdmin on a VPS that already has a web server?
Use a clean operating-system image instead. DirectAdmin installs and configures its own web, PHP, database, FTP and mail components, so existing services can conflict with the supported setup.
Do I need two IPv4 addresses?
One static IPv4 address is the documented minimum. Certain DNS-control arrangements may require two, so check the design of your nameserver setup before provisioning.
Where are the DirectAdmin login credentials stored?
The installer prints them and saves them in /usr/local/directadmin/conf/setup.txt. Treat that file as sensitive administrative data.
Which port does DirectAdmin use?
The panel listens on port 2222. Use the HTTPS address printed by setup when available, or the equivalent server-IP URL with port 2222.
Free tools Windows power users keep installed
One-click scans. No signup required.
What should I do if the VPS uses venet0:0 instead of eth0?
Run ip a, identify the interface that owns the public address, and set that exact device name as ethernet_dev in /usr/local/directadmin/conf/directadmin.conf.
Is 4 GB RAM enough for production?
It meets the documented installation minimum, but actual capacity depends on domains, databases, mail and traffic. Treat it as a starting point and monitor resource use before adding workloads.
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.

