Skip to content

Connect a Dokploy application to a domain

Route a domain to the correct internal container port and verify HTTPS.

Protect your data firstKeep a current off-server backup before reinstalling, updating, changing firewall rules, or running an application installer.
On this page

Prepare DNS and the application

Point the intended hostname to the VPS and confirm the application is running. Identify the port the process actually listens on inside its container; do not guess from the public URL.

Add the domain

In the application's domain settings, select the host and correct container port. Review path handling before adding prefixes or stripping paths. Enable HTTPS with the supported certificate method once validation can reach the service.

Understand deployment differences

Dokploy application domain changes and Docker Compose domain changes use different routing configuration. Compose changes may need redeployment for updated labels to take effect. Follow the workflow for your resource type.

Keep internal ports private

A proxy route to a container port is not a reason to expose that port directly to the internet. Do not expose database services. If routing fails, inspect application status, DNS, and proxy logs before changing several settings.

Dokploy domain reference.

Was this not enough?Include the service number, exact error, and time of the problem. Never send a password or private key.
Contact support