Domains

Dokploy Provide 2 ways to add a domain to your service:

1. Free Domains from Traefik.me
2. Buy a domain from one of the providers above

If you don't have a domain, you can use our integrated free domains from Traefik.me in the Dokploy panel, without doing any configuration however is only for HTTP, if you want to have a HTTPS domain you need to buy a domain from one of the providers above.

Domains are supported for:

• Applications
• Docker Compose

Requirements (Optional)

We recommend this if you want to have a HTTPS domain, you need to buy a domain from one of the providers above.

• Cloudflare
• Porkbun
• Namecheap
• Name.com
• GoDaddy
• Domain.com

Add Domain

Associate custom domains with your application to make it accessible over the internet.

• Host: The domain name that you want to link to your application (e.g., api.dokploy.com).
• Path: The specific path within the domain where the application should be accessible.
• Internal Path: The internal path where your application expects to receive requests.
• Strip Path: Removes the Path from the request before forwarding to the application.
• Container Port: The port on the container that the domain should route to.
• HTTPS: Toggle this on to enable HTTPS for your domain, providing secure, encrypted connections.
• Certificate: Select (letsencrypt) or (None)

For how Internal Path and Strip Path work using Traefik middlewares, see the note below.

Note

Proper domain configuration is crucial for the accessibility and security of your application. Always verify domain settings and ensure that DNS configurations are properly set up to point to the correct IP addresses. Enable HTTPS to enhance security and trust, especially for production environments.

Understanding Internal Path and Strip Path

Dokploy uses Traefik middlewares to modify request paths before they reach your application. These powerful tools allow you to create flexible routing configurations that match your application's expected URL structure.

Internal Path Middleware

The Internal Path middleware adds a prefix to the request path before forwarding it to your container. This is useful when your application expects all requests to start with a specific base path.

Example:

• Domain: api.dokploy.com
• Path: /v1
• Internal Path: /backend/api
• Request: api.dokploy.com/v1/users
• Forwarded to container as: /backend/api/users

In this example, the middleware adds /backend/api to the beginning of the request path, which is helpful when your application is structured to expect requests at a specific internal directory.

Strip Path Middleware

The Strip Path middleware removes a specified path prefix from the request before forwarding it to your container. This is perfect when you want to organize your public URLs with prefixes but your application expects clean, unprefixed paths.

Example:

• Domain: app.dokploy.com
• Path: /dashboard
• Strip Path: Enabled
• Request: app.dokploy.com/dashboard/settings
• Forwarded to container as: /settings

Here, the middleware removes the /dashboard prefix, so your application receives the request as if it was made directly to /settings.

Using Both Internal Path and Strip Path Together

You can combine both middlewares to create sophisticated routing scenarios. When both are enabled, Strip Path is applied first, then Internal Path is added.

Example:

• Domain: service.dokploy.com
• Path: /public
• Strip Path: Enabled
• Internal Path: /app/v2
• Request: service.dokploy.com/public/api/users
• Processing:
  1. Strip Path removes /public: /api/users
  2. Internal Path adds /app/v2: /app/v2/api/users
• Final forwarded path: /app/v2/api/users

This powerful combination allows you to:

• Remove public-facing path prefixes that users see
• Add internal path prefixes that your application requires
• Create clean separation between your public URL structure and internal application structure

When to Use Each Option

• Internal Path only: When your application requires a specific base path that differs from your public URL
• Strip Path only: When you want organized public URLs but your application expects clean paths
• Both together: When you need to transform public URLs to match complex internal application structures

These middlewares ensure your application receives requests in the exact format it expects, regardless of how you structure your public domain paths.

Important Clarification on Container Ports

The "Container Port" specified in the domain settings is exclusively for routing traffic to the correct application container through Traefik, and does not expose the port directly to the internet. This is fundamentally different from the port settings in the "Advanced -> Ports" section, which are used to directly expose application ports. The container port in the domain settings ensures that Traefik can internally direct traffic to the specified port within the container based on the domain configuration.

Static Build Type

When using the Static build type or Nixpacks and Publish Directory build type, you need to use the port 80 when creating a domain.

Adding WWW to your domain

If you want to add WWW to your domain, you can do it by adding a CNAME record to your DNS provider.

For example, if your domain is example.com, you can add a CNAME record to your DNS provider with the following configuration:

• TYPE: CNAME
• NAME: www
• VALUE: example.com

Create the domain in dokploy, using the host www.example.com

Now in dokploy, you can go to application -> advanced -> redirects (Select the preset www to non-www) and click on save.

now everytime you access www.example.com it will redirect to example.com