How to change the domain of a Docker project

When you deploy an application like n8n or OpenClaw from the Hostinger Docker Catalog, it is assigned a default temporary hostname (e.g., n8n-xxxx.srv123.hstgr.cloud). To use your own custom domain (e.g., n8n.example.com) with full HTTPS (SSL) support, you must update the project’s configuration and configure your DNS settings.

Step 1: Prepare your DNS (Cloudflare or other providers)

Before changing the configuration in hPanel, your domain must point to your server:

1. Create an A record for your desired subdomain (e.g., n8n).
2. Set the Content/Target to your VPS IP address.
3. Important: If using Cloudflare, set the Proxy status to DNS-only (gray cloud) during the initial setup. You can reactivate the proxy (orange cloud) once the SSL certificate is successfully issued.

Step 2: Update the Docker Compose configuration

You must tell the Docker container to listen for requests coming from your custom domain instead of the temporary one.

1. Go to your hPanel → VPS → Manage.
2. Navigate to the Docker Manager section.
3. Locate your active project (e.g., n8n) and click the Manage
   
   
4. Then access the .yaml editor.

   

5. Locate the labels section in the YAML file. Look for lines mentioning Host rules.
6. Change the default hostname to your custom domain in the following places:
   • traefik.http.routers.[project-name].rule=Host(‘yourdomain.com’)
   • traefik.http.routers.[project-name]-secure.rule=Host(‘yourdomain.com’)
     
7. Deploy the container to apply the changes.
   

Step 3: Verify SSL and Connectivity

Once redeployed, Traefik will automatically attempt to issue a Let’s Encrypt SSL certificate for your new domain.

1. Wait 1–3 minutes for the SSL handshake to complete.
2. Open your site in an Incognito/Private window to avoid cached errors.
3. If you encounter an ERR_TOO_MANY_REDIRECTS error, ensure your Cloudflare SSL/TLS encryption mode is set to Full (strict) or that the Cloudflare proxy is temporarily disabled.

By updating the Traefik Host labels in your Docker configuration, you can easily transition from a temporary development URL to a professional custom domain. This setup ensures that your Docker applications remain secure with automated HTTPS certificates.