Installing DirectAdmin on a VPS is not the same as ordering a normal DirectAdmin Hosting plan. A VPS gives you an empty server and root access. You must arrange a DirectAdmin licence, start with a clean supported Linux installation, run the installer, complete the configuration and then take responsibility for the server over time.
This guide takes you from a newly deployed VPS to a DirectAdmin server that is ready for controlled testing. It does not repeat account-level tasks such as uploading files, creating FTP users, changing PHP limits or using phpMyAdmin—those belong in your DirectAdmin knowledgebase once the panel is running.
Install DirectAdmin on a VPS only when the project needs root access and you intend to operate the hosting environment yourself. It suits developers, agencies, resellers and technical teams that need control beyond a standard hosting account. The installer creates a control-panel foundation; it does not make the VPS a production hosting service on its own.
Before you begin, decide who will own the ongoing work. On a self-managed VPS or VDS, that person is responsible for operating-system updates, DirectAdmin updates, access control, firewall policy, backups, monitoring, DNS, mail configuration and recovery if something stops working. If that level of ownership is not part of the plan, use DirectAdmin Hosting instead: the panel and normal website hosting environment are already set up and ready to use.
Do not use an existing live server for a first DirectAdmin installation
DirectAdmin's installation guidance is clear: use a clean operating-system installation, do not pre-install web, database, FTP or mail services, and do not install it over another hosting control panel. A live server has data, services and dependencies that the installer is not designed to convert. Rebuild a fresh VPS, test the setup and migrate workloads only after you have a proven plan.
What this guide installs—and what it does not do for you
The official DirectAdmin installer creates the control-panel foundation. You can then create administrator, reseller and user accounts and manage domains, websites, databases, email and related services. It does not decide your DNS model, account structure, backup target, access policy, update schedule or recovery procedure. It also leaves hostname TLS, mail routing, firewall policy and update ownership with the server administrator before production use.
The sequence below is deliberate. Running the installation command before resolving licensing, server cleanliness, hostname planning and access control can leave you with a panel that opens but cannot be operated, handed over or recovered safely.
DirectAdmin VPS preflight checklist
Every item below should be confirmed before you touch the installer.
A clean supported Linux VPS
Choose a Linux release that DirectAdmin currently supports. Do not reuse a server with cPanel, Plesk, an existing web stack or live customer data.
Root SSH access
The installer needs a real root shell. A standard hosting login and ordinary control-panel user are not enough to install server software.
An active DirectAdmin licence
A VPS from Website Hosts UK does not include DirectAdmin by default. Purchase or arrange the licence separately and check it is active before installation.
Enough memory, swap and storage
DirectAdmin's current requirements state at least 4 GB RAM, 4 GB swap and 2 GB of free disk after Linux is installed, before website data is considered.
A static IPv4 address
Plan the server IP and hostname before installation. DirectAdmin requires a static IPv4 address; running your own DNS requires additional planning.
A defined administration owner
Know who will apply updates, manage the firewall, check backups, respond to alerts and handle a recovery if the server has a problem.
Use DirectAdmin's official documentation as the installation source of truth
DirectAdmin can change supported operating systems, installer options and setup guidance. Before using the commands in this article, read the current DirectAdmin installation guide and system requirements. This article explains the hosting decision and the workflow around those official steps; it should not replace the vendor documentation.
How to install DirectAdmin on a VPS: numbered setup steps
Complete the steps in order. Each stage prevents a problem that is harder to fix once websites or email accounts are live.
Start with a new VPS and select a supported Linux release
Order or rebuild the VPS as a new server. DirectAdmin supports several mainstream Linux families, but the exact supported releases change over time. Choose a supported version from DirectAdmin's current list rather than choosing an operating system purely because it is familiar or because an older tutorial used it.
Do not install Apache, Nginx, PHP, MariaDB/MySQL, FTP software, mail software, another firewall stack or another hosting panel first. DirectAdmin's installer and build system are designed to install and configure the services it expects. Adding competing services before the panel is installed can create conflicts that are difficult to diagnose later.
Plan the server hostname, public IP and DNS responsibility
Decide the server hostname before installation. Use a fully qualified hostname that you control, such as server.example.co.uk, rather than a temporary provider label. The name should resolve to the server's public address and should be planned separately from the customer domains you will host later.
Confirm that the VPS has a static IPv4 address. DirectAdmin lists one static IPv4 as a minimum requirement. If you plan to operate authoritative nameservers from the same server, review the nameserver design early: depending on the registrar and how DNS is managed, you may need a second IP address or you may decide to use an external DNS service instead.
Hostname and DNS choices affect panel access, mail reputation, TLS setup and the speed of adding new domains. Set them before the panel starts creating accounts.
Arrange and verify the DirectAdmin licence before installation
DirectAdmin on a VPS needs its own licence. This is the main commercial difference between a self-managed VPS and DirectAdmin Hosting, where the panel and hosting environment are already supplied as part of the service.
Obtain the licence, then confirm it is active and verified in the DirectAdmin client area before starting the installer. Do not configure the VPS on the assumption that licensing can be fixed later. A missing or inactive licence can stop the build and leave you rebuilding a partially prepared server, so resolve it before changing the VPS.
For a more detailed look at why licence choice matters, see DirectAdmin Licensing Explained. Keep the licence key private and treat it like a credential: do not paste it into public tickets, screenshots or chat messages.
Log in through SSH as root and check the blank server
Connect using SSH and enter a real root shell. DirectAdmin's installer requires root access; it will not work correctly from a non-root session where you simply prefix the install command with sudo. If you normally log in with a non-root administrator account, switch to a root shell first using the operating system's proper method.
Before running the installer, verify the VPS hostname, RAM, swap, root filesystem capacity and assigned IPv4 address. Save those values in deployment notes; they provide the baseline for later capacity checks and troubleshooting.
# Check the current hostname
hostnamectl
# Check available memory and swap
free -h
swapon --show
# Check free disk space
df -h /
# Check the server's IPv4 addresses
ip -4 addrConfirm that RAM and swap match the plan, the root filesystem has working space, and the planned public IPv4 is present. Record any difference before proceeding. These checks matter more than matching example output from another server.
Confirm the server is clean and not carrying another hosting stack
This is the last safe point to stop and rebuild. Do not continue if the VPS was previously used for cPanel, Plesk, another control panel, a production WordPress server or a hand-built stack that you now hope DirectAdmin will take over. DirectAdmin does not convert an existing server into a clean DirectAdmin system as part of the installation.
A clean server does not only mean “no websites are visible”. It means you have not already installed overlapping web, database, mail and FTP services that DirectAdmin expects to control. If you are unsure what is present, rebuilding from a clean supported image is normally less risky than attempting to preserve an unknown configuration.
Run the official DirectAdmin setup script from the root shell
Once the licence, server checks and clean-install decision are complete, use the current command from DirectAdmin's official guide. The normal web-based route downloads the setup script and starts the initial system preparation:
sh <(curl -fsSL https://download.directadmin.com/setup.sh)Run this only from a root shell on the VPS you have checked. The script will prepare the system and print a temporary URL that you use in a browser to continue the installation. Treat the URL and its key as sensitive: it can provide temporary access to the installer, so do not share it or leave it accessible to everyone.
DirectAdmin also documents a command-line installation route that accepts a licence key and uses default settings. Use that method only where the installation options and deployment pattern are already documented. For a first manual build, the browser route makes it easier to review the choices that shape the server. Use unattended or customised installation only after documenting the hostname, DNS design, services and security controls the build must apply.
Complete the installer and record the administrator access safely
Open the temporary URL in a private browser session from your own trusted device and complete the installer using the active licence information. Review each choice rather than clicking through defaults without understanding what it changes. Record the server hostname, administrator username, recovery contact details and any nameserver information in your secure deployment notes.
At the end of installation, DirectAdmin provides the administrator credentials and a direct login route. Keep the administrator password in a password manager rather than a plain-text note. DirectAdmin also records setup credentials in its local setup file; that is useful for recovery, but it is another reason to protect root access and restrict who can read the server.
The installation might take time while it downloads and configures the components it needs. Do not interrupt it because the command has been quiet for a few minutes, and do not start adding customer websites while it is still building the environment.
Access the panel on port 2222 and test the administrator view
DirectAdmin normally uses port 2222. Access it through the server hostname or IP address at https://your-server-hostname:2222 once TLS is configured, or use the route provided by the installer while you complete the first setup. If the page cannot be reached, check the VPS provider's network firewall or security group as well as the operating-system firewall; do not respond by opening unnecessary ports to the whole internet.
Log in as the administrator and review the server-level areas before creating any customer account. The administrator role controls global server configuration, IPs, security options, backups, services and software updates. That is fundamentally different from a normal website-owner login.
Test the essentials in a controlled way: confirm you can log in, confirm the hostname is correct, check the server IPs shown in DirectAdmin and confirm you understand which level you are using—Administrator, Reseller or User. A mistaken assumption about access level can lead to changes being made in the wrong place.
Secure, configure and back up the server before hosting live sites
Once the panel opens, move to production-readiness work. Before adding a live domain or customer account, configure the server's security and operational controls. DirectAdmin's first-steps documentation highlights firewall and brute-force protection, software updates, secure PHP configuration, ModSecurity, strong passwords, hostname TLS, nameservers and backups.
Before production use, assign management IPs, document update ownership, establish off-server backup storage, test one restore and name the person who reviews alerts. Record the restore date, the account used and the destination recovered from. Until a backup has restored successfully, it has not been verified for recovery.
- Restrict panel and SSH access to the people who genuinely manage the server.
- Set and document a software-update and security-review routine.
- Configure a backup destination separate from the VPS itself.
- Test restoration of a small account before relying on backups for production.
- Configure nameservers or connect the server to the external DNS plan you chose.
- Enable and test TLS for the hostname, panel and the websites you later host.
- Create a monitoring and escalation plan for disk space, failed services, updates and backups.
Build one test account before migrating anything live
Run a small, reversible test before any migration. Create a test user, add a non-critical domain or subdomain, create a database, make a mailbox and issue a certificate. This checks account creation, DNS behaviour, mail configuration, web service and TLS setup before a production site depends on the server.
Do not treat a successful login as proof that the environment is ready for real websites. A server may load the panel perfectly while DNS, outbound mail, backups, hostname certificates or resource limits are still unfinished.
Keep the roles clear
Administrator: manages server-wide settings, services, security, backups and software.
Reseller: creates hosting packages and end-user accounts where that model is required.
User: manages their own domains, email, databases, files and ordinary website tasks.
Five DirectAdmin VPS installation mistakes to avoid
Installing on a live cPanel, Plesk or website server
DirectAdmin is not an in-place conversion tool. Build a new server and plan a migration instead of trying to layer another panel over a live environment.
Treating the licence as the entire setup
The licence allows DirectAdmin to run; it does not select your hostname, secure SSH, configure nameservers, make backups or run updates for you.
Opening broad firewall access for convenience
Troubleshoot the specific management path you need. Do not expose management ports more widely than necessary just to make first login easier.
Going live before backup restoration is tested
A scheduled backup job is not a recovery plan until you know where the data is stored and have proved that it can be restored.
Using a VPS when a ready-to-use account is the real requirement
A VPS is valuable when server control is necessary. For normal websites, email and domains, ready-to-use DirectAdmin Hosting is often less work and easier to manage.
When DirectAdmin Hosting is the better answer
Installing DirectAdmin on a VPS is a technical build, not a feature you need simply to host a WordPress or business website. Choose DirectAdmin Hosting when you want DirectAdmin, website hosting, domain email, SSL and normal account tools ready from the start. You do not need a separate licence and you do not need to build or administer the Linux server behind it.
Choose VPS Hosting or VDS Hosting when root access, a custom stack, isolated server resources or dedicated CPU are genuine technical requirements. Read DirectAdmin Hosting vs VPS before ordering if you need help deciding which responsibility level suits the project.
Related DirectAdmin and server guides
Use these after deciding whether you are building a self-managed server or choosing a ready-to-use hosting route.
DirectAdmin Hosting UK
DirectAdmin already set up for normal website, domain, email and SSL administration.
Root Access Hosting
Compare VPS and VDS options when the project requires server-level control.
DirectAdmin Licensing Explained
Understand the separate licence decision before installing DirectAdmin on your own VPS.
DirectAdmin Hosting vs VPS
Choose the right route before committing to the self-managed server responsibilities in this guide.
How to install DirectAdmin on a VPS FAQs
Can I install DirectAdmin on any VPS?
Only install DirectAdmin on a clean VPS that uses a Linux distribution currently supported by DirectAdmin and meets its current system requirements. Check the official requirements before ordering or rebuilding the server because supported operating-system versions can change.
Does a VPS from Website Hosts UK include a DirectAdmin licence?
No. Website Hosts UK VPS and VDS servers are self-managed and do not include a DirectAdmin licence by default. Arrange a separate licence before starting the DirectAdmin installation.
Can I install DirectAdmin on a server that already has cPanel, Plesk or another panel?
No. DirectAdmin advises against installing on a live production server or one that already has another control panel. Start with a clean supported Linux installation instead of attempting an in-place conversion.
How much RAM do I need for DirectAdmin on a VPS?
DirectAdmin's current system requirements state a minimum of 4 GB RAM and at least 4 GB swap memory. A busier website, a larger mail workload, more accounts or a heavier web stack can need more resources.
Do I need a static IPv4 address for DirectAdmin?
Yes. DirectAdmin's current requirements state that the server needs at least one static IPv4 address. Running your own authoritative DNS can require more planning and may require a second IP address or an external DNS service.
Do I need root access to install DirectAdmin?
Yes. DirectAdmin requires root access. A normal DirectAdmin Hosting account gives you control-panel access for website tasks, but it does not provide the root access needed to install server software.
What is the DirectAdmin installation command?
The current official web-installer command is sh <(curl -fsSL https://download.directadmin.com/setup.sh), run from a root shell on a clean supported server. Always recheck DirectAdmin's own installation guide before running it in case the process changes.
Can I use the DirectAdmin web installer rather than the command-line installer?
Yes. The official setup script can start a browser-based installation flow and prints a temporary URL. DirectAdmin also documents a command-line route that accepts a licence key and uses default configuration options.
Where do I log in after DirectAdmin is installed?
DirectAdmin is normally accessed using the server IP address or hostname on port 2222. The installer shows the administrator account details and saves them in the server's DirectAdmin setup file.
Does DirectAdmin set up email, DNS, websites and backups automatically?
The installer creates the control-panel environment, but you still need to make deliberate decisions about nameservers, DNS, user accounts, website data, email configuration, TLS certificates, backups, monitoring and ongoing maintenance.
Who is responsible for security and updates on a DirectAdmin VPS?
You are. A DirectAdmin VPS remains self-managed, so you or your server administrator are responsible for operating-system updates, DirectAdmin updates, firewall policy, backups, monitoring, access control and the services you choose to run.
When should I choose DirectAdmin Hosting instead of installing DirectAdmin on a VPS?
Choose DirectAdmin Hosting when you want the panel, website hosting environment, email, SSL and normal account tools ready to use without buying a separate licence or administering a Linux server.
A DirectAdmin VPS makes sense only when server control is a deliberate project requirement. Start with a clean server, verify the licence and resource requirements, follow the official installer, secure the result and test the operating process before real websites depend on it. When the project only needs a normal website account, choose DirectAdmin Hosting and avoid taking on Linux server management as a deliberate responsibility.
