Domains and SSL

Your temporary hostname

After the first successful deploy, Nautvia creates a hostname for you — your-site-production.apps.nautvia.com — with DNS and a certificate already in place. Use it to test before your real domain points anywhere.

It follows your store automatically. If the server is rebuilt and the IP changes, this record is updated for you.

Adding your own domain

Overview → Domains → Add domain. Nautvia then shows the exact record to create:

Type	Name	Value	TTL
A	@ or the subdomain	your application server's IP	300

Create it at your DNS provider. Nautvia re-checks every minute for up to twelve hours, and the panel shows what your domain currently answers, so you can see propagation happening rather than guess.

Once the record resolves, a Let's Encrypt certificate is issued and an nginx server block is installed. The domain moves to connected.

Only A records

Nautvia publishes an IP address, not a hostname. There is no CNAME target to point at, and no ALIAS or ANAME support.

This is why apex domains work — example.com cannot be a CNAME under DNS rules, but it can be an A record. It is also the source of the one real operational catch, below.

Three things that block verification

• Remove any AAAA record. The store is served over IPv4 only. Browsers prefer IPv6, so a leftover AAAA sends visitors to an address that does not answer, and the store looks down while DNS looks correct.
• Cloudflare must be "DNS only" (grey cloud). With the orange cloud on, Let's Encrypt's validation request never reaches your server and the certificate cannot be issued. Turn the proxy back on afterwards if you want it, but only after the certificate exists.
• Extra A records split your traffic. Verification still passes if your server's IP is among the answers, and you will be warned — but visitors are being sent to more than one place.

Making it primary

A connected domain can be made primary. Nautvia then updates Magento's base_url and base_url_secure and flushes the cache, so generated links and redirects use it.

Until you set a primary domain the store's base URL is http://your-server-ip/, which is what the first install configures. Setting a primary domain is what moves your store onto HTTPS properly.

Certificates

Issued by Let's Encrypt over HTTP validation, renewed automatically by a timer on your server, with nginx reloaded on renewal. Nothing to configure and nothing to remember.

The team owner's email address is given to Let's Encrypt for expiry notices — see the Privacy Policy.

After a teardown: read this

Tearing down an environment gives you a new IP address on the next deploy. Your custom domain's A record still points at the old one, and Nautvia cannot change it for you.

The temporary apps.nautvia.com hostname moves automatically. Your own domain does not — it lives at your DNS provider, under your account.

After a rebuild: open the domain, read the new IP, update the A record, and press Retry. Verification and certificate issuance run again. Lowering the TTL to 300 before a planned teardown makes the gap minutes instead of hours.

Removing a domain

Removing it from Nautvia deletes the server block and stops serving that hostname. Your DNS record is yours and stays until you delete it — which means the name will keep resolving to an address that no longer answers, so remove it at your provider too. If the removed domain was primary, the oldest remaining connected domain takes over.