Free tools Windows power users keep installed
One-click scans. No signup required.
Coolify can deploy one application image to a primary server and one or more additional standalone servers. Each destination runs its own instance; attaching servers does not balance requests. To serve users from all instances, place an external load balancer or cloud traffic service in front of them, with health checks and routing configured separately from Coolify.
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
What a Coolify multi-server deployment actually does
In a multi-server deployment, Coolify keeps one application definition but starts that application on several independent Docker hosts. One host is designated the Primary Server. Other validated hosts are attached as additional servers. During deployment, the primary server (or a configured build server) creates the container image and publishes it to a registry. Each additional server pulls that exact image and runs its own copy.
As an Amazon Associate I earn from qualifying purchases.
The arrangement gives you multiple application instances, not a built-in cluster. Coolify’s dashboard remains the control plane: it connects to each host over SSH and performs Docker operations there. User traffic does not pass through the dashboard. Requests go directly to the reverse proxy and application on whichever resource server your DNS or external load balancer selects.
- What is shared: the application definition, image version, deployment action and rollback target.
- What is independent: container processes, local container filesystems, reverse-proxy listeners and host resources on each server.
- What is not supplied by Coolify: request distribution, DNS failover, TLS termination at the edge, health-check policy, firewall rules, monitoring or capacity alerts.
Coolify documentation describes the feature as deploying the same application to a primary server and additional standalone servers, and separately notes that adding deployment servers does not distribute traffic by itself. Treat the feature as an orchestration and release mechanism; treat traffic management as a separate infrastructure layer.
#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.
Decide whether you need more than one server
A second server adds capacity and failure isolation, but it also adds state-management and networking work. Coolify recommends starting with the smallest setup that meets measured capacity or availability requirements. Compare the trade-offs before attaching another destination.
| Consideration | Single server | Multi-server deployment |
|---|---|---|
| Operational simplicity | One host, one proxy and one place to inspect logs. | Every release and incident spans multiple hosts; each must remain reachable and correctly configured. |
| Capacity | Limited by the CPU, memory, storage and network capacity of one server. | Runs additional instances, allowing traffic and compute work to be spread when an external balancer is present. |
| Failure isolation | A host failure takes the application offline unless another recovery path exists. | A healthy instance can continue serving if routing removes an unhealthy host, but the routing layer must be configured to do that. |
| Traffic routing | DNS can point directly to the server or its proxy. | Requires a cloud or external load balancer, health checks and a defined origin path for every server. |
| Application state | Local files and in-process sessions may appear to work. | Sessions, uploads, queues, caches and other mutable state must be external and reachable by every instance. |
| Build and registry work | The host can build and run the image locally. | The built image must be published to a registry accessible to the builder, primary server and every additional server. |
| Infrastructure cost | One server and its associated services. | Additional servers plus load-balancing, shared database/storage and monitoring costs. |
Horizontal deployment is most useful when you have a stateless web or API process, a clear health endpoint and a reason to tolerate host failure or handle more concurrent work. It is not a substitute for optimizing a single instance or for designing a database and storage layer that can safely be shared.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Prerequisites to satisfy before attaching a server
Validate every destination in Coolify
Each host must be validated in Coolify and configured as a standalone Docker destination. Resolve SSH authentication, Docker availability and host-level connectivity before adding it to the application. A server that has not passed validation should not be used as a production destination.
Keep CPU architecture consistent
Use the same CPU architecture on all participating hosts, such as AMD64 on every server or ARM64 on every server. An image built for one architecture may not run on a host using another unless you have deliberately built and published a compatible multi-architecture image. The documented multi-server workflow expects architectural consistency, so standardize the fleet before deployment.
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
Use one reverse-proxy type on proxied hosts
If a reverse proxy is enabled, use the same proxy type on every proxied server: Traefik on all of them or Caddy on all of them. A server without a proxy can still be attached, but you must account for its different ingress path when configuring your external router, TLS and health checks.
Make the application stateless at the container level
Every instance must be able to start from the same image and configuration without relying on files written by another instance. Move mutable data to services reachable from every server:
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 match- Store login sessions in a shared session service or database rather than process memory.
- Put user uploads and generated assets in shared object or network storage, not a container filesystem.
- Use a shared queue for background jobs and make workers safe to run on more than one host.
- Place caches in a shared cache service, and design cache misses so a new instance can recover.
- Use a database endpoint accessible from all application servers, with credentials and network rules that are identical where appropriate.
Expose a health endpoint that represents application readiness, not merely whether a process exists. The load balancer should be able to remove an instance that cannot reach required dependencies. Also verify that every host can run the same environment variables, secrets, feature flags and image tag.
Understand the storage and Compose limitations
The current multi-server deployment feature cannot be used for an application with persistent storage configured in Coolify. Docker Compose applications cannot be attached through the application’s Servers page either. If your workload depends on a persistent volume or is defined as a Compose application, do not assume that selecting another server will replicate it safely. Redesign the state layer and use a deployment model supported by your Coolify version, or keep that workload on a single appropriate destination.
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)
Prepare a registry reachable by every participant
Create a repository in a Docker registry that the primary server, optional build server and every additional destination can access. Authenticate the SSH user configured in Coolify to that registry on each host that must push or pull. Check both directions: the build path must be able to push the image, and each runtime host must be able to pull it through its firewall, DNS and registry credentials.
Set up the application and attach additional servers
The following procedure uses Coolify’s application interface. Labels can vary slightly by release, but the workflow is the same: publish one image, select validated standalone destinations and then deploy.
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 →- Choose the image repository. Open the application and go to General. Set Container image to the full name of the registry repository, including the registry host and repository path. Save the application settings. Use a repository name that every participating host can resolve and authenticate to.
- Open the server selector. Go to the application’s Servers page. Under Add another server, choose a server that has already passed Coolify validation and is configured as a standalone Docker destination.
- Repeat for each destination. Add one server at a time and confirm its architecture, proxy choice and registry access. The original destination remains the Primary Server; adding another server does not replace it.
- Start a deployment. Deploy the application from Coolify. The primary server, or the build server you configured, builds the image and pushes the published tag to the registry. Additional destinations pull that published image instead of rebuilding it locally.
- Watch every deployment log. Follow the deployment output until each attached server reports a running application. A successful build on the primary server is not proof that a pull, extraction or container start succeeded elsewhere.
- Verify each origin directly. Test every server through the origin path you intend to place behind your router. Confirm the expected status from the health endpoint, application behavior, database access, session handling and asset retrieval on each instance.
- Add origins to your external traffic layer. Only after direct tests pass, add the servers to your cloud or external load balancer. Configure DNS, TLS termination, firewall or security-group rules, health checks, monitoring and capacity alerts in that layer and in your infrastructure tooling, not in the Coolify dashboard.
Because additional servers consume the image published by the primary deployment, the commit, rollback target and image tag are intended to match across the attached destinations. Keep deployment tags immutable where your registry policy allows it, and record which tag was promoted so an incident can be reproduced.
Configure traffic distribution outside Coolify
Coolify does not create or manage the external load balancer. Select a router that can send requests to each server’s reachable origin and remove an origin when its health check fails. The exact controls depend on your provider, but the design decisions are the same.
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
Define the origin contract
- Choose whether the balancer connects to HTTP or HTTPS on each server and where certificates terminate.
- Use the same application hostname and expected headers on every origin so redirects and secure-cookie behavior do not vary by server.
- Expose a health path that returns success only when the instance is ready to serve. Keep it lightweight and avoid reporting healthy while critical dependencies are unavailable.
- Set firewall and security-group rules to allow the balancer’s source addresses while denying unintended public access to administrative ports.
Plan DNS and TLS
Point the public DNS record at the traffic layer rather than at one application server when the balancer provides a stable endpoint. Decide where TLS terminates and ensure the application receives the correct forwarded-protocol and host information. If TLS terminates separately on each origin, install and renew certificates on every server instead.
Recommended Free Tools
Add monitoring and capacity alerts
Monitor health-check state, response codes, latency, CPU, memory, disk and registry-pull failures per host. Alert when an instance is removed from service, when the remaining capacity is shrinking or when a deployment leaves servers on different image tags. Coolify can operate the deployment, but it does not replace these edge and host-level controls.
How deployments, stops and promotions behave
Application-wide actions
Normal application-wide deploy, restart and stop actions include all attached servers. A stop operation attempts every server even if one destination is unreachable, so inspect the result for each host rather than treating one connection failure as proof that all instances stopped.
Per-server actions
The application’s Servers page lets you deploy to, stop, promote or remove an individual attached server. Use a per-server deployment for controlled maintenance or to recover one host without unnecessarily interrupting the others. Removing a server from the application does not by itself erase external DNS or load-balancer membership; remove the origin from those systems as well.
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.
Promoting a server
Promoting an additional server makes it the primary server and demotes the former primary. Before promotion, verify that the candidate has the correct registry credentials, secrets, proxy configuration and build or deployment permissions. After promotion, confirm which host will build and publish future images, then test a normal deployment.
Pull-request previews
A pull-request preview is not deployed to additional destinations. Do not use a preview result as evidence that every production server received the same image; perform a production deployment and inspect each destination’s logs.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.State, sessions and releases across instances
The most common multi-server failures are application-design failures rather than Coolify failures. A request can land on any instance after every load-balancer decision, so code must not depend on a previous request reaching the same process.
- Sessions: use a shared session store or stateless, verifiable tokens. In-memory sessions can make users appear logged out when routing changes.
- Uploads: write to shared storage and make object names collision-safe. A file written only to server A will not exist when a later request reaches server B.
- Jobs: use a shared queue and idempotent handlers. Retries and duplicate delivery must not corrupt records.
- Database migrations: coordinate migrations so old and new application instances can coexist during rollout. Do not assume that deploying simultaneously means every request switches at one instant.
- Cache invalidation: either share the cache or tolerate independent caches and define how updates become visible across instances.
- Secrets and configuration: keep values consistent, rotate them deliberately and verify that every destination received the intended revision before routing traffic to it.
Persistent volumes configured directly for the application are excluded from the current feature. If data must survive container replacement, provide that durability through an external service designed for multi-host access rather than treating a local Docker volume as replicated storage.
Troubleshoot common failures
| Symptom | Likely cause | What to check |
|---|---|---|
| An additional server never starts the release. | The host cannot pull the image. | Registry login for the Coolify SSH user, repository permissions, DNS resolution, outbound firewall rules and the exact image tag in the deployment log. |
| Build succeeds but one host reports an exec-format or architecture error. | CPU architectures differ. | Confirm every host is AMD64 or every host is ARM64, then publish an image compatible with the fleet before redeploying. |
| Requests reach only one instance. | No external router is distributing traffic, or DNS still points at one origin. | Inspect the public DNS target, balancer membership and health-check state. Attaching a server in Coolify does not change routing. |
| Users lose sessions intermittently. | Sessions are stored in one process or on one local filesystem. | Move session state to a shared service or use a stateless session design, then test while sending requests to different origins. |
| Uploaded files appear on some requests but not others. | Files are stored in a container filesystem or host-local volume. | Move uploads to storage reachable by every instance. The current feature does not support applications with Coolify persistent storage configured. |
| One origin is healthy according to the balancer but returns application errors. | The health check tests only a listening port. | Use an application readiness endpoint that checks the dependencies required to serve real requests. |
| A Compose application cannot be attached from the Servers page. | Compose applications are outside this attachment workflow. | Keep the Compose workload on its supported destination or adopt a deployment approach that explicitly supports its topology. |
| A proxy behaves differently on different hosts. | Proxied servers use different proxy types or configuration. | Standardize on Traefik or Caddy for all proxied destinations and compare host-specific settings. |
| A stop or restart appears incomplete. | One or more hosts were unreachable. | Review per-server results; application-wide actions attempt every attached host but cannot operate a server that is unavailable. |
Security and operations checklist
- Use a dedicated, least-privileged SSH identity for each Coolify connection and protect its private key.
- Authenticate the same Coolify SSH user to the registry on every host that pulls or pushes images.
- Restrict registry, database, cache and storage access to the required server networks.
- Keep proxy, TLS, forwarded-header and hostname behavior consistent across origins.
- Make image tags and rollback targets auditable; record the tag running on every server after a release.
- Test a complete origin failure by removing one server from service and confirming that the external router stops sending it traffic.
- Test recovery: restore the host, validate it in Coolify, pull the intended image and re-enable it only after health checks pass.
- Monitor the shared state services as carefully as the application hosts; a database or storage outage can make every instance unhealthy.
- Keep capacity headroom for the loss of one server if availability is a goal. The number of servers and their required headroom depends on your measured workload, not on a fixed Coolify setting.
When a single server is the better design
Stay with one server when the application requires local persistent volumes, is packaged as a Compose application that cannot be attached through the Servers page, or has not yet been made stateless. A single destination is also preferable when your measured workload fits comfortably and you do not want to operate a separate load balancer, shared state services and multi-host monitoring.
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 glitchesMove to multiple servers when you can run identical instances, publish one accessible image, externalize mutable state and operate health-checked routing. Add one destination at a time, validate it directly, then put it behind the traffic layer. This staged approach lets you identify registry, proxy, state or firewall problems before they affect every origin.
Quick Recap
Key takeaways
- Coolify’s feature deploys identical application instances to a primary server and additional standalone Docker servers.
- It does not load-balance requests; an external load balancer or equivalent routing service is required.
- All servers need compatible CPU architecture, consistent proxy choices where proxies are used, validation in Coolify and registry access.
- Sessions, uploads, queues, caches and other mutable state must be shared or externalized for reliable horizontal scaling.
- Applications with Coolify persistent storage configured and Docker Compose applications cannot use this attachment workflow as currently documented.
- Deployment, promotion and stop controls live in Coolify, while DNS, TLS, firewalls, health checks, monitoring and capacity planning remain operator responsibilities.
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.
