DevOps

Coolify hosting - multiple servers

How does Coolify handle multiple servers?

Florian Schüssel

• 1 min read
Coolify hosting - multiple servers
Photo by Petr Magera / Unsplash

Coolify has besides being an all in one solution the possibility to manage multiple secondary servers. With secondary I mean that those are "clients" to the main server that acts as control plane.

If you have your server setup to your liking you need to prepare the connection from main to secondary.

As written in their documentation Coolify does everything via SSH also on localhost. This means you need to transfer the public key to the secondary server and set it in the user's .ssh/authorized_keys. You can use a Coolify generated key for this (Keys & Tokens).

💡
Note that you either need to have root login enabled or a non password sudo user installed so Coolify can run all Docker tasks without permission issues.

If you have done all these steps you should be able to create resources and test if everything works.

💡
The secondary server has to have a dedicated (wildcard) domain set. It is not possible to only have one wildcard domain for both.

In my case the deployment worked as should. The only thing is currently (v4.0.0-beta-306) that there seems to be an issue with Let's Encrypt which lead me to temporarily remove the secondary server again as it cannot retrieve a certificate due to rate limiting.