# Https://www Unsecure and Not Redirecting

**URL:** https://discourse.roots.io/t/https-www-unsecure-and-not-redirecting/7071
**Category:** trellis
**Created:** 2016-06-27T00:19:48Z
**Posts:** 35
**Showing post:** 31 of 35

## Post 31 by @fullyint — 2016-08-01T07:14:39Z

@Simeon you mentioned updating your `wordpress_sites` files but could you confirm that you updated [all files as in roots/trellis#622](https://github.com/roots/trellis/pull/622/files)? I suspect your files are missing the [`site_hosts` definition](https://github.com/roots/trellis/blob/aa7c0645f4e88cf0bb2717aa2d1251e463c89c3e/group_vars/all/helpers.yml#L13) in `group_vars/all/helpers.yml`, potentially among other things.

Once you have the full set of updates, I suggest you run the entire `server.yml` playbook (without specifying any `--tags`). If that runs into trouble, you could then run just  
`ansible-playbook server.yml -e env=production --tags wordpress`  
to work out the Nginx confs, and then run  
`ansible-playbook server.yml -e env=production --tags letsencrypt`

* * *

> [@Let's Encrypt issue when adding new domain to multisite](https://discourse.roots.io/t/lets-encrypt-issue-when-adding-new-domain-to-multisite/7021/10):
>
> I wonder if a future version of Trellis might be smart enough to detect if there’s new `site_hosts` and remove all existing `letsencrypt` data

I’m currently testing an update to implement this. In the meantime, if you’re working on a site/project with some existing letsencrypt CSRs/certs, you may need to do one of these:

> [@fullyint](#):
>
> 1. a fresh droplet (so there’s no LE stuff on it)  
> OR
> 2. SSH in to the remote and  
> delete the CSRs in `/var/lib/letsencrypt/csrs` and  
> delete the certs in `/etc/nginx/ssl/letsencrypt`

---

_[View the full topic](https://discourse.roots.io/t/https-www-unsecure-and-not-redirecting/7071)._