Only users in the root team could configure system-wide settings.
optional
You can specify a Fully Qualified Domain Name (FQDN, eg: https://example.com) for your Coolify instance.
Without this configuration you need to use <ip address>:3000 to reach your Coolify instance and all webhooks will be going to the ip address.
If you change the domain name and you already have an existing integration with any Git provider, the webhooks (for autobuild and PR deployments, etc…) will fail. You need to reconfigure the URL manually in the GitHub/GitLab App.
optional
Redirect not configured services to this page. Like if you set a DNS entry for example.com, but you do not have anything running on this domain, Coolify Proxy will redirect any requests to this Default Redirect URL.
You can rollback Coolify to any previous version if something is broken on the latest one.
Example: 3.11.13
default: 3
You can specify how many Docker images are kept locally for your applications. It helps you to revert to a previous state blazingly fast.
default: .
The separator used in the PR/MR previews.
With the default you get: PRMRNumber.yourdomain.com
If you set it to: - the preview domain will be: PRMRNumber-yourdomain.com
default: off
You can specify if you would like to reach your Coolify instance on www & non-www as well, or just the defined FQDN (https://example.com -> non-www).
default: 9000-9100
Port rage for on-demand TCP proxies (public databases), services (if need additional proxies).
Allow these ports in your firewall settings.
default: on
By default, all DNS settings would be resolvable by Let’s Encrypt servers and Coolify. If you are using behind a reverse proxy or tunnel, you can disable this check to prevent unnecessary errors.
optional
default: the OS configured DNS servers will be used
If you have an internal DNS server, you can specify them here with comma separated a list, for example: 1.1.1.1,8.8.8.8.
default: on, but after the first registration, off.
After the first registration, this option is enabled to prevent unwanted registrations.
default: off
If enabled, Coolify checks for update every ~10 minutes and apply them automatically if there is a new version available.
All resources (applications, databases, services) are keep running and available. Coolify does not required to run them. Only Git webhooks will fail during the update.
Set Do Not Track after installation.
You can add SSH Keys (private keys) to your Coolify instance, which can be used to connect to a Remote Docker Engine.
You can add custom SSL certificates to Coolify Proxy, even self-signed.
You can add custom Docker registries and set authentication for it to be able to: