If you absolutely need a hostname that is not "localhost" you should still configure your own host record and use a utility like mkcert.[1] Most of the time, y

If you absolutely need a hostname that is not "localhost" you should still configure your own host record and use a utility like mkcert.[1] Most of the time, you really shouldn't need this, and your local HTTPS development should just require: mkcert -install mkcert localhost In the directory of your app, etc. If you're deploying private applications, these records should exist in your intranet DNS resolver instead. [1]: https://github.com/FiloSottile/mkcert https://github.com/FiloSottile/mkcert