Complete Setup Process
Follow these steps to set up your custom domain for your status page. The entire process typically takes 10-15 minutes.Before you begin: Make sure you meet all requirements and have access to your DNS settings.
Step 1: Add Your Domain
Open Status Page Settings
Navigate to Settings → Status Page → Custom Domain in your Watchman Tower dashboard.
Enter Your Domain
In the custom domain input field, enter your desired subdomain:Important:
- Must be a subdomain (not root domain)
- Use only lowercase letters
- No http:// or https:// prefix
- No trailing slashes
Step 2: Configure DNS
Now you need to create a CNAME record in your DNS settings pointing to Watchman Tower.DNS Record Details
Copy these exact values into your DNS provider:| Field | Value |
|---|---|
| Type | CNAME |
| Name | status (or your chosen subdomain) |
| Target | status.watchmantower.com |
| TTL | 3600 (or Auto/Default) |
| Proxy | Off / DNS only (if using Cloudflare) |
- Cloudflare DNS
- Namecheap
- GoDaddy
- Route 53 (AWS)
Log in to Cloudflare
Go to dash.cloudflare.com and select your domain
Add CNAME Record
Click Add record and fill in:
- Type: CNAME
- Name: status
- Target: status.watchmantower.com
- Proxy status: DNS only (gray cloud) ⚠️
Verify DNS Configuration
After adding the CNAME record, verify it’s correct using your terminal:DNS changes can take 5-60 minutes to propagate depending on your TTL settings. If the command doesn’t show results immediately, wait a few minutes and try again.
Step 3: Wait for SSL Validation
Once your DNS is configured, Cloudflare automatically begins SSL certificate validation.What’s Happening
Monitor Progress
Watch the status badge in your dashboard:- SSL Being Issued ⏳ - In progress (normal for 5-10 minutes)
- Working ✅ - Setup complete, domain is live
- Configuration Error ❌ - DNS issue, see troubleshooting
Typical timing:
- DNS propagation: 5-10 minutes
- SSL validation: 1-5 minutes
- Total: 10-15 minutes on average
Step 4: Test Your Domain
Once the status shows Working ✅, your custom domain is live!Verify HTTPS Access
Open your custom domain in a browser:✅ Page Loads Successfully
✅ Page Loads Successfully
Your status page displays with your monitors and status information
✅ HTTPS Lock Icon
✅ HTTPS Lock Icon
Browser shows a padlock icon indicating secure connection
✅ Valid Certificate
✅ Valid Certificate
Click the lock icon → Certificate details should show:
- Issued to: status.mycompany.com
- Issued by: Cloudflare Inc ECC CA-3
- Valid: Green/secure status
✅ No Warnings
✅ No Warnings
No privacy warnings or SSL errors
Test HTTP Redirect
Try accessing via HTTP (no S):Test from Multiple Locations
Use a tool like UpStatus.io or IsItDownRightNow.com to verify your domain loads correctly from different geographic locations.Step 5: Update Links & Communication
Now that your custom domain is live, update your communication channels:Website Footer
Add a “Status” link pointing to your custom domain
Email Signatures
Include your status page URL for transparency
In-App Links
Update any status page references in your application
Social Media
Share your status page in bio/about sections
Support Documentation
Reference your status page in help articles
Incident Communications
Use your custom domain in incident notifications
Complete Setup Example
Here’s a full walkthrough forstatus.acmecorp.com:
Timeline: Total setup completed in 12 minutes.
Troubleshooting Common Issues
If your domain doesn’t become active within 15-20 minutes, check these common issues:Status Stuck on 'SSL Being Issued'
Status Stuck on 'SSL Being Issued'
Cause: DNS not propagated or incorrect CNAMESolution:
- Verify CNAME record with
digcommand - Check for typos in target domain
- Wait up to 30 minutes for DNS propagation
- Ensure TTL isn’t extremely high (>3600)
Status Shows 'Configuration Error'
Status Shows 'Configuration Error'
Cause: CNAME record missing or incorrectSolution:
- Double-check CNAME target is exactly
status.watchmantower.com - Ensure no extra spaces or characters
- If using Cloudflare, verify proxy is OFF (gray cloud)
- Delete and re-add CNAME if needed
Browser Shows Privacy Error
Browser Shows Privacy Error
Cause: SSL certificate not yet issuedSolution:
- Wait for status to show Working in dashboard
- Don’t visit the domain until status is active
- SSL validation can take up to 10 minutes
Domain Works but Shows Wrong Page
Domain Works but Shows Wrong Page
Cause: DNS cached or propagation incompleteSolution:
- Clear browser cache and try incognito mode
- Try different browser or device
- Flush local DNS:
sudo dscacheutil -flushcache(macOS) - Wait 10-20 more minutes
Deleting a Custom Domain
If you need to remove your custom domain:Next Steps
Understanding Statuses
Learn what each status badge means
Troubleshooting
Resolve common setup issues
FAQ
Answers to frequently asked questions
Security
Security best practices for custom domains
Need Help?
If you’re stuck or need assistance with your custom domain setup:Contact Support
Email us at [email protected] with:
- Your domain name
- Screenshot of DNS settings
- Output of
dig CNAME your-domain.com
