### Author:  [@wiliamjoaquim](https://meta.discourse.org/u/wiliamjoaquim)
#### Post date: [May 19, 2017, 7:35pm UTC](https://meta.discourse.org/t/error-when-installing-ssl-lets-encrypt/63032/1 "2017-05-19T19:35:42Z")
I’m trying to install ssl by following this tutorial
> [@Set up HTTPS support with Let's Encrypt](https://meta.discourse.org/t/setting-up-lets-encrypt/40709):
>
> bookmark This is a guide for enabling HTTPS on an existing Discourse installation using Let’s Encrypt. It assumes prior installation without HTTPS enabled. person_raising_hand Required user level: System Administrator exclamation This guide is only for existing installs where HTTPS is not enabled. Following the [official setup guide](https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md) automatically enables HTTPS by default. So you’d like to add https to your Discourse absolutely free, courtesy of our friends at [Let’s Encrypt?](https://letsencrypt.org/)bell I…
But during rebuild of `./launcher rebuild app` the following error occurs at the end of the rebuild
```
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && bash -c "ln -s /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr}.log /var/www/discourse/log" failed with return #
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"code", "cmd"=>["git reset --hard", "git clean -f", "git remote set-branches --add origin master", "git pull", "git fetch origin $version", "git checkout $version", "mkdir -p tmp/pids", "mkdir -p tmp/sockets", "touch tmp/.gitkeep", "mkdir -p /shared/log/rails", "bash -c \"touch -a /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr}.log\"", "bash -c \"ln -s /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr}.log $home/log\"", "bash -c \"mkdir -p /shared/{uploads,backups}\"", "bash -c \"ln -s /shared/{uploads,backups} $home/public\"", "chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups"]}
79ac568b42218337eeca4810bb478054b34f762f73ee4b20c1d7e5571520387e
**FAILED TO BOOTSTRAP** please scroll up and look for earlier error messages, there may be more than one
```
Is all set up correctly, what can it be?
---
### Author:  [@steko](https://meta.discourse.org/u/steko)
#### Post date: [May 19, 2017, 8:56pm UTC](https://meta.discourse.org/t/error-when-installing-ssl-lets-encrypt/63032/2 "2017-05-19T20:56:43Z")
Let’s Encrypt was down for several hours today, preventing the correct release of new certificates:
[https://news.ycombinator.com/item?id=14374933](https://news.ycombinator.com/item?id=14374933)
Things should be back to normal now or soon.
---
### Author:  [@wiliamjoaquim](https://meta.discourse.org/u/wiliamjoaquim)
#### Post date: [May 19, 2017, 9:40pm UTC](https://meta.discourse.org/t/error-when-installing-ssl-lets-encrypt/63032/3 "2017-05-19T21:40:12Z")
Is it still back today?
---
### Author:  [@featheredtoast](https://meta.discourse.org/u/featheredtoast)
#### Post date: [May 19, 2017, 10:58pm UTC](https://meta.discourse.org/t/error-when-installing-ssl-lets-encrypt/63032/4 "2017-05-19T22:58:26Z")
Looks like it’s still having some residual issues with their CDNs:
> **[Let's Encrypt Status](https://letsencrypt.status.io/)**
>
> Support for Let's Encrypt services is community-based and information on current status and outages can be found at: https://community.letsencrypt.org
> May 19, 2017 12:44PM MDT
> May 19, 2017 6:44PM UTC[Monitoring] We are still engaged in communication with our CDN to try and resolve connectivity issues. Users hitting affecting CDN nodes are still unable to reach our service.
> May 19, 2017 3:44PM MDT
> May 19, 2017 9:44PM UTC[Monitoring] We appreciate your patience while we continue to work with other providers to correct issues impacting our service.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [May 21, 2017, 1:00am UTC](https://meta.discourse.org/t/error-when-installing-ssl-lets-encrypt/63032/5 "2017-05-21T01:00:03Z")
This topic was automatically closed after 25 hours. New replies are no longer allowed.