Domains and SSL Jun 4, 2026

Connecting a Domain and Enabling SSL

This guide explains how to connect your own domain or subdomain to a service running inside DockerCP. It also explains the basic SSL workflow so your app can be accessed securely through HTTPS.

Step 1: Decide which domain you want to use

You can use a root domain or a subdomain. For apps, a subdomain is usually cleaner.

Examples:

  • example.com
  • www.example.com
  • app.example.com
  • crm.example.com

Step 2: Point DNS to your server IP

Open your domain DNS provider and create an A record.

Type A
Name app
Value Your server IP address
TTL Auto or default

If you are using the root domain, the name may be @. If you are using app.example.com, the name is usually app.

Step 3: Wait for DNS propagation

DNS changes may take a few minutes to several hours. You can check the record using online DNS lookup tools or your terminal.

dig app.example.com

Step 4: Add the domain inside DockerCP

  1. Open DockerCP.
  2. Go to Domains.
  3. Click Add Domain.
  4. Enter the full domain, such as app.example.com.
  5. Select the project and service where traffic should be routed.
  6. Save the domain.

Step 5: Verify DNS

Use the DNS verification option if available. If verification fails, confirm that the A record points to the correct server IP and that there is no typo in the domain.

Step 6: Enable SSL

After DNS points correctly to the server, you can enable SSL. DockerCP is designed to support automatic SSL workflows through reverse proxy routing and certificate records.

Common SSL issues

  • The domain does not point to the correct server IP.
  • Port 80 or 443 is blocked by firewall.
  • DNS propagation is not complete.
  • The service internal port is incorrect.
  • The reverse proxy container is not running.

Commands

The panel handles most actions visually, but these commands help beginners understand what a server operator usually checks while working with Docker-based deployments. 

docker --version
docker compose version
docker ps
docker logs --tail=100 container_name
df -h
free -m

Summary

Area What to check Expected result
Server CPU, RAM, disk, firewall, Docker The server has enough resources and Docker is available.
Application Image, tag, port, variables, storage The service can start and keep data after restart.
Network DNS, proxy route, SSL, browser response The app is reachable from the correct domain.
Security Roles, secrets, audit logs, backups The setup is safe enough for continued operation.

Screenshots

Panel previews matched to this guide: how the related DockerCP screens look while following "Connecting a domain and enabling SSL".

Domain attached to a service, as covered in "Connecting a domain and enabling SSL".
DNS records verified from the DockerCP domain panel.
Certificate state for the routed domain.

Next

  • Apply the guide in a test project first.
  • Check logs after every deployment or configuration change.
  • Document custom values for future handoff.
  • Review related documentation when domains, SSL, databases, or billing are involved.