Domain name Change?

Community Support
4

Since in some cases WordPress can have issues with different/changing domain names, we do it another way, provided that the client already owns/knows the domain name that will be used:

  1. Setup the correct (future) domain name in Hestia
  2. On the developer side we either add lines to the OS’s hosts file that point to the Hestia server IP address or use Fiddler for that.
  3. On the client side, we setup and configure Fiddler and a browser that supports proxy server. In this browser we configure Fiddler as the proxy and in Fiddler we use the hosts remapping feature. The client is using this browser to watch the site as it being built.

This way WordPress “knows” only one domain name, so there is no name to be changed when the site will go LIVE, apart from DNS server records. The downside is that we can’t have any Let’s Encrypt certificate this way.

We also use this method when the client wants us to renew the web site, but the old site needs to be up and running while we work on the renewed version.