devs.li

Deployment Guides & DNS Setup

Step-by-step instructions to connect your .devs.li subdomain to top cloud hosting platforms and avoid common configuration pitfalls.

Vercel & Next.js Render (onrender.com) GitHub Pages Netlify Custom Linux VPS Common Pitfalls & FAQ

1. Connect to Vercel (Next.js / React)

Automatic edge network deployment and auto SSL
  1. Set Primary Routing: In your DEVS.LI Dashboard, claim your subdomain with record type CNAME and target cname.vercel-dns.com (or your project's unique alias like xxxx.vercel-dns-017.com).
  2. Add Domain in Vercel: In your Vercel Project dashboard, go to Settings → Domains, enter yourname.devs.li, and click Add.
  3. Handling TXT Verification (If Requested by Vercel):

    If Vercel asks for domain ownership verification via TXT (Name: _vercel, Value: vc-domain-verify=...):

    • Click the + Add Record button next to your subdomain on DEVS.LI dashboard.
    • Select Type: TXT.
    • Enter Hostname Prefix: _vercel (do not leave blank).
    • Paste the verification value: vc-domain-verify=... into Record Value.
    • Click Add Record (our system automatically routes this to _vercel.devs.li at the apex DNS zone as required by Vercel), then return to Vercel and click "Verify".

    Important: Never change your main subdomain record to TXT in "Edit DNS". Your main record must stay as CNAME so Vercel can route your web traffic.

  4. Resolving "404 DEPLOYMENT_NOT_FOUND": If visiting your domain returns a Vercel 404 page, your DNS is working properly, but Vercel has not mapped an active production deployment to the domain. Go to Vercel → Settings → Domains, verify that your domain is assigned to the Production environment, and ensure your project has completed at least one successful build.

2. Connect to Render (onrender.com)

Free custom domain for Render Web Services & Static Sites
  1. Set Primary Routing: In your DEVS.LI Dashboard, click Claim Subdomain, select record type CNAME, and enter your Render service address (e.g. my-service.onrender.com). You can also click the quick Render preset button.
  2. Add Domain in Render: Open your web service in the Render Dashboard → Settings → Custom Domains. Click Add Custom Domain and enter yourname.devs.li.
  3. Click the "Verify" Button (Crucial Step):

    Render will show an orange badge labeled "DNS update needed". You must click the "Verify" button next to the domain to trigger DNS checking and SSL certificate generation.

    Notice regarding Cloudflare Error 1001: Render routes traffic through Cloudflare for SaaS. If you visit your domain before Render finishes verification, Cloudflare edge servers will temporarily return "Error 1001" or an SSL Handshake error. This does not mean your DNS is broken. Once you click Verify in Render, certificate issuance completes within 1-2 minutes and the error clears automatically.

3. Connect to GitHub Pages

Free static hosting with automated GitHub Actions deployment
  1. On DEVS.LI Dashboard, claim your subdomain with record type CNAME and target username.github.io.
  2. In your GitHub Repository, navigate to Settings → Pages.
  3. Under Custom domain, enter yourname.devs.li and click Save.
  4. Wait for the DNS check to pass (10-30 seconds), then check Enforce HTTPS.

4. Connect to Netlify

Edge server routing with automatic Let's Encrypt TLS
  1. On DEVS.LI Dashboard, set record type to CNAME and enter your Netlify site hostname (e.g. my-app.netlify.app).
  2. In Netlify Dashboard, navigate to Site configuration → Domain management → Custom domains.
  3. Click Add a domain, enter yourname.devs.li, and click Verify.
  4. Netlify detects the CNAME instantly and provisions an SSL certificate.

5. Connect to Custom VPS (Nginx / Apache / Docker)

Direct A-record configuration to your server's public IP
  1. On DEVS.LI Dashboard, select record type A and enter your public IPv4 address (e.g. 139.99.90.146).
  2. In your server's Nginx configuration, add your virtual host:
server {
    listen 80;
    server_name yourname.devs.li;

    location / {
        proxy_pass http://127.0.0.1:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
}

For HTTPS, run certbot --nginx -d yourname.devs.li to obtain a free Let's Encrypt certificate.

Common Configuration Mistakes & Fixes

Review these tips if your domain fails to connect

Do not include "https://" or slashes in DNS Targets

DNS records resolve hostnames, not URLs. Entering https://username.github.io/ or myapp.onrender.com:3000 is invalid. Always enter pure hostnames such as username.github.io or myapp.onrender.com.

Do not change your main CNAME to TXT for verification

When Vercel asks for domain verification, do not edit your primary record to TXT. Your primary record must stay as CNAME to direct traffic to your site. Instead, click "+ Add Record" on your dashboard, select TXT, and enter _vercel as the Hostname Prefix.

Cloudflare Error 1001 on Render

If you see Cloudflare Error 1001 when accessing your Render domain, open your Render dashboard and click the "Verify" button under Custom Domains. The error will disappear once Render completes TLS provisioning (usually 1-2 minutes).

Vercel 404 DEPLOYMENT_NOT_FOUND

This indicates your DNS is working properly and reaching Vercel edge servers, but Vercel has not mapped an active deployment to the domain. Make sure your project has a successful deployment on your production branch (e.g. main).