The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →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.
After Virtualmin installs, do not create a production site immediately. First open the panel on port 10000, finish the post-install wizard, confirm the server hostname and DNS, choose the appropriate feature profile, install updates, and run Check Configuration. Only when those checks pass should you create a virtual server and test its web, DNS, mail, database, and SSL functions. Finish by configuring an off-server backup and testing a restore path.
1. Sign in and finish the post-install wizard
Open the encrypted Virtualmin panel
- Open
https://your-hostname:10000in a browser. Port 10000 is Virtualmin’s control-panel port and uses HTTPS. - If DNS for the hostname is not ready, use the server’s IP address instead.
- Sign in with root or another account that has the sudo privileges required by your installation.
An IP-based login can show a browser certificate warning when the server does not yet have a trusted certificate for its hostname. That warning is acceptable for this setup stage only after you have verified that you are connecting to the correct server. Do not treat it as the finished state for administration.
Answer the wizard for the intended environment
Virtualmin’s guided post-install wizard configures the installation for the environment you selected and asks questions that determine which services are enabled. Read each choice as an operating decision, not merely a default to accept. A mail-enabled hosting server, a web-only application server, and a machine whose DNS is managed elsewhere have different requirements.
Record the choices you make. That record helps you explain later why a service is absent, why a package was installed, or why a test should be skipped. The wizard can be completed before you create any virtual server; there is no benefit to publishing a site while these global settings remain undecided.
2. Set a proper hostname, DNS, and certificate path
Use a fully qualified hostname
Give the operating system a fully qualified hostname such as host.example.com. The hostname should not be exactly the same as a domain you plan to host as a virtual server. Keeping the management hostname separate prevents the panel’s identity from colliding with a hosted domain and makes certificate and service troubleshooting clearer.
For automatic certificate issuance, the hostname must resolve publicly to this server and the required ports must be reachable from the certificate authority. If the DNS record is missing, points elsewhere, or is blocked by a firewall or provider rule, the certificate request can fail even though the installation itself completed.
Repair the hostname certificate after DNS is ready
- Publish the hostname’s DNS record and wait until it resolves to the server from outside your network.
- Confirm that the ports needed for certificate validation are reachable.
- Return to Virtualmin and request or renew the certificate for the system hostname.
- Reconnect to
https://your-hostname:10000and verify that the browser presents a certificate for that hostname.
If DNS or reachability cannot be corrected immediately, continue initial setup by IP and accept the temporary warning for that session. Revisit the certificate as soon as the hostname resolves correctly; leaving the warning in place makes it harder to distinguish a trusted administrative connection from an accidental or intercepted one.
Decide who operates authoritative DNS
Choose one authoritative DNS design before creating domains:
- Local DNS: Virtualmin operates the DNS service on this server. Choose this only when you will publish the required authoritative records and maintain that service.
- External DNS: A separate DNS provider remains authoritative. In that case, create and maintain the records there, and do not assume that changing a local zone changes public resolution.
Whichever model you choose, make sure the domain records point to the server before you use automatic SSL issuance or judge a new site from an outside connection. DNS propagation and cached answers can make a recently corrected record appear broken for a while, so test from more than one network when a result is ambiguous.
3. Select the full or mini feature profile
The profile controls which packages and services are installed. It is safer to omit a service you deliberately do not operate than to enable a service without a plan for updates, security, storage, and monitoring. Omitted features can be added later when their packages are installed.
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 reinstall| Capability | Full profile | Mini profile |
|---|---|---|
| Local mail handling | Included | Omitted |
| Spam filtering | Included | Omitted |
| Virus filtering | Included | Omitted |
| Local DNS | Included | Omitted |
| FTP | Included | Omitted |
| Jailkit | Included | Omitted |
Choose full when the server is a self-contained host
Use the full profile when this machine will provide local mail, spam or virus filtering, local DNS, FTP, or Jailkit isolation. These services make the server more self-contained, but they also increase package count, memory use, update work, and the number of services that must be tested.
Choose mini when other systems provide those services
Use mini when mail, DNS, file transfer, or related functions are intentionally supplied elsewhere or are not needed. Do not select mini merely because the initial server is small if you expect to run the omitted services shortly afterward. Add a feature only after confirming that its packages are installed and that you have an operational plan for it.
Check memory against the selected profile
| Installation type | Published memory guidance | What it implies |
|---|---|---|
| Minimal installation | At least 1 GiB RAM | Suitable only for a minimal service set. |
| Full installation with mail, spam filtering, and virus scanning | 4 GiB RAM or more | Allows the larger service profile described by the installer guidance. |
These are installation requirements, not a guarantee of capacity for every workload. A busy application, many domains, or large mail queues can require more resources. If you select full services on a machine below the published guidance, expect installation or runtime problems and resize before production use.
4. Apply operating-system and Virtualmin updates
Use the dashboard
From the Virtualmin dashboard, choose Install All Updates Now. Review what will change, allow the package operation to finish, and sign in again if services restart the panel or the web server. Do not interrupt a package transaction partway through; an incomplete transaction can leave dependent services in a mixed state.
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 glitchesUse the documented package-manager routes
If you prefer the command line, use the route matching the operating system family:
- Enterprise Linux systems:
dnf update -y - Debian derivatives:
apt-get update && apt-get upgrade -y
Run these commands from a root or appropriately privileged shell. Check the command output for held packages, dependency errors, or a request to restart services. Resolve those messages before moving on to the configuration check.
Keep Virtualmin’s application catalog current
If you use Virtualmin-managed application installers, enable System Settings → Web App Installers → Installer Updates. This updates installer metadata; it is separate from updating the operating system packages themselves. Keeping both current prevents a newly created site from being deployed from stale application information.
5. Run Check Configuration before creating a site
The configuration check is the gate between installation and publishing. Virtualmin’s documentation places it on the List Virtual Servers page: click Check Configuration at the top of that page and read every reported item.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Open List Virtual Servers.
- Click Check Configuration.
- Resolve hostname and DNS errors first, because certificate and service tests depend on correct identity and resolution.
- Resolve package or service errors next. A missing package or stopped daemon can make a later site test misleading.
- Resolve certificate and reachability errors, then run the check again.
- Repeat until the report no longer contains issues that affect the services you intend to operate.
Do not treat a warning as harmless solely because the panel loads. A panel that opens by IP can still have an unusable hostname certificate, incorrect DNS, or a disabled service. The check is specifically intended to expose those conditions before the first virtual server is created.
6. Create and validate the first virtual server
Prepare the domain before clicking Create Virtual Server
- Confirm the domain is not being used as the system hostname.
- Decide where its authoritative DNS records will be maintained.
- Point the necessary records to this server if the site should be publicly reachable.
- Know which enabled services the site actually needs: web only, mail, database access, or SSL.
- Ensure the configuration check has been run and its relevant errors are fixed.
Create the account
On the Virtualmin interface, use Create Virtual Server after the configuration check passes. Select the intended domain and only the services required for that account. A web-only domain should not be treated as mail-enabled unless local mail was deliberately included and tested.
Test the resulting site in a fixed order
- HTTP and HTTPS: Open the site externally and confirm that the expected content is served over the protocols you intend to support.
- DNS: Verify that the public records resolve to this server, not an old address or a different provider.
- SSL identity: Confirm that the certificate matches the domain visitors are using. A certificate for the system hostname does not automatically prove that the hosted domain is covered.
- Mail, when enabled: Send and receive a test message using the domain. If local mail was omitted, do not interpret the absence of a local mailbox as a failure.
- Database connectivity: For an application that needs a database, perform a real connection test with the account and database credentials created for that application.
Test from outside the server as well as from the panel. Local success can hide a public DNS, firewall, routing, or certificate problem.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.7. Troubleshoot the common post-install failures
| Symptom | Likely area to inspect | Corrective action |
|---|---|---|
| Browser warning when opening the panel by hostname | Hostname DNS, certificate issuance, or reachability | Use the IP temporarily, make the hostname resolve publicly, confirm required ports are reachable, then request the hostname certificate again. |
| Configuration check reports a hostname problem | Fully qualified hostname or name collision with a hosted domain | Use a separate host name such as host.example.com and correct the system’s hostname and DNS. |
| Automatic certificate request fails | DNS still points elsewhere or validation ports are blocked | Correct the public record and reachability, wait for the change to be visible, and retry. |
| Expected mail, DNS, FTP, or Jailkit controls are absent | Mini profile or missing packages | Confirm the selected profile, install the required packages, and enable the feature only when its service will be operated. |
| Site works locally but not from the Internet | Public DNS or network reachability | Check the authoritative DNS provider and the server’s reachable ports from an external network. |
| Application cannot connect to its database | Application credentials, database setup, or service availability | Test the database service and credentials separately before debugging the application code. |
Run Check Configuration again after each structural correction. This keeps the panel’s report aligned with the actual state instead of relying on an earlier result.
8. Set up an off-server backup and prove it works
A backup stored on the same server does not protect you from disk failure, a compromised host, or an administrator mistake that removes both the site and its backup. Configure a destination outside the Virtualmin machine, define retention that matches your recovery needs, and perform a restore test before calling the backup complete.
Choose the destination deliberately
- Remote object storage: Useful for separating backups from the host and for retaining multiple generations. Verify the provider’s compatibility, credentials, lifecycle rules, and egress or restore terms.
- Another server: Keeps data under your control, but requires secure access, sufficient capacity, and monitoring of the receiving host.
Virtualmin 8 release documentation describes cloud-backup enhancements and support for many S3-compatible storage providers. Treat that as an integration option to verify against the installed Virtualmin version, operating system, and provider terms rather than as a guarantee that every provider uses identical settings.
Test recovery, not just upload
- Run a backup for the new virtual server.
- Confirm that the remote destination contains the expected files and metadata.
- Restore at least one site component to a safe test location.
- Verify that restored web content, configuration, database data, and mail data (when enabled) are usable.
- Record the restore procedure and the time it took, then schedule recurring backups and periodic restore tests.
9. Optional integrations to evaluate after the baseline is stable
Virtualmin 8 release documentation also describes enhancements for DNS and backups, Cloudflare DNS and proxy features, and multiple ACME-compatible SSL providers. These integrations can reduce manual work, but they add external credentials and provider-specific behavior. Add them only after the basic hostname, configuration check, first-site tests, and backup restore have succeeded.
- Verify that the integration is supported by your installed Virtualmin version and operating system.
- Use the provider’s current authentication and permission model.
- Document which system is authoritative for DNS and which system is responsible for certificate renewal.
- Retest DNS, HTTPS, and backup recovery after enabling an integration.
10. A practical post-install checklist
- Panel opens at
https://your-hostname:10000, or you have a documented temporary IP login while DNS is repaired. - Hostname is fully qualified, publicly resolvable when automatic certificates are required, and distinct from every hosted domain.
- Post-install wizard choices match the services you will actually run.
- Memory meets the guidance for the selected profile: at least 1 GiB for minimal installs or 4 GiB or more for full installs with mail, spam filtering, and virus scanning.
- Operating-system packages and Virtualmin-managed installer metadata are current.
- List Virtual Servers → Check Configuration reports no unresolved issue that affects the planned services.
- First virtual server has been tested over HTTP/HTTPS, with its DNS and domain certificate verified.
- Mail and database tests have been performed only where those services are enabled and required.
- Backups reach an off-server destination, and at least one restore has been verified.
Once this list is complete, the server has moved from an installed control panel to an intentionally configured hosting platform. Future domains can follow the same sequence: confirm DNS and service requirements, create the virtual server, test the enabled features, and include the account in the backup and restore routine.
Recommended Free Tools
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.
