Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix 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
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Run each WordPress site as its own Docker Compose project, with a dedicated WordPress container, database container, and named volumes. Put one reverse proxy such as Traefik in front of all projects on a shared external network; keep every database on its project’s private network. This gives you separate updates, backups, rollbacks, and domain routing without running a separate VPS for every site.
The procedure below covers DNS, Compose files, HTTPS, persistent storage, migration, backups, updates, scaling limits, and the failure modes that commonly take sites offline.
The architecture that works for multiple sites
Use one Compose project per independent site. A project contains two core services:
- WordPress: the PHP application and web server.
- MariaDB or MySQL: the site’s database, reachable only over the project network.
Attach the WordPress service to two networks. Its private project network connects it to the database. Its shared proxy network connects it to Traefik, NGINX, Caddy, or another reverse proxy. The proxy selects a site by the incoming host name, terminates TLS, and forwards the request to the correct WordPress container.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
Do not route traffic by container IP address. Docker assigns container IP addresses dynamically whenever a container starts or is recreated. Compose service names, such as db, are the stable DNS names that applications should use.
| Component | Network visibility | Purpose |
|---|---|---|
| Reverse proxy | Shared proxy network and public ports 80/443 | Domain routing, HTTPS, redirects, and access logging |
| WordPress service | Private site network plus shared proxy network | Runs PHP and serves the site |
| Database service | Private site network only | Stores posts, users, settings, and plugin data |
| Named volumes | Host-managed Docker storage | Preserve WordPress files and database files across container replacement |
Separate Compose projects or WordPress Multisite?
For unrelated client sites, separate projects are usually the safer operational boundary. A failed update, damaged plugin, or database restore then affects one site rather than a shared installation. You can deploy, stop, back up, and roll back one project without coordinating every other site.
| Decision factor | Separate Compose projects | WordPress Multisite |
|---|---|---|
| Isolation | Each site has its own application and database containers. | Sites share one WordPress installation and commonly share operational failure modes. |
| Update independence | Update plugins, themes, WordPress, or images per project. | Core and network-wide components are managed together. |
| Backup and restore | Restore one SQL dump and one file volume without touching other sites. | Granularity depends on the multisite backup tooling and database layout. |
| Domain routing | Reverse-proxy host rules map each domain to a project. | Multisite domain mapping and the web-server configuration must agree. |
| Operational overhead | More Compose files, volumes, and update jobs to maintain. | Fewer containers, but more shared configuration and coordination. |
Choose Multisite when the sites are managed as one network with shared administrators, themes, and release cycles. Choose separate projects when ownership, release schedules, plugins, or recovery requirements differ. Multisite has an important deployment constraint: the official Docker sample notes that it works only on ports 80 and 443, so it is not a substitute for arbitrary per-site application ports behind a proxy.
Prerequisites on the VPS
- A supported Linux VPS with a public IPv4 address (and IPv6 if you intend to publish it).
- Docker Engine and the Docker Compose plugin installed from the distribution or Docker’s supported packages.
- Administrative access for installing Docker, creating networks, and opening the firewall.
- One DNS name per site, with permission to create or edit its A record.
- A backup destination outside the VPS, such as object storage, another server, or an offline copy.
There is no single authoritative CPU or memory number that fits every portfolio. Traffic, page caching, PHP workers, plugins, media processing, and database queries determine capacity. Start with monitoring enabled and leave enough memory for the operating system, Docker, the proxy, databases, and burst traffic. Increase the VPS before memory pressure causes the kernel to terminate containers.
Plan directories, names, and networks
Create a directory for each site and give each Compose project a unique name. A simple layout is:
/opt/wordpress-sites/site-a/compose.yml
/opt/wordpress-sites/site-a/.env
/opt/wordpress-sites/site-b/compose.yml
/opt/wordpress-sites/site-b/.envUse one shared external network for the proxy. Create it once, before deploying any site:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
docker network create traefik-networkEach project defines its own private backend network. If the proxy network is declared external, its name must match the network you created; Compose will not create an external network for you.
Build a Compose file for each site
Copy the following pattern into each site directory and change the domain, project name, and secrets. The WordPress image mounts /var/www/html; the database image mounts /var/lib/mysql. Named volumes are deliberately used instead of container-layer storage.
services:
db:
image: mariadb
restart: unless-stopped
environment:
MYSQL_DATABASE: wordpress
MYSQL_USER: wordpress
MYSQL_PASSWORD: ${DB_PASSWORD}
MYSQL_ROOT_PASSWORD: ${DB_ROOT_PASSWORD}
volumes:
- db_data:/var/lib/mysql
networks:
- backend
wordpress:
image: wordpress
restart: unless-stopped
depends_on:
- db
environment:
WORDPRESS_DB_HOST: db:3306
WORDPRESS_DB_USER: wordpress
WORDPRESS_DB_PASSWORD: ${DB_PASSWORD}
WORDPRESS_DB_NAME: wordpress
volumes:
- wp_data:/var/www/html
networks:
- backend
- proxy
labels:
- traefik.enable=true
- traefik.http.routers.site-a.rule=Host(`site-a.example`)
- traefik.http.services.site-a.loadbalancer.server.port=80
volumes:
wp_data:
db_data:
networks:
backend:
internal: true
proxy:
external: true
name: traefik-networkThe database host is db:3306, not a numeric IP. Compose registers the service name db on the private network and updates its address automatically if the container is recreated.
Store secrets in the project’s .env file or, preferably, a secrets manager with permissions that prevent ordinary users from reading it. Do not commit database passwords to source control. Use long, unique values for the database user password and root password.
Free tools Windows power users keep installed
One-click scans. No signup required.
Image names in the example are intentionally generic. For production, select a tested WordPress and MariaDB/MySQL tag or digest and record it in version control. Avoid allowing an unattended deployment to change images merely because a registry’s latest tag moved.
Install and configure the reverse proxy
Run one reverse-proxy project on the VPS and attach it to traefik-network. The proxy listens publicly on ports 80 and 443. Each WordPress service joins the same network and carries labels or configuration that identify its host name and internal port.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Host-based routing
For a request to site-a.example, the proxy matches the host rule and forwards to the service named by that project’s labels. A request to site-b.example follows a different rule and reaches the second project. No public database port is needed, and WordPress containers do not need distinct host ports.
HTTP to HTTPS and forwarded headers
Configure the proxy to redirect HTTP to HTTPS and to obtain certificates through its supported certificate resolver. DNS must resolve to the VPS before automated certificate issuance can succeed. Docker’s deployment guidance warns that a new A record may take a few minutes to 48 hours, and occasionally longer, to propagate.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteWhen TLS terminates at Traefik, NGINX, Caddy, or another proxy, WordPress must receive the original protocol in the X-Forwarded-Proto header. The official WordPress image documents this requirement for reverse-proxy HTTPS; without it, WordPress can generate HTTP links, create redirect loops, or mark secure cookies incorrectly.
Protect the proxy dashboard
If you enable a proxy dashboard or API, keep it off the public internet unless it is protected by authentication and restricted by network policy. A dashboard that exposes routing or certificate details without access control is an avoidable attack surface.
Point domains at the VPS
- Create an A record for each domain, such as
site-a.exampleandsite-b.example, pointing to the VPS public IPv4 address. - If you publish IPv6, create matching AAAA records and verify that the VPS firewall and proxy listen on IPv6.
- Wait for DNS to resolve from an external network. Check with your DNS provider’s tools or
dig; do not assume that a local cached result represents global propagation. - Deploy the proxy and the site project only after the hostname resolves to the correct server, or be prepared to retry certificate issuance after propagation.
Do not point several unrelated domains at one WordPress container unless that is intentional. Host rules, WordPress site URLs, canonical redirects, and certificate names must all agree.
Deploy each project
- Change to the site directory:
cd /opt/wordpress-sites/site-a. - Review the Compose configuration and environment values:
docker compose config. This catches malformed YAML and missing substitutions before containers start. - Start the project with a unique name:
docker compose -p site_a up -d. A separate project name prevents similarly named resources from colliding. - Check container state:
docker psanddocker compose -p site_a ps. - Follow logs for a service that is not healthy:
docker compose -p site_a logs -f wordpressordocker compose -p site_a logs -f db. - Open the domain over HTTPS and complete the WordPress installer. Confirm that uploads, permalinks, login cookies, and an administrator login work before importing content or enabling plugins.
Repeat the same sequence in the second site directory, changing only its project-specific domain, secrets, and volume names. The proxy network is shared; the backend network and volumes remain project-scoped.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Persistence: what survives a container update
Containers are replaceable. The named volumes are the durable state. When you run docker compose up, Compose creates a declared volume if it does not exist and reuses it on later deployments. Recreating a WordPress or database container therefore leaves files and database pages in place.
docker compose down stops and removes the project’s containers and networks but preserves named volumes. Never add --volumes casually: docker compose down --volumes removes the project’s stored volumes and can destroy the site database and uploaded files.
Keep the database off the public network. A custom frontend/backend network arrangement lets the proxy reach WordPress while the database remains unreachable from the proxy and the internet.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Back up both the database and WordPress files
A database dump alone cannot restore media uploads, themes, plugins, or generated files. A file copy alone cannot restore posts, users, settings, or orders. Schedule both layers and store the results outside the VPS.
Export the database
From the project directory, create a logical SQL dump using the database container’s credentials:
docker compose -p site_a exec -T db sh -c 'mysqldump -u"$MYSQL_USER" -p"$MYSQL_PASSWORD" "$MYSQL_DATABASE"' > site-a.sqlTest that the output is non-empty and retain a timestamp in the backup filename. Protect SQL files because they contain user data and may include password-reset or payment-related information.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Copy the WordPress volume
Archive the persistent files from the named volume. The exact volume name includes the Compose project name unless you explicitly set one, so inspect it with docker volume ls first:
docker volume ls | grep site_a
docker run --rm
-v site_a_wp_data:/from:ro
-v "$PWD":/to
alpine tar czf /to/site-a-wp-files.tgz -C /from .Use your actual volume name in the command. Back up uploads frequently; they change independently of application image updates.
Verify and rehearse recovery
- Keep several dated generations rather than overwriting one backup.
- Encrypt backups in transit and at rest.
- Periodically restore a SQL dump and file archive into a temporary project on a non-public network.
- Record the Compose file, image tags, environment variable names, and WordPress URL for each site.
- Measure how long restoration takes; that is more useful than merely having a backup job that reports success.
Migrate an existing WordPress site into Docker
- Lower the existing site’s DNS TTL before the migration window if your provider permits it.
- Put the old site into maintenance mode or schedule a brief write freeze so the final database export contains all recent changes.
- Export the existing database with
mysqldumpor an equivalent tool and copy the complete WordPress directory, includingwp-content/uploads, plugins, themes, and the existing configuration file for reference. - Deploy the new Compose project with empty named volumes and confirm that the database service is reachable as
db. - Copy the SQL dump into the MariaDB container or mount it temporarily, then import it. Docker’s migration procedure uses this export-copy-import sequence.
- Copy the WordPress files into the persistent
/var/www/htmlvolume. Preserve ownership and permissions expected by the image. - Set the container environment variables or update
wp-config.phpso the database name, user, password, and host match the Compose service. The host should be the service name, not the old server address. - Check the site URL, HTTPS behavior, serialized settings, cron jobs, and any hard-coded references to the old domain. Run a search-and-replace tool that understands serialized WordPress data rather than editing SQL with plain text.
- Test the new site through a temporary hostname or local hosts-file entry before changing public DNS.
- At cutover, stop writes on the old site, take one final database and file backup, import the delta if necessary, then change DNS and monitor logs.
Do not delete the old hosting copy until DNS has stabilized and the Docker deployment has passed a complete restore or rollback check.
Updating WordPress, plugins, and container images
Run updates per project so one site can be tested without changing another:
- Take a fresh SQL dump and file backup.
- Review the image tag or digest change and read the image’s release notes.
- Pull the selected images:
docker compose -p site_a pull. - Recreate changed services while retaining volumes:
docker compose -p site_a up -d. - Check
docker compose -p site_a ps, application logs, the WordPress dashboard, front-end pages, media uploads, and scheduled jobs. - If the release fails, restore the previous image tag and volume/database backup rather than repeatedly restarting a broken container.
The official WordPress image notes that additional PHP extensions may require a custom image built with FROM wordpress. Build and test such an image separately; do not install extensions manually into a running container and expect them to survive recreation.
Recommended Free Tools
Scaling limits on a single VPS
Compose can start multiple replicas of a WordPress service with docker compose up --scale wordpress=2, but replicas introduce state-sharing requirements. Every replica must see the same uploaded media, and any session or cache state that is not stored in the database must be externalized or shared. A local named volume mounted independently into two containers is not automatically a shared, conflict-safe filesystem.
For a small portfolio, independent single-instance projects are generally easier to back up, troubleshoot, and roll back than a horizontally scaled cluster. Scale only after measuring a real bottleneck and designing shared media, session handling, database capacity, and proxy load balancing.
Troubleshooting by symptom
The site shows a proxy 404 or the wrong site
- Confirm the request’s host name exactly matches the proxy rule, including the non-
wwworwwwvariant you intend to serve. - Check that the WordPress service is attached to the shared proxy network.
- Inspect proxy labels or configuration for a typo in the service name or internal port.
- Verify that DNS points to this VPS rather than an old server.
WordPress cannot connect to the database
- Use
db:3306as the database host, not a container IP. - Check that the database container is running and review its logs for initialization errors.
- Compare
WORDPRESS_DB_NAME,WORDPRESS_DB_USER, and passwords with the MariaDB environment values. - Ensure both services share the private backend network.
HTTPS redirects loop or links are HTTP
- Confirm the proxy forwards
X-Forwarded-Proto: httpsfor secure requests. - Check WordPress’s site URL and home URL for the intended HTTPS address.
- Remove conflicting redirect rules in a plugin, proxy, or web-server configuration.
Uploads disappear after a redeploy
- Verify that
/var/www/htmlis mounted to the expected named volume. - Check that the Compose project name did not change, which can create a different project-scoped volume.
- Use
docker volume lsanddocker volume inspectbefore removing anything. - Do not run
docker compose down --volumesunless you intentionally want to erase stored data.
Certificate issuance fails
- Wait for DNS propagation and verify the A/AAAA records from outside the VPS.
- Make sure ports 80 and 443 reach the proxy through the VPS firewall and cloud security group.
- Check that another service is not already binding those ports.
- Review proxy logs for rate limits, invalid host names, or challenge failures.
Security and maintenance checklist
- Expose only the proxy’s public ports; do not publish database ports to the internet.
- Use unique database credentials per site and restrict access to environment files.
- Keep Docker, the host kernel, WordPress, plugins, themes, and proxy images patched.
- Pin image tags or digests and test updates before applying them to every project.
- Enable automatic security updates for the host where appropriate, with a rollback plan.
- Use HTTPS for every public domain and redirect HTTP consistently.
- Limit administrative access with SSH keys, least-privilege accounts, and firewall rules.
- Monitor disk usage, memory, container restarts, certificate expiry, backup age, and database errors.
- Test restoration, not merely backup creation.
When this design is the right fit
This pattern suits agencies, freelancers, and small publishers running several low-to-moderate traffic WordPress sites on one VPS. It combines site-level isolation with one shared ingress layer and avoids exposing databases. It is less suitable when sites require strict regulatory isolation, independent operating-system kernels, very high availability, or sustained traffic that exceeds one server’s capacity; those requirements call for a broader infrastructure design.
The essential operating rule is simple: treat every site as an independently deployable application, treat the proxy network as shared ingress, and treat named volumes plus verified SQL and file backups as the data boundary. With those boundaries in place, adding a second or tenth domain is a repeatable deployment rather than a risky container experiment.
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.
