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.

The short version

Create or open a project, create an Umami service resource, keep the service port in the URL configuration, deploy it, open the public URL, and sign in with the default credentials.

This path is ideal for a first service deployment because Umami is ready-made, uses prebuilt Docker images, and gives you a clear browser check after deployment.


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

First service deployment flow

This first service deployment uses Umami because it is a ready-made one-click service with a clear browser check after deployment.

1

Create or open a project

2

Choose Umami

3

Review service URL

4

Deploy service

5

Open the URL and sign in

  • Create or open the project where the service will live.
  • Choose Umami from the service resources list.
  • Keep the service port in the Coolify URL configuration.
  • Deploy Umami and wait for the containers to start.
  • Open the public URL without the port and sign in.

You should end with running Umami containers, a generated service URL, and a successful login page.

Services run as containers

Coolify deploys one-click services from predefined templates. For this guide, Coolify will create and run the containers Umami needs, then route traffic through the Coolify proxy.

One-click services use prebuilt Docker images, so you do not need to configure a Git repository or build settings for this first test.


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
Tip

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.

Generated URL or your own domain

Fastest first test

http://<uuid>.<server-ip>.sslip.io:3000
  • Keep :3000 in the Coolify URL configuration.
  • Visit the URL without :3000 in your browser.
  • Use this only to confirm the service and proxy work.

Production-style test

https://analytics.example.com:3000
  • Point DNS to your server IP address.
  • Keep :3000 in the Coolify URL configuration.
  • Visit https://analytics.example.com in your browser.
Keep the service port in Coolify

For the first deployment, you can keep the generated sslip.io URL. Do not remove the :3000 port from the URL field in Coolify, because Coolify uses it to route traffic to Umami.

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: umami
Change the default password

After 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 80 and 443
  • 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.

On this page