# Enabling Letsencrypt fails

**URL:** https://discourse.roots.io/t/enabling-letsencrypt-fails/6446
**Category:** trellis
**Created:** 2016-04-12T14:26:57Z
**Posts:** 6
**Showing post:** 6 of 6

## Post 6 by @fullyint — 2016-04-16T01:02:39Z

> [@Let's Encrypt: Could not access the challenge file for the hosts/domain](https://discourse.roots.io/t/lets-encrypt-could-not-access-the-challenge-file-for-the-hosts-domain/6457/11):
>
> [roots/trellis#565](https://github.com/roots/trellis/pull/565/) enables Trellis to transition existing `http` sites to `https`. This update may resolve some issues that led to the error message `Could not access the challenge file`
> 
> **Existing servers.** If you try the Trellis update above on a server that has already been provisioned with the prior version of Trellis (i.e., on a server that already has an Nginx conf set up), you should first run:
> 
> ```
> ansible-playbook server.yml -e env=<environment> --tags wordpress
> ```
> 
> That sets up an Nginx conf that will help with the next step of running the `letsencrypt` role:
> 
> ```
> ansible-playbook server.yml -e env=<environment> --tags letsencrypt
> ```
> 
> **New servers.** Just to be clear, for fresh/new servers, you can just run the regular command once:
> 
> ```
> ansible-playbook server.yml -e env=<environment>
> ```

(20 characters for discourse)

---

_[View the full topic](https://discourse.roots.io/t/enabling-letsencrypt-fails/6446)._