### Author:  [@bobghosh](https://meta.discourse.org/u/bobghosh)
#### Post date: [March 11, 2019, 10:02pm UTC](https://meta.discourse.org/t/go-daddy-ssl-certificate-installation-error-in-d-o-server/111317/1 "2019-03-11T22:02:09Z")
I purchased a wildcard SSL certificate from Go Daddy and have followed the blog for SSL installation:
> [@Allow SSL / HTTPS for your Discourse Docker setup](https://meta.discourse.org/t/advanced-setup-only-allowing-ssl-https-for-your-discourse-docker-setup/13847):
>
> This guide is likely out of date as there are now very few reasons not to use the built-in Let’s Encrypt certificate that Just Works. See also: 2023-04-10 @pfaffman says: This is left here mostly for historical purposes. So you’d like to enable SSL for your Docker-based Discourse setup? Let’s do it! This guide assumes you used all the [standard install](https://meta.discourse.org/t/142537?silent=true) defaults – a container configuration file at/var/discourse/containers/app.yml and Discourse docker is installed at: /var/discourse Buy a SS…
I have a one-click Discourse from Docker image in Digital Ocean. Any help will be appreciated.
Did everything as per the instruction. When I run the command “./launcher rebuild app” I am getting the error below.
What does this mean?
FAILED
* * *
Pups::ExecError: cd /var/www/discourse && bash -c "ln -s /shared/log/rails/{production,production\_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log /var/www/discourse/log" failed with return #\
Location of failure: /pups/lib/pups/exec\_command.rb:112: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,sidekiq}.log"", "bash -c "ln -s /shared/log/rails/{production,production\_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log $home/log"", "bash -c "mkdir -p /shared/{uploads,backups}"", "bash -c "ln -s /shared/{uploads,backups} $home/public"", "bash -c "mkdir -p /shared/tmp/{backups,restores}"", "bash -c "ln -s /shared/tmp/{backups,restores} $home/tmp"", "chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp"]}
eac99c52aa1c499e6f4e56bd9b439d59615a58c14fb8b8eb97f6245958a8862d
\*\* FAILED TO BOOTSTRAP \*\* please scroll up and look for earlier error messages, there may be more than one
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 11, 2019, 10:31pm UTC](https://meta.discourse.org/t/go-daddy-ssl-certificate-installation-error-in-d-o-server/111317/2 "2019-03-11T22:31:32Z")
Unless you have some reason that you want it to be much harder to configure and that you’ll need to do it again every year then the cert expires, you can instead just run `./discourse-setup` and get a free certificate from Let’s Encrypt. The only reason not to that I’m aware of is if you are a bank or something and have a cert that shows that it’s really your company.
---
### Author:  [@bobghosh](https://meta.discourse.org/u/bobghosh)
#### Post date: [March 14, 2019, 8:13pm UTC](https://meta.discourse.org/t/go-daddy-ssl-certificate-installation-error-in-d-o-server/111317/3 "2019-03-14T20:13:48Z")
I did the free let’s encrypt option and got mixed SSL browser error. After inspecting, it says this:
Mixed Content: The page at ‘[https://portal.slccpoa.org/](https://portal.slccpoa.org/)’ was loaded over HTTPS, but requested an insecure image ‘[http://portal.slccpoa.org/uploads/default/original/1X/be8d1b2f999b51c2c7895046e80485ac288492fb.jpeg](http://portal.slccpoa.org/uploads/default/original/1X/be8d1b2f999b51c2c7895046e80485ac288492fb.jpeg)’. This content should also be served over HTTPS.
Can you guide me in how to fix this?
Thanks
---
### Author:  [@Remah](https://meta.discourse.org/u/Remah)
#### Post date: [March 14, 2019, 8:25pm UTC](https://meta.discourse.org/t/go-daddy-ssl-certificate-installation-error-in-d-o-server/111317/4 "2019-03-14T20:25:23Z")
> [@bobghosh](#):
>
> I have a one-click Discourse from Docker image in Digital Ocean.
Hi @bobghosh, welcome to [meta.discourse.org](http://meta.discourse.org). 😀
The following may be unrelated to your problem but you should know the following as this could save you time in future:
- The Digital Ocean one-click install is not officially supported here as it does not use the [official install](https://meta.discourse.org/t/142537?silent=true) instructions:
> [@Discourse One-Click Application doesn't work](https://meta.discourse.org/t/discourse-one-click-application-doesnt-work/97779/2):
>
> Unfortunately we can only provide support for our official installation instructions. The digital ocean one-click installer creates a slightly different environment. You can find our official instructions here: [discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md)
- The one-click install may still have these issues:
> [@Digital Ocean Now allow to install discourse with one click](https://meta.discourse.org/t/digital-ocean-now-allow-to-install-discourse-with-one-click/73005/2):
>
> Their one-click app is just fine, so long as you upgrade it immediately afterwards to ensure it is on latest. Also, please note, that everytime you SSH into the machine, it might re-start the installation process and you have to use CTRL + C to exit out (since Discourse is already installed).
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [March 14, 2019, 10:57pm UTC](https://meta.discourse.org/t/go-daddy-ssl-certificate-installation-error-in-d-o-server/111317/5 "2019-03-14T22:57:41Z")
Mixed content errors are caused by not having “force\_https” enabled in the site settings.
---
### Author:  [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [March 14, 2019, 10:59pm UTC](https://meta.discourse.org/t/go-daddy-ssl-certificate-installation-error-in-d-o-server/111317/6 "2019-03-14T22:59:44Z")
Mixed content errors can also be caused by explicitly using an `http://` URL that is loaded, for example in a theme, rather than an `https://` or a relative URL.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [March 14, 2019, 11:00pm UTC](https://meta.discourse.org/t/go-daddy-ssl-certificate-installation-error-in-d-o-server/111317/7 "2019-03-14T23:00:31Z")
Really? I was sure I had seen URLs rewritten with that setting enabled.
---
### Author:  [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [March 14, 2019, 11:04pm UTC](https://meta.discourse.org/t/go-daddy-ssl-certificate-installation-error-in-d-o-server/111317/8 "2019-03-14T23:04:54Z")
> [@Stephen](#):
>
> Really?
Yep. Take a look at [try.discourse.org](http://try.discourse.org) right now (or before 2019-03-15T10:00:00Z when it resets).
I added an `http://` URL in a theme to overwrite the logo.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [May 3, 2022, 1:07am UTC](https://meta.discourse.org/t/go-daddy-ssl-certificate-installation-error-in-d-o-server/111317/9 "2022-05-03T01:07:37Z")
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [May 3, 2022, 2:24am UTC](https://meta.discourse.org/t/go-daddy-ssl-certificate-installation-error-in-d-o-server/111317/10 "2022-05-03T02:24:25Z")