Install DirectAdmin on a VPS:a current setup checklist

Start with a supported operating system

CentOS Linux 7 reached end of life on 30 June 2024; CentOS Linux 8 reached end of life on 31 December 2021. Choose a distribution and release on DirectAdmin’s current supported list for a new server. CentOS Stream is a separate release line, so support for one CentOS product does not establish support for another.

Choose a clean installation with sufficient memory, storage, and CPU for your intended websites, databases, mail, and backup workload. A supported distribution is only the starting point: you must also plan patching and ongoing administration.

DirectAdmin’s requirements at this review specify at least 4 GB of RAM, 4 GB of swap, and one static IPv4 address, along with a kernel and filesystem that support quotas. These are installation requirements, not a capacity recommendation for a busy store or many customer accounts. Allow additional storage for the operating system, website data, mail, logs, and backups.

Check the licence and access requirements

Confirm that you have an appropriate active DirectAdmin licence and understand any account or domain limits. The installer requires a root shell on the server. Use authorised SSH access and the connection details from your provider, and keep a working recovery console available.

Set a stable hostname using a subdomain you control, and configure its DNS as the vendor requires. If the server will send email, review reverse DNS, mail authentication, and network restrictions with the provider. A control panel does not automatically make a new server ready to send reliable mail.

Prepare before running the installer

1. Read the current vendor installation guide and operating-system requirements.
2. Create a server snapshot or verified backup.
3. Apply the operating system’s security updates.
4. Confirm the hostname, network addressing, and time synchronisation.
5. Review firewall access for SSH and the required DirectAdmin services.
6. Record a recovery plan before modifying network rules.

The installer changes system packages and service configuration. Use a fresh server rather than a production machine already running a different control panel. Avoid copying old installation commands from screenshots or a third-party blog; download and run only the current vendor-documented installer after reviewing it.

Follow the current DirectAdmin installation guide

Use the official installation guide linked in the sources section. It offers a browser-assisted installer and a command-line path using your licence key. Run the current vendor-documented command from the required root shell, then follow the chosen setup method. Installer options, licence activation, and software-build choices change over time, so keep licence keys and generated login links private and follow the instructions for your distribution.

Keep the installation log available if a service fails. Check package dependencies, the firewall, DNS, and licence state before repeating the installer. Re-running a partially completed installation without diagnosis can make recovery more complicated.

Secure and test the new server

Enable a valid certificate for the panel, use strong unique credentials, and restrict administrative access where practical. Set up scheduled backups to a separate location and test restoration. Review SSH settings carefully while maintaining a second working session, so a configuration error does not lock you out.

Create a test account and website. Check web serving, database access, HTTPS, DNS, and email if mail is enabled. Monitor memory, disk space, and errors. Make sure somebody owns routine updates and incident response; an unmanaged VPS leaves those responsibilities with you.

If you would rather maintain the site than the server, compare managed services before choosing a VPS. Our hosting beginner’s guide explains the tradeoffs.