Skip to content

Custom Domains

Connect your own domain name to your Easy Deploy applications for a professional, branded experience.

In your application dashboard:

  1. Go to SettingsDomains
  2. Click “Add Custom Domain”
  3. Enter your domain (e.g., myapp.com or app.mydomain.com)
  4. Click “Add Domain”

Point your domain to Easy Deploy by updating your DNS records:

For root domains (example.com):

Terminal window
Type: A
Name: @
Value: 185.199.108.153

For subdomains (app.example.com):

Terminal window
Type: CNAME
Name: app
Value: your-app.easydeploy.com

SSL certificates are automatically provisioned and renewed:

  • Automatic SSL: Free Let’s Encrypt certificates
  • Custom SSL: Upload your own certificates (Pro plan)
  • Wildcard SSL: Covers all subdomains (Enterprise plan)
  • example.com
  • mysite.org
  • company.net
  • app.example.com
  • api.mysite.org
  • blog.company.net
  • *.example.com (matches any subdomain)
  • Automatically secure new subdomains
  • Perfect for multi-tenant applications
Terminal window
Type: CNAME
Name: your-subdomain
Content: your-app.easydeploy.com
Proxy status: DNS only (gray cloud)
Terminal window
Type: CNAME Record
Host: your-subdomain
Value: your-app.easydeploy.com
TTL: Automatic
Terminal window
Type: CNAME
Name: your-subdomain
Value: your-app.easydeploy.com
TTL: 1 Hour
Terminal window
Type: CNAME
Name: your-subdomain
Value: your-app.easydeploy.com
TTL: 300

After updating DNS records, verification typically takes:

  • CNAME records: 5-10 minutes
  • A records: 15-30 minutes
  • Global propagation: Up to 48 hours

Check DNS propagation: whatsmydns.net

  • Let’s Encrypt certificates automatically provisioned
  • 90-day validity with automatic renewal
  • Domain validation via HTTP-01 challenge
  • Multiple domains supported per certificate

Upload your own SSL certificates:

  1. Navigate to SettingsSSL
  2. Click “Upload Custom Certificate”
  3. Provide:
    • Certificate file (.crt or .pem)
    • Private key file (.key)
    • Certificate chain (if applicable)
  • Covers all subdomains automatically
  • Simplified certificate management
  • Perfect for multi-tenant applications

Some DNS providers offer CNAME flattening for root domains:

  • Cloudflare: Automatic CNAME flattening
  • AWS Route 53: ALIAS records
  • Azure DNS: ALIAS records

Easy Deploy includes global CDN:

  • Edge locations: 200+ worldwide
  • Cache optimization: Automatic asset caching
  • Performance: Faster page loads globally
  • DDoS protection: Built-in security

Set up domain redirects:

Redirect www.example.com to example.com:

.easydeploy.yml
redirects:
- from: "www.example.com"
to: "example.com"
status: 301

Force HTTPS for all traffic:

.easydeploy.yml
redirects:
- from: "http://example.com/*"
to: "https://example.com/:splat"
status: 301

Connect multiple domains to the same application:

  • Primary domain: Main domain for your app
  • Alias domains: Additional domains that redirect
  • Branch domains: Different domains for different environments

Use different domains for different environments:

  • Production: myapp.com
  • Staging: staging.myapp.com
  • Development: dev.myapp.com

Transfer domains between applications:

  1. Remove domain from current application
  2. Add domain to new application
  3. Update DNS records if needed
Terminal window
curl -X POST \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"domain": "myapp.com",
"ssl": true
}' \
https://api.easydeploy.com/v1/applications/APP_ID/domains
Terminal window
curl -H "Authorization: Bearer YOUR_API_KEY" \
https://api.easydeploy.com/v1/applications/APP_ID/domains
Terminal window
curl -X PUT \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"ssl_enabled": true,
"force_https": true
}' \
https://api.easydeploy.com/v1/applications/APP_ID/domains/DOMAIN_ID

Domain not resolving

  • Check DNS record configuration
  • Verify TTL settings and wait for propagation
  • Use DNS lookup tools to verify records

SSL certificate not working

  • Ensure domain is properly verified
  • Check that domain points to Easy Deploy
  • Wait up to 24 hours for certificate provisioning

Mixed content warnings

  • Update hardcoded HTTP links to HTTPS
  • Use relative URLs for assets
  • Check third-party integrations

Need help? Check our troubleshooting guide or contact support.