What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Yes. Put both sites behind one NGINX server block, keep the first site at /, and give the second site a distinct path such as /site2/. Route each path to its own WordPress front controller with try_files. Use WordPress Multisite when the sites should share one network and administration layer; use two standalone installations when you need independent databases, plugins, updates, backups, or failure boundaries. If the sites run on different machines or containers, proxy each path to its own upstream instead of serving both from the same PHP-FPM pool.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Choose the architecture before editing NGINX
The URL design determines nearly every later decision. A single domain can expose two WordPress sites in three practical ways:
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute- Multisite with subdirectory URLs: one WordPress network serves the main site and path-based subsites such as
example.com/subsite. - Two standalone installations: the first install owns the root path and a second install lives in a directory such as
/site2/, with its own database and administration area. - Separate upstream applications: NGINX remains the public entry point while each path is sent to a different VM, container, or internal web server.
Do not start by copying rewrite rules from an Apache setup. NGINX has no directory-level .htaccess or web.config equivalent. Permalink rewrites, PHP restrictions, redirects, caching, and security rules must be written in the NGINX configuration that the server administrator controls.
When Multisite is the better fit
Choose a path-based Multisite network when one organization wants shared WordPress core files, centralized updates, common user management, and a network dashboard. The sites remain separate in content and settings, but they operate inside one network and share the same core runtime. This can make administration efficient when the same team owns every site.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Check plugin and theme compatibility before converting an existing single site. Network activation rules, user roles, upload paths, and backup procedures differ from a normal single-site installation. A plugin that works on one standalone site may not support network activation or multisite-specific behavior.
When two standalone installations are safer
Use independent installations when each site needs its own database, plugin and theme set, update schedule, administrators, or restore process. A failure or risky update on one installation is less likely to affect the other. The trade-off is duplicated maintenance: each site needs its own WordPress files, PHP configuration, security review, backups, updates, and dashboard.
Free tools Windows power users keep installed
One-click scans. No signup required.
For this model, the first site normally remains at the document root, while the second site’s files are placed in a directory such as /var/www/example.com/site2. The public URL and filesystem directory do not have to use the same name, but keeping them clear and consistent reduces mistakes.
When separate upstreams are appropriate
Proxy each path to a separate upstream when the sites run in different containers, virtual machines, or internal web servers. This gives each application its own runtime and deployment lifecycle while NGINX handles TLS termination, host routing, and the public URL. The upstream WordPress configuration must still understand that its public address includes the correct scheme and path.
How NGINX matches the two sites
NGINX evaluates locations and then applies the matching PHP handler. The second site’s location must preserve the /site2/ prefix and fall back to that installation’s own index.php. The root site uses a separate fallback to the root /index.php.
A typical local layout looks like this:
server {
listen 80;
server_name example.com;
root /var/www/example.com/main;
index index.php;
location /site2/ {
try_files $uri $uri/ /site2/index.php?$args;
}
location / {
try_files $uri $uri/ /index.php?$args;
}
location ~ .php$ {
try_files $uri =404;
include fastcgi_params;
fastcgi_pass unix:/var/run/php/php8.3-fpm.sock;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
}
}The exact PHP-FPM socket, document root, user permissions, and file locations vary by operating system and hosting setup. Replace the example values rather than copying them unchanged.
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 →Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Why each directive matters
server_nameidentifies the public host handled by this block.rootpoints to the directory containing the root installation.location /site2/is more specific thanlocation /, so requests beginning with that path are handled by the second site’s routing rule.try_files $uri $uri/ /site2/index.php?$args;serves existing files and directories, then sends unknown pretty-permalink requests to the second site’s front controller while preserving the query string.- The root fallback sends other unknown requests to the first site’s
index.php. try_files $uri =404;in the PHP location prevents NGINX from passing a nonexistent script to PHP-FPM. This is an important guard against executing arbitrary path fragments.fastcgi_param SCRIPT_FILENAMEtells PHP-FPM which real file to execute. Its correct value depends on how the document root and URI are mapped.
Install a second standalone WordPress site in a subdirectory
1. Prepare the files and database
- Create the second document directory, for example
/var/www/example.com/site2, beneath the same web root or at a location your NGINX layout can safely expose. - Copy or install a separate WordPress codebase into that directory. Do not reuse the first site’s
wp-config.phpunless you intentionally configure a shared installation. - Create a separate database and database user for the second site. Independent credentials make permissions, backups, and restoration boundaries unambiguous.
- Set filesystem ownership and permissions so the NGINX/PHP-FPM account can read the files and WordPress can write only the directories that require uploads or updates.
A separate database is not strictly required by the web server, but it is the normal choice for standalone sites. Sharing tables or credentials makes an ostensibly independent installation harder to secure and restore.
2. Add the path-specific NGINX location
Add the /site2/ location inside the same server block as the root site. Keep the root site’s generic location as a fallback for everything else:
location /site2/ {
try_files $uri $uri/ /site2/index.php?$args;
}
location / {
try_files $uri $uri/ /index.php?$args;
}If you place additional locations in the server block, make sure a broader rule does not intercept /site2/ first. Static asset, cache, or security locations must be reviewed for the same prefix; otherwise requests for /site2/wp-content/ can accidentally be served or blocked using rules intended for site one.
3. Configure the second site’s public URLs
During installation, set both the WordPress Address and Site Address to the public scheme and path, for example https://example.com/site2. The values must match how visitors reach the site. A missing path commonly produces redirects to the root site, login loops, or CSS and JavaScript URLs that omit /site2.
If you must correct the values before the dashboard is reachable, use the site’s database or a temporary configuration override appropriate to your deployment process, then remove the override after saving the correct settings. Change one source of truth at a time so an old value does not keep forcing redirects.
4. Keep PHP handling guarded
Use one carefully tested PHP location for both installations when they share a PHP-FPM service:
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
location ~ .php$ {
try_files $uri =404;
include fastcgi_params;
fastcgi_pass unix:/var/run/php/php8.3-fpm.sock;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
}If the two sites require different PHP versions or pools, create separate upstream definitions and route them deliberately. Do not assume that a socket named php8.3-fpm.sock exists on your host; inspect the installed service and use its actual path.
Use WordPress Multisite with subdirectory URLs
A path-based network can expose the main site at the domain root and additional sites at paths such as example.com/subsite. WordPress’s Multisite setup requires network configuration in WordPress and more involved NGINX rules than a normal single site, particularly for network administration paths, wp-* requests, and PHP entry points.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →What changes operationally
- The network administrator manages sites, users, themes, and plugins from a central dashboard.
- WordPress core is shared, so a core update is a network-wide operational event rather than an isolated site update.
- Database tables are organized for the network and its sites instead of two wholly independent databases.
- Uploads for subsites use a site-specific path under
wp-content/uploads/sites/. - Backups must capture the network database, shared code, uploads, and configuration as a consistent set.
NGINX implications
The normal single-site fallback is not enough for every network request. The Multisite subdirectory pattern adds handling for paths such as /wp-admin, /wp-*, and PHP requests so a subsite resolves through the network’s front controller. Start from the current Multisite subdirectory rules for your WordPress version and adapt the filesystem paths; do not combine fragments from unrelated Apache and NGINX examples.
Before converting an existing site, verify that all required plugins support Multisite, that administrators understand network versus site roles, and that your backup system can restore one site without silently damaging the rest of the network. If you need strict independence, a standalone installation is usually the clearer boundary.
Proxy the second site to another server or container
When the second WordPress application is not stored under the same document root, NGINX can forward only its path to an upstream:
upstream wordpress_site2 {
server 127.0.0.1:8082;
}
server {
listen 80;
server_name example.com;
location /site2/ {
proxy_pass http://wordpress_site2/;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}
This is a conceptual pattern. The trailing slash on proxy_pass affects how NGINX rewrites the URI sent upstream, so test whether the upstream expects requests with or without the /site2/ prefix. The backend’s WordPress URL settings, web-server routing, cookie path, and canonical redirects must agree with that choice.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Forwarded headers and HTTPS
Pass the original host and scheme so WordPress can generate canonical URLs and secure redirects correctly. Configure the upstream application to trust those forwarded values only from your proxy. If it does not, HTTPS requests may be treated as HTTP, causing redirect loops, mixed-content URLs, or cookies without the expected secure behavior.
Cookies, cache, and asset paths
Log in and out through the public URL, not the internal upstream address. Check cookie domains and paths, cache keys, REST endpoints, media URLs, and redirects. A proxy that returns correct HTML can still fail when CSS, JavaScript, login cookies, or uploaded media use an internal hostname or omit /site2/.
Complete implementation sequence
- Select the model: decide between Multisite, two standalone installations, or separate upstream applications based on administration and isolation requirements.
- Plan the URL: reserve a path such as
/site2/. Check that no existing page, API endpoint, language prefix, or cache rule already owns that path. - Prepare the application: create the second filesystem directory and database for a standalone site, or create the network/subsite in WordPress. For a proxy, deploy the second application and record its internal address.
- Write one server block: keep the domain in one NGINX
serverblock unless you have a specific reason to split TLS or host handling. - Add the specific route: configure
/site2/before or alongside generic rules so it falls back to the correct front controller or upstream. - Configure PHP or proxy headers: use guarded FastCGI handling for local files, or forward
Host,X-Forwarded-For, andX-Forwarded-Protofor a proxied application. - Set WordPress addresses: include the public scheme and
/site2path for the second site. Ensure the root site continues to use the root URL. - Validate before reload: run your distribution’s NGINX configuration test command, commonly
nginx -t, and fix every reported error. - Reload safely: reload NGINX rather than stopping it, then watch the error and access logs while making requests to both sites.
- Run the full verification checklist: test anonymous pages, authenticated sessions, assets, uploads, redirects, and pretty permalinks before announcing the second site.
Verification checklist
Routing and permalinks
- Open the root site’s home page and a nested pretty permalink.
- Open
/site2/and a nested pretty permalink owned by the second site. - Request a real static file from each installation and confirm it is served by the correct directory.
- Confirm that an unknown path under
/site2/is handled by site two rather than the root site’s front controller.
Administration and sessions
- Open
/site2/wp-admin/, sign in, visit the dashboard, and sign out. - Confirm that login redirects stay on the intended host and path.
- Verify that cookies from one site do not unexpectedly authenticate or log out the other.
Assets and uploads
- Load the second site’s CSS and JavaScript from its public path.
- Upload an image, insert it into content, and open the resulting media URL.
- Check that
/site2/wp-content/never falls through to site one. - For Multisite, verify that a subsite’s uploads use the expected
wp-content/uploads/sites/structure.
Proxy-specific checks
- Inspect the upstream’s received
Hostand forwarded scheme. - Check canonical redirects, secure cookies, REST requests, and cache behavior through the public URL.
- Temporarily bypass or vary caches while testing so a stale response does not hide a routing error.
Common failures and precise fixes
The second site’s URLs redirect to the root
Usually the WordPress Address or Site Address omits /site2, or a proxy is stripping or adding the path incorrectly. Correct both WordPress URL values, inspect the Location response header, and compare the public request path with the URI sent to the upstream.
Every pretty permalink returns 404
Check that the /site2/ location contains try_files $uri $uri/ /site2/index.php?$args;, that the file exists at the configured document root, and that the PHP location is not rejecting the rewritten script. Flush WordPress permalinks only after NGINX routing is correct; WordPress cannot write the missing NGINX rules for you.
PHP source downloads or scripts fail
Verify that the PHP location is active, that fastcgi_pass points to a running PHP-FPM socket, and that SCRIPT_FILENAME resolves to the real file. A syntax-valid NGINX configuration can still reference a nonexistent socket or an incorrect filesystem path.
CSS and JavaScript load from the wrong site
Inspect the generated HTML for missing /site2/ prefixes. Correct the WordPress URL values, then review any hard-coded theme or plugin URLs and cache entries. Ensure a broad static-file location is not rewriting or aliasing the second site’s assets into the root directory.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Login loops occur behind a proxy
Check the forwarded scheme, secure-cookie handling, and canonical URL settings. The backend must know that the client connected over HTTPS when TLS terminates at NGINX. Also verify that the cookie path covers /site2/ and that the proxy is not caching login responses.
One site’s changes affect the other
This is expected for shared Multisite core and network-level operations, but not for two properly isolated standalone installations. Confirm database credentials, filesystem paths, PHP pools, object-cache namespaces, and deployment scripts. A shared cache or an accidentally shared wp-config.php can erase the isolation you intended.
Outdated 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 matchPC 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 & 11Administration, isolation, and backup trade-offs
| Decision area | Multisite subdirectories | Two standalone installations | Separate upstreams |
|---|---|---|---|
| Administration | One network dashboard with network and site-level roles | Separate dashboards and administrators | Depends on how each upstream is managed |
| Core and updates | Shared WordPress core; network-wide operational impact | Independent code and update schedules | Independent runtimes and deployments |
| Databases | One network database structure | Separate databases are the normal isolation boundary | Each upstream controls its own database design |
| Failure scope | A network-level change can affect multiple sites | Failures are more naturally contained per installation | Proxy, network, and upstream failures add another layer |
| URL model | Subdirectory, subdomain, or mapped external domain | Subdirectory under the shared domain | Any public path that the proxy and backend agree on |
| NGINX access | Required for network routing and security rules | Required for both path routing and PHP handling | Required for proxy locations and forwarded headers |
| Backup scope | Back up network database, shared code, and all site uploads consistently | Back up each database, codebase, uploads, and configuration independently | Back up each upstream plus the proxy configuration |
Choose the model that matches the failure boundary you can actually operate. Central administration is valuable only if your team accepts shared core updates and network-wide maintenance. Independence is valuable only if you maintain separate credentials, backups, monitoring, and patch schedules.
Domain mapping after a path-based start
A Multisite network that begins with URLs such as example.com/subsite1 can later present a subsite on its own top-level domain through domain mapping. The mapped domain does not remove the need for correct network routing, TLS, DNS, canonical URLs, and cookie testing. Treat it as an additional public address for the same subsite rather than as a new standalone installation.
Security and maintenance requirements
- Keep NGINX, PHP, WordPress core, themes, and plugins patched on schedules appropriate to their exposure.
- Never pass arbitrary filenames to PHP; retain a guarded script check such as
try_files $uri =404. - Limit write permissions to upload and cache directories wherever possible.
- Use separate database users and credentials for standalone sites.
- Review access logs for requests crossing the
/site2/boundary or probing another installation’s files. - Back up NGINX configuration along with WordPress files, databases, uploads, and secrets. Test restoration rather than assuming a successful backup job is recoverable.
- Document which team owns NGINX. WordPress administrators cannot add or repair server-level rewrite rules from the dashboard.
What the finished setup should look like
One request to https://example.com/ reaches the first installation and falls back to its root index.php. A request to https://example.com/site2/ reaches the second installation, whose files and pretty permalinks fall back to /site2/index.php, or is proxied to the second upstream. PHP requests are validated before FastCGI execution, and WordPress generates URLs using the same public scheme and path that visitors use.
If those four conditions hold—and your login, media, assets, redirects, and backups have been tested—you can run two WordPress sites under one domain without making the second site appear to be part of the first site’s filesystem or URL space.
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.
