Guide for Self-Hosting with Coolify
Step-by-Step Instructions for Coolify Setup on Gozunga Cloud
Self-Hosting Coolify on Gozunga Cloud is simple and gives you complete control. Follow these instructions to enable endless application hosting capabilities that can scale with your needs.
- 1. Create Your Gozunga Account - Sign Up to access your dashboard.
- 2. Launch an Instance - You can start with a low end instance and can resize as you grow.
- 3. Secure Your Instance - Connect to perform some basic setup tasks.
- 4. Coolify Setup - Install Coolify and first login
- 5. Final Steps - Last steps before we can host our app
1. Create your gozunga account
If you haven't yet done so, Create an Account. You can sign up for free.
2. Launch an instance
We need to create a server to host our n8n instance. You can start with a low-end instance, and resize later as you grow. If you have another server ready for this task, you may skip this step.
- Login to Gozunga’s Cloud Management Portal, and create a Project to house your virtual machine instance.
- From the Server pane, click Create a Cloud Server
- Select your favorite Linux distribution (ex Ubuntu 24.04) and instance size (st.small1)
- Choose your network settings (ex. Public Network → Internet), and the appropriate SSH key.
- Under Cloud configuration, in order to take care of Coolify installation at install time using Linux’ cloud-init, we will include the following configuration:
#cloud-config
package_update: true
package_upgrade: true
packages:
- curl
runcmd:
- curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash
final_message: "Coolify installation has been completed. The system is now ready to use after $UPTIME seconds."
- Then choose a name for the server (ex. ‘coolify‘) and click Create Server
The server installation, package updates and Coolify installation will take 3-4 minutes to complete
3. Secure your Instance
We'll update our security groups to allow us to securely log in to the server remotely.
- Choose Networking → Security Groups
- Using our knowledge base guide Using Security Groups, create firewall rules to allow secure inbound connectivity to Coolify as follows:
SECURE PORTS FOR COOLIFY MANAGEMENT
SSH - TCP/22
| Field | Value |
|---|---|
| Rule | Custom Protocol |
| Description | Permit inbound SSH |
| Direction | Ingress |
| Open Port | Port |
| Port | 22 |
| Protocol | TCP |
| Remote | CIDR |
| CIDR | [Your IP Address] |
| Ether Type | IPv4 |
COOLIFY WEB Interface - TCP/8000
| Field | Value |
|---|---|
| Rule | Custom Protocol |
| Description | Permit Coolify Management |
| Direction | Ingress |
| Open Port | Port |
| Port | 8000 |
| Protocol | TCP |
| Remote | CIDR |
| CIDR | [Your IP Address] |
| Ether Type | IPv4 |
WEBSOCKET - TCP/6001
| Field | Value |
|---|---|
| Rule | Custom Protocol |
| Description | Permit Coolify Websocket |
| Direction | Ingress |
| Open Port | Port |
| Port | 6001 |
| Protocol | TCP |
| Remote | CIDR |
| CIDR | [Your IP Address] |
| Ether Type | IPv4 |
TERMINAL - TCP/6002
| Field | Value |
|---|---|
| Rule | Custom Protocol |
| Description | Permit Coolify Terminal |
| Direction | Ingress |
| Open Port | Port |
| Port | 6002 |
| Protocol | TCP |
| Remote | CIDR |
| CIDR | [Your IP Address] |
| Ether Type | IPv4 |
(Optional) PING
| Field | Value |
|---|---|
| Rule | Custom Protocol |
| Description | Permit PING |
| Direction | Ingress |
| Open Port | All Ports |
| Port | n/a |
| Protocol | ICMP |
| Remote | CIDR |
| CIDR | [Your IP Address] |
| Ether Type | IPv4 |
PORTS FOR APP TRAFFIC AND MANAGEMENT
HTTP - TCP/80
| Field | Value |
|---|---|
| Rule | Custom Protocol |
| Description | Permit inbound HTTP |
| Direction | Ingress |
| Open Port | Port |
| Port | 80 |
| Protocol | TCP |
| Remote | CIDR |
| CIDR | 0.0.0.0/0 |
| Ether Type | IPv4 |
HTTPS - TCP/443
| Field | Value |
|---|---|
| Rule | Custom Protocol |
| Description | Permit inbound HTTPS |
| Direction | Ingress |
| Open Port | Port |
| Port | 443 |
| Protocol | TCP |
| Remote | CIDR |
| CIDR | 0.0.0.0/0 |
| Ether Type | IPv4 |
Warning
Be sure to follow the instructions, specifically about applying this Security Group to the Virtual Machine instance we created. Creating the security groups does not automatically apply them to the server.
4. (OPTIONAL) VERIFY SSH
The installation process we're using here doesn't require you to even SSH to the server, but if you're like me, you'll want to log in anyway; here is how
- Using the SSH key you selected when creating the virtual machine, SSH to your new server. Take note of the IP address from our Cloud Management Portal.
# If necessary on MacOS or Linux
chmod 600 /path/to/<new-ssh-key>.pem
# SSH to your new server using the key.
# If you are using your own supplied SSH key, specify the proper path
ssh -i /path/to/<new-ssh-key>.pem ubuntu@<ip-address>
# Use sudo to get a root shell on the new server
ubuntu:~$ sudo -s
ubuntu:~#
5. FInal Steps
Last steps before we can host our apps.
- Visit http://<ip-address>:8000 to create your Coolify admin account
- Make sure your account is created and you’re seeing the on-boarding screen
- Skip on-boarding, and choose Settings from the left menu
- Enter your instance’s hostname with https://fqdn format, ex https://coolify.yourdomain.com
- This allows remote TLS access over standard port TCP/443
- Make sure to switch your browser to that new URL to confirm you can log in
- e.g. https://coolify.mydomain.com
- That’s it! Now you’re ready to create a Project within the Coolify admin portal to continue your journey
