Custom Domain
Custom Domain
Section titled “Custom Domain”Point your own domain at your ɳCloud instance instead of using the default *.nself.cloud address. We’ll verify ownership via DNS, then issue a free TLS certificate from Let’s Encrypt.
1. Add your domain
Section titled “1. Add your domain”Navigate to your instance Custom domain settings and enter your domain name:
example.com# or a subdomainclaw.example.comClick Add domain.
2. Verify via DNS
Section titled “2. Verify via DNS”We’ll display a DNS record you need to add to your domain’s registrar:
Name: _nself-verify.claw.example.comType: TXTValue: nself-verify=xxxxxxxxxxxxxAdd this record to your DNS provider (Cloudflare, Route 53, GoDaddy, etc.). Verification typically completes within a few minutes of the record being live.
3. TLS Certificate (automatic)
Section titled “3. TLS Certificate (automatic)”Once verified, we automatically issue and renew a free TLS certificate via Let’s Encrypt. HTTPS is enabled immediately.
Details
Section titled “Details”- Default address preserved: Your
*.nself.cloudaddress keeps working alongside your custom domain - Single domain per instance: One instance = one custom domain. Create a new instance if you need multiple domains
- DNS-only: No nameserver change required — just add a single TXT record
- Auto-renewal: Certificates renew 30 days before expiry (you don’t need to do anything)
Troubleshooting
Section titled “Troubleshooting””Verification failed”
Section titled “”Verification failed””- Confirm the DNS record is live:
dig _nself-verify.claw.example.com TXT - Wait 2–3 minutes after adding the record
- Check your registrar’s interface for typos in the value
”Domain already in use”
Section titled “”Domain already in use””Each domain can point to only one instance. If you need to move it, remove it from the old instance first.
Certificate errors
Section titled “Certificate errors”HTTPS errors usually mean:
- DNS verification is still pending
- You’re accessing before the certificate issued (wait ~30 sec after “Active” status)
- The domain isn’t in the certificate yet (rare; email support)
API Reference
Section titled “API Reference”Add custom domain:
POST /api/instances/:id/domainContent-Type: application/json
{ "domain": "claw.example.com" }Fetch domain state:
GET /api/instances/:id/domainRemove domain:
DELETE /api/instances/:id/domain