HTTPS for your pod

.dev names only load over HTTPS, so every pod needs a certificate. Podu doesn’t issue one: your host does, or you do on your own server.

Your host issues it

These hosts issue and renew a certificate for alice.podu.dev on their own, once your pod points at them:

  • Vercel: Issues the certificate automatically once it has verified the domain.
  • Netlify: Issues a Let’s Encrypt certificate automatically and renews it. Check its status under Domain management › HTTPS.
  • GitHub Pages: Requests a Let’s Encrypt certificate once its DNS check passes. Then tick Enforce HTTPS in Settings › Pages; the option can take up to 24 hours to appear.
  • Render: Creates and renews the certificate automatically, and redirects HTTP to HTTPS.
  • Cloudflare Pages: Cloudflare issues the certificate once the domain shows as active in your Pages project.
  • Railway: Generates a Let’s Encrypt certificate once the domain is set up, and renews it before it runs out.
  • Fly.io: Issues a Let’s Encrypt certificate once the record resolves. On a pod with A records, Fly also needs the _fly-ownership TXT record it shows, or follow Fly’s own instructions.

Every host guide has an HTTPS note for its host.

On your own server

When your pod points at your own server with A records, the certificate is yours to get. Let’s Encrypt issues free ones, and certbot is the usual tool. The private key stays on your server.

  1. HTTP-01, the usual way

    Open port 80. Certbot puts a file on your web server, Let’s Encrypt fetches it, and the certificate is issued.

    For nginx: sudo certbot --nginx -d alice.podu.dev. Most certbot installs renew the certificate on their own.

  2. DNS-01, when port 80 is closed

    Run your ACME client with the DNS challenge, for example sudo certbot certonly --manual --preferred-challenges dns -d alice.podu.dev. It shows a value for a TXT record named _acme-challenge.

    Open the pod in My Pods, choose Add TXT record, enter _acme-challenge and paste the value. It is live in about a minute; check with dig +short TXT _acme-challenge.alice.podu.dev, then let the client continue.

    Each renewal asks for a new value, so update the record then too.

    _acme-challenge.alice.podu.dev   TXT   "value-your-acme-client-shows"

Podu and your keys

Podu never issues, stores or sees certificates or private keys.

Podu only publishes the DNS records you set. The certificate and its key stay with your host or on your server.

It doesn't work?

  • A certificate error right after you claim: your host issues the certificate once it sees the record. That usually takes a few minutes.
  • An error about too many certificates: Let’s Encrypt limits how many new certificates can be issued for one registered domain each week, and all pods share the limit for podu.dev. Wait a day or two and try again.
  • DNS-01 fails: check that the TXT name is _acme-challenge and the value is exactly what the client shows, without quotes.
  • .dev only loads over HTTPS. A plain http:// link won’t open, even before the certificate is ready.
  • Still stuck? Open an issue on GitHub.