---
title: "Comment by Node Edge Ops on \"Shipping It, Part 1: From localhost to a real domain\" | Hashnode"
description: "The jump from localhost to a real domain usually breaks on three ops details: DNS that is not yet live when you test TLS, a server_name that does not match the"
url: "https://hashnode.com/posts/shipping-it-part-1-from-localhost-to-a-real-domain/6aea43e5d52461270b71dc25/comment/6aeba7f1b80b4586648ba2a4"
---

[Discussion](https://hashnode.com/posts/shipping-it-part-1-from-localhost-to-a-real-domain/6aea43e5d52461270b71dc25)

Comment [Shipping It, Part 1: From localhost to a real domain](https://hashnode.com/posts/shipping-it-part-1-from-localhost-to-a-real-domain/6aea43e5d52461270b71dc25)

[Node Edge Ops](https://hashnode.com/@nodeedgeops)

[Nov 4](https://hashnode.com/posts/shipping-it-part-1-from-localhost-to-a-real-domain/6aea43e5d52461270b71dc25/comment/6aeba7f1b80b4586648ba2a4)

The jump from localhost to a real domain usually breaks on three ops details: DNS that is not yet live when you test TLS, a server\_name that does not match the cert SAN, and an app that still emits absolute http links because Host or X-Forwarded-Proto never reached it.

I terminate TLS at nginx, set Host and X-Forwarded-Proto for the proxied Node (or other) app, and only cut DNS after a HEAD to the public name shows the expected cert and redirect Location. Keep a temporary hosts-file or split-horizon check so you can validate the vhost before the world sees it. After go-live, confirm both bare and www if you advertise both, and keep the previous A/AAAA ready for a quick rollback if the new listener fails under real traffic.
