Adding a Domain

Follow these steps to assign a custom domain to one of your Odoo services.

Step-by-step guide #

1. Configure DNS #

At your domain registrar or DNS provider, create a DNS record pointing to your server:

• Type: A record
• Name: The subdomain you want (e.g., erp for erp.yourcompany.com)
• Value: The IP address of the server hosting your Odoo service

2. Add the hostname in calmo.cloud #

1. Navigate to your Odoo service
2. Click the Hostnames tab
3. Click Add Hostname
4. Enter the full domain name (e.g., erp.yourcompany.com)

3. Verify and activate #

calmo.cloud will configure the reverse proxy to route traffic from your domain to the service. An SSL certificate is provisioned automatically.

Setting up DNS automatically #

Some DNS providers support Domain Connect, which lets calmo.cloud set up the DNS record for you. When your domain's provider supports it, the hostname shows an Auto-configure DNS button in its DNS Records section, and Auto-configure next to the DNS check on the Hostnames tab. Click it, sign in at your provider and confirm. The provider then creates the record pointing at your server. If the button does not appear, set up the record by hand as described above.

Wildcard domains and DNS certificates #

To serve every first-level subdomain, such as shop.example.com and customer.example.com, add *.example.com as a hostname. Add example.com separately if you also want to serve the root domain. A wildcard does not cover nested names such as shop.customer.example.com.

Wildcard certificates require a DNS certificate resolver:

1. Open the hosting server's configuration and select the Traefik tab.
2. Under DNS certificate resolvers, add a resolver with a name, the IONOS provider and your IONOS API key in prefix.secret format. DNS propagation wait sets how long the proxy waits for the validation record to appear before it asks for the certificate; the default of 60 seconds suits most cases. Save the configuration to update the proxy.
3. Point a wildcard A record (*) at the server's IP address.
4. Add *.example.com under the service's Hostnames tab and select your resolver under Certificate validation.

calmo.cloud verifies wildcard DNS using a fresh subdomain before activating routing. An exact hostname assigned to another service on the same server, such as test.example.com, takes precedence over the wildcard once its DNS is verified. Normal requests, WebSockets and security protections follow the same routing.

You can also select DNS validation for an ordinary hostname. Other domains can keep Automatic (TLS challenge), even when their DNS is hosted by another provider.

One resolver per DNS provider can be configured on each server. Existing API keys are never displayed; leave the key empty when editing to keep it. Changing a key recreates the proxy to reload the credentials. A resolver cannot be removed while any hostname uses it, including a deleted hostname that could be restored.

Removing a hostname #

Click Delete next to the hostname on the Hostnames tab. The service stops answering on it shortly after, without a redeploy on your part.

A deleted hostname keeps its name reserved, so no other service can take it in the meantime. To see it again, set the tab's Deleted records filter to With deleted records or Only deleted records. From there, Restore brings the hostname back with its settings, and Force delete removes it for good and releases the name.

Examples #

Troubleshooting #