Deploy your first service
Deploying your first service in Coolify helps you validate one-click resources, proxy routing, generated domains, and browser access in a simple flow.
In this guide, you will deploy Umami, an open source analytics service, from the one-click service resources list.
Before you start
Make sure these things are ready before you deploy the service.
Dashboard access
You can sign in to Coolify and see the main dashboard.
- You can access Coolify in your browser
- Dashboard loads without errors
Server is connected
Coolify has at least one server listed on the Servers page.
- Open Servers from the sidebar
- For self-hosted installs, localhost is fine
Proxy is running
Services need the proxy to route the generated URL to the right container.
- Open the server page
- Start the proxy if it is stopped
If Coolify is not ready yet, first follow Start with Self-hosted or Start with Coolify Cloud.
Deployment overview
Deploy your first Umami service
Choose the deployment method you want to use. Each tab reaches the same first-deployment outcome.
Create your first project
On the Coolify dashboard:
- click New Project
- enter a project name, for example
my-first-project - click Continue
If you already have a project, skip this step and continue to Step 2.
Create a new resource
Open your project and click Create New Resource.
A resource is something Coolify will run for you, such as an app, database, or service. In this guide, the resource will be an Umami service.
Choose Umami from the service list
In the resource list:
- search for Umami
- click Umami
Coolify will create an Umami service resource with generated settings.
Review the service URL
Coolify gives the service a generated URL so you can test it quickly.
If you use your own domain, configure it in Coolify as https://analytics.example.com:3000. Make sure DNS points to your server IP address and ports 80 and 443 are open on your server firewall.
Deploy
Click the Deploy button.
Coolify will pull the required Docker images and start the Umami containers.
After deployment, keep these values ready:
- public service URL without the port
- Umami username,
admin - Umami password,
umami
Open Umami and sign in
Open the public service URL without the port in your browser.
For example, if Coolify is configured with http://<uuid>.<server-ip>.sslip.io:3000, visit http://<uuid>.<server-ip>.sslip.io.
If you use your own domain and Coolify is configured with https://analytics.example.com:3000, visit https://analytics.example.com.
You should see the Umami login page. Sign in with the default credentials:
username: admin
password: umamiAfter the first test works, change the default Umami password before using the service for real traffic.
Common first-deploy issues
Use these checks when Umami deploys but the browser test does not behave as expected.
Link doesn't open
Usually means DNS, firewall, or proxy routing is not ready.
Login fails
Usually means the login details are wrong.
Site not secure
sslip.io can be rate-limited. Use a real domain for TLS.
Usually means the generated URL cannot reach the service through your server and proxy, or the URL is being opened with the wrong port behavior.
Check:
- Umami deployment is in running state
- the URL field in Coolify still includes the service port, for example
:3000 - you open the public URL in your browser without
:3000 - Coolify proxy is running on the server
- your server firewall allows ports
80and443 - if using your own domain, DNS points to your server IP address
What to do next
Your first service confirms that Coolify can create a one-click service, start its containers, route a URL through the proxy, and load the service in a browser.
