Yes—you can host many domains on one VPS and one public IP. DNS sends each hostname to the VPS, then hostname-based virtual hosting selects the correct website: Nginx uses server_name inside a server block, while Apache uses ServerName and ServerAlias inside a name-based <VirtualHost>. Each site should have its own document root, configuration, logs, application credentials and backups.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
The practical sequence is: point every domain at the VPS, create an isolated site directory, add one Nginx server block or Apache virtual host per domain, enable and syntax-check the files, reload the web server, then issue certificates with Certbot. There is no reliable universal site-count limit; traffic, application workers, databases, memory and storage determine how many sites the VPS can run safely.
As an Amazon Associate I earn from qualifying purchases.
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 →How one VPS serves multiple domains
A browser includes the requested hostname in its HTTP request. DNS resolves that hostname to the VPS public address, and the web server examines the hostname before choosing a configuration. Nginx compares it with server_name; Apache compares it with ServerName and any ServerAlias values. The selected configuration then serves files from that site’s document root or forwards the request to an application upstream.
This is hostname-based hosting, also called name-based virtual hosting. Apache’s documentation uses “virtual host” for running more than one website on one machine and distinguishes name-based hosting from assigning a separate IP address to every site. A single IPv4 address can therefore serve an apex domain, its www name and many unrelated domains, provided DNS and the web-server configurations agree.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
Isolation is logical rather than physical. If all sites share one VPS, a kernel failure, disk failure, provider outage or serious resource exhaustion can affect every site. Separate users, databases, logs and backups reduce accidental access and make operations clearer, but they do not create separate failure domains.
What you need before adding the first site
- A VPS with a supported Linux distribution, administrative access and a stable public IPv4 address. Add IPv6 only when the VPS firewall and web server are configured for it.
- Nginx, Apache or both installed. Decide which service will bind to public ports 80 and 443; two services cannot normally listen on the same address and port.
- Registered domains and control of their DNS zones. You need an A record for each IPv4 hostname and an AAAA record only when IPv6 is actually working end to end.
- A deployment account, a web-server account (commonly
www-dataon Debian-derived systems), and a plan for file ownership. Do not make every site’s files globally writable. - A firewall that permits only required traffic—normally SSH from controlled source addresses, HTTP on port 80 and HTTPS on port 443. Keep databases and application backends on localhost or a private network.
- Enough disk space for site files, uploads, logs, databases, backups and operating-system updates. Leave headroom for traffic spikes rather than sizing to average usage.
Distribution defaults differ. Paths such as /etc/nginx/sites-available/ and /etc/apache2/sites-available/ are common on Debian and Ubuntu, while other distributions may use a single configuration directory. Keep the same separation of one file and one root per site even when the paths differ.
Recommended Free Tools
Choose Nginx, Apache or a mixed design
| Architecture | Configuration unit | Best fit | Operational trade-off | HTTPS arrangement |
|---|---|---|---|---|
| Nginx only | server { } block |
Static files, reverse proxies and sites that follow consistent conventions | Usually the least moving parts when every site uses the same stack | Certbot’s Nginx integration edits the matching server block |
| Apache only | <VirtualHost> |
Applications that need .htaccess or Apache-specific modules |
Straightforward when the applications already expect Apache behavior | Certbot’s Apache integration edits the matching virtual host |
| Nginx in front of Apache | Public Nginx block proxying to an internal Apache listener | Mixed legacy and modern applications on one machine | Highest complexity: two services, internal ports, proxy headers and two sets of logs | Normally terminate TLS at Nginx, then proxy over localhost or a private interface |
Choose one web server when it can satisfy all sites. A mixed setup is valid, but it should solve a real compatibility requirement rather than be added by default.
Configure several sites with Nginx
1. Create a separate root and ownership model for each domain
Use a predictable layout such as /var/www/example.com/public and /var/www/example.net/public. The final public directory is the only directory exposed as a document root; keep environment files, private uploads and deployment metadata outside it.
sudo mkdir -p /var/www/example.com/public
sudo mkdir -p /var/www/example.net/public
sudo chown -R deployuser:www-data /var/www/example.com
sudo chown -R deployuser:www-data /var/www/example.net
sudo find /var/www/example.com -type d -exec chmod 750 {} ;
sudo find /var/www/example.com -type f -exec chmod 640 {} ;
Replace deployuser and the group with the accounts used on your distribution. The web-server process needs read access to public files and write access only to directories that genuinely require uploads, caches or generated files.
2. Add one server block per hostname set
Create a file for each site under /etc/nginx/sites-available/. The following serves a static site and also leaves the conventional PHP index name available if a later upstream is added.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
server {
listen 80;
listen [::]:80;
server_name example.com www.example.com;
root /var/www/example.com/public;
index index.html index.php;
access_log /var/log/nginx/example.com.access.log;
error_log /var/log/nginx/example.com.error.log;
}
Create a second file with its own server_name, root and log paths for example.net. Never reuse a site’s root merely because the domains currently display similar content; separate roots prevent an edit or deployment intended for one domain from silently changing another.
3. Enable only the intended files
On systems using the available/enabled convention, make a symbolic link for each site:
sudo ln -s /etc/nginx/sites-available/example.com.conf /etc/nginx/sites-enabled/example.com.conf
sudo ln -s /etc/nginx/sites-available/example.net.conf /etc/nginx/sites-enabled/example.net.conf
Inspect the enabled directory and remove or disable the distribution’s default site if it would answer requests for unmatched hostnames. Keep a deliberate default server when you want unknown or malformed Host headers to receive a neutral response instead of another site’s content.
4. Validate before reloading
Always parse the complete configuration before applying it:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
sudo nginx -t
sudo systemctl reload nginx
A successful syntax check means Nginx can parse the files; it does not prove that DNS, permissions, upstream applications or certificates are correct. Reload applies valid changes without the interruption associated with a full restart. If the check fails, fix the reported file and line, rerun it and leave the running configuration untouched until the test passes.
5. Verify each hostname and its logs
After DNS has propagated, request every hostname separately:
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
curl -I http://example.com
curl -I http://example.net
When DNS is not ready, test the intended address without changing public DNS by supplying the Host mapping:
curl -I --resolve example.com:80:203.0.113.10 http://example.com/
Replace 203.0.113.10 with the VPS address. Check the per-site access and error logs while making a request. A response from the wrong site usually means the hostname does not match the intended block, the request reached a default server, or the DNS record points elsewhere.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated 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 matchConfigure several sites with Apache
1. Create roots and log destinations
Use the same one-directory-per-domain layout as with Nginx and give each virtual host separate access and error logs. Distinct logs make it possible to identify which site generated a load spike or an application error.
2. Define a name-based virtual host
Create one file per site in /etc/apache2/sites-available/ on Debian-derived systems:
<VirtualHost *:80>
ServerName example.com
ServerAlias www.example.com
DocumentRoot /var/www/example.com/public
ErrorLog ${APACHE_LOG_DIR}/example.com-error.log
CustomLog ${APACHE_LOG_DIR}/example.com-access.log combined
<Directory /var/www/example.com/public>
AllowOverride All
Require all granted
</Directory>
</VirtualHost>
AllowOverride All permits an application to use .htaccess; disable overrides when the application does not need them and put equivalent rules in the main configuration for tighter control. Apache’s exact module names, directory paths and service unit can vary by distribution.
3. Enable, test and reload
sudo a2ensite example.com.conf
sudo a2ensite example.net.conf
sudo apachectl configtest
sudo systemctl reload apache2
Disable the default site when it could catch an unmatched request:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
sudo a2dissite 000-default.conf
sudo apachectl configtest
sudo systemctl reload apache2
Do not disable a default configuration blindly on a distribution that uses it for another required service. Confirm the active virtual hosts with your distribution’s Apache inspection command and check that each ServerName and ServerAlias is unique.
Point DNS at the VPS before requesting certificates
For every site, create an A record for the apex domain and the www hostname if you intend to serve both. Add AAAA records only when the VPS, firewall, routing and web server all accept IPv6. An AAAA record that points to a non-working address can make some visitors fail even when IPv4 is correct.
- Publish the A and, where applicable, AAAA records at the authoritative DNS provider.
- Wait for the records to resolve to the VPS address. Check both the apex and every alias used in
server_nameorServerAlias. - Confirm that the web server answers on port 80 for each hostname before attempting HTTP-based certificate validation.
- Allow inbound ports 80 and 443 in the VPS firewall and any provider-level firewall.
A DNS mismatch, a closed validation port or a hostname missing from the web-server configuration commonly prevents HTTP validation. Treat these as troubleshooting hypotheses: inspect DNS answers, firewall rules, listeners and the request logs rather than assuming one cause.
Add HTTPS with Certbot
Once the HTTP site responds correctly, use the Certbot integration that matches the public web server. Each -d option adds a name to the certificate’s Subject Alternative Name set.
sudo certbot --nginx -d example.com -d www.example.com
sudo certbot --apache -d example.net -d www.example.net
The Nginx plugin locates the matching server block, adds TLS directives and reloads Nginx. The Apache plugin performs the equivalent operation for a matching virtual host. Review the proposed redirect and configuration changes before accepting them, especially when an application must remain reachable over HTTP for a special callback or health check.
Run the command separately for unrelated domains unless they intentionally share a certificate. A certificate containing several names is convenient, but adding or removing one name later affects the renewal set for that certificate. Keep each site’s certificate and private key permissions restricted to the service accounts that need them.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Use the installed Certbot tooling to inspect renewal configuration and perform a controlled renewal check. A successful configuration check or certificate issuance is not proof that a future renewal will succeed; retain working DNS, port 80 access and the same hostname mappings.
Run Nginx in front of Apache when sites need both
A mixed design gives Nginx public ownership of ports 80 and 443 while Apache listens only on an internal address such as 127.0.0.1:8080. Nginx can serve static sites directly and proxy selected hostnames to Apache.
- Configure Apache to listen on the internal address and port, not the public HTTP port.
- Create an Nginx server block for the Apache-backed hostname with a
proxy_passtarget such ashttp://127.0.0.1:8080. - Forward the original host and client information so the application can generate correct links and logs:
location / {
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://127.0.0.1:8080;
}
- Terminate TLS at Nginx, obtain the certificate with the Nginx Certbot plugin, and proxy only over localhost or a private network.
- Test both services independently, then test the public hostname and inspect Nginx and Apache logs for the same request.
This arrangement adds another failure point and another configuration layer. A port conflict, missing proxy header, incorrect Apache virtual-host match or blocked internal listener can look like an application outage, so document which service owns each hostname and port.
Isolation and security practices for a shared VPS
- Separate Unix access: use distinct deployment keys, users or groups where practical. A deployment account for one site should not automatically read another site’s environment file or private uploads.
- Keep secrets outside web roots: store database credentials, API keys and application environment files above the public directory, with restrictive permissions.
- Use separate databases and sockets: give each application its own database account, schema and PHP-FPM or application socket when possible.
- Limit writable paths: make only upload, cache or generated-content directories writable by the web process. Never make the entire document root world-writable.
- Control unknown hosts: define a deliberate default server or virtual host that returns a neutral response. Do not let an unmatched hostname expose the first site’s files.
- Protect administration: restrict SSH by source where possible, use keys rather than password login, apply security updates and avoid exposing database ports publicly.
- Separate logs and rotate them: per-site logs simplify incident response, but unbounded logs can fill the disk. Configure rotation and monitor free space.
- Back up configuration as well as content: include enabled-site links, certificates, scheduled jobs, databases, uploads and application configuration. Store copies outside the VPS.
Troubleshoot the common failure modes
| Symptom | Likely checks | Corrective action |
|---|---|---|
| The wrong site appears | Compare the requested hostname with server_name or ServerName; inspect the default site and DNS records. |
Correct the hostname spelling, remove conflicting aliases, disable an unintended default and reload after a syntax check. |
| Connection refused or timed out | Check that the service is running, listening on 80/443, and allowed through both host and provider firewalls. | Start the intended service, resolve port conflicts, open only required ports and retest. |
| HTTP works but HTTPS fails | Verify a certificate exists for the exact hostname, that port 443 is open and that the TLS server block or virtual host is enabled. | Run the matching Certbot integration, correct the hostname list and reload the service. |
| Certbot cannot validate a name | Check A/AAAA answers, port 80 reachability, redirects and whether the hostname is present in the active configuration. | Fix DNS, firewall or host matching first; then retry issuance. |
| 403 Forbidden | Inspect directory traversal permissions, file ownership, Apache <Directory> rules and Nginx root paths. |
Grant read and execute access to the web process without making files broadly writable. |
| 502 Bad Gateway in a mixed setup | Check that Apache is listening on the configured internal port and that Nginx’s proxy_pass target and headers are correct. |
Restart or reload the failed backend only after validating its configuration, then review both services’ error logs. |
| Changes do not appear | Confirm the edited file is enabled, the request reaches this VPS, caches are not masking the change and the reload completed. | Inspect enabled links, use a direct curl request and check service status and logs. |
Keep the last known-good configuration so a failed deployment can be rolled back quickly. A syntax check should precede every reload, including automated deployments.
Estimate capacity instead of counting domains
There is no authoritative number of websites that every VPS can host. Ten low-traffic static sites may use fewer resources than one busy application with background jobs and a database. Capacity depends on request rate, dynamic work per request, PHP-FPM or other worker counts, database load, cache hit rate, storage speed, log volume and traffic bursts.
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 glitchesMeasure the actual stack while it is under realistic load. Watch memory pressure and swap, CPU saturation, disk latency and free space, network throughput, web-worker queues, PHP-FPM or application process counts, database connections and slow queries. Set alerts before a resource reaches exhaustion, and leave capacity for kernel updates, certificate renewal, backups and unexpected spikes.
If one site repeatedly consumes resources or requires a different security boundary, move it to another VPS rather than allowing it to destabilize unrelated domains. Horizontal separation is also the recovery path when the shared failure domain becomes unacceptable.
Quick Recap
A repeatable operating procedure
- Record the domain names, aliases, document roots, application ports, Unix owners, databases and backup destinations in a small inventory.
- Create the root directory and permissions before uploading code.
- Publish and verify DNS records, including IPv6 only when it is functional.
- Write one Nginx server block or Apache virtual host per site, with unique roots and logs.
- Enable the intended files and remove accidental defaults or conflicting aliases.
- Run
nginx -torapachectl configtest; do not reload a failing configuration. - Reload the service, request every hostname with
curl, and inspect the corresponding logs. - Issue certificates with the appropriate Certbot plugin and verify that HTTPS serves the correct site.
- Check renewal configuration, backups, firewall rules, monitoring and disk headroom.
- Keep a rollback copy of the previous configuration and test restoration before the VPS becomes critical.
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.
