Error when installing ssl Let's Encrypt

I’m trying to install ssl by following this tutorial

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 #<Process::Status: pid 18775 exit 1>
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?

Let’s Encrypt was down for several hours today, preventing the correct release of new certificates:

https://news.ycombinator.com/item?id=14374933

Things should be back to normal now or soon.

5 Likes

Is it still back today?

Looks like it’s still having some residual issues with their CDNs:

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.

3 Likes

This topic was automatically closed after 25 hours. New replies are no longer allowed.