@swalkinshaw, @retlehs: From the back of my head I remembered an issue that occurs exactly when a WordPress site hostname in Trellis resolves to 127.0.0.1: https://discourse.roots.io/t/ssl3-read-bytes-tlsv1-unrecognized-name-downloading-domain-satispress-packages-json/24639/52?u=strarsis and roots/docs#446 - Does this also apply to the localhost records added by this PR?

@strarsis Great memory and thanks for pointing this out

Does this also apply to the localhost records added by this PR?

Looks like it! Maybe we should scope this to development servers only?

Looks like it! Maybe we should scope this to development servers only?

Is HTTPS/TLS used for Trellis development environment?

The underlying issue is that the nginx configuration for localhost is different to the one for its public IP.
When nginx can be configured to also listen on localhost/127.0.0.1 and not just public IP for the wordpres sites (if possible with nginx configuration), then resolving to 127.0.0.1 should not be a problem anymore.