ERR_TOO_MANY_REDIRECTS after enabling SSL LE

```
System Information
| OS Linux 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC 2018 x86_64
| Shell /bin/bash
| PHP binary /usr/bin/php7.2
| PHP version 7.2.13-1+ubuntu18.04.1+deb.sury.org+1
| php.ini used /etc/php/7.2/cli/php.ini
| EE root dir phar://ee.phar
| EE vendor dir phar://ee.phar/vendor
| EE phar path /opt/easyengine/services/nginx-proxy
| EE packages dir
| EE global config /opt/easyengine/config/config.yml
| EE project config
| EE version 4.0.9
```

```
Client:
Version: 18.09.1
API version: 1.39
Go version: go1.10.6
Git commit: 4c52b90
Built: Wed Jan 9 19:35:31 2019
OS/Arch: linux/amd64
Experimental: false
```

```
Server: Docker Engine - Community
Engine:
Version: 18.09.1
API version: 1.39 (minimum version 1.12)
Go version: go1.10.6
Git commit: 4c52b90
Built: Wed Jan 9 19:02:44 2019
OS/Arch: linux/amd64
Experimental: false
```

```
docker-compose version 1.23.2, build 1110ad01
docker-py version: 3.6.0
CPython version: 3.6.7
OpenSSL version: OpenSSL 1.1.0f 25 May 2017
```

I have just enabled SSL on a site that was initially created without the SSL flag. So the site was up and running on the non-HTTPS version of the URL. Now, I went ahead and enable SSL via the `ee site update example.com --ssl=le` command. Now the site wont load and browsers are complaining about `ERR_TOO_MANY_REDIRECTS`

While trying to troubleshoot this issue I came across the `/opt/easyengine/services/nginx-proxy/conf.d/example.com-redirect.conf` file and noticed that it has an entry for `www.example.com` for the `server_name` values. This doesn't seem correct.

I have done a `ee site reload example.com` after changing those entries to `example.com`, however the issue remains.

Inizia riproducendo l’aggiornamento SSL con `ee site update example.com --ssl=le` e ispeziona `/opt/easyengine/services/nginx-proxy/conf.d/example.com-redirect.conf`, inclusi i valori `server_name` generati. Controlla il percorso di reload dopo aver modificato la configurazione; il lavoro è completato quando il sito viene caricato tramite HTTPS senza `ERR_TOO_MANY_REDIRECTS` e la configurazione di reindirizzamento utilizza il nome host previsto.

Scritto dal modello di indicizzazione a partire dal testo della issue.