Go Daddy SSL certificate installation error in D.O. server

unsupported-install

(Bob Ghosh) #1

I purchased a wildcard SSL certificate from Go Daddy and have followed the blog for SSL installation:

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

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 &quot;touch -a /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log&quot;", "bash -c &quot;ln -s /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log $home/log&quot;", "bash -c &quot;mkdir -p /shared/{uploads,backups}&quot;", "bash -c &quot;ln -s /shared/{uploads,backups} $home/public&quot;", "bash -c &quot;mkdir -p /shared/tmp/{backups,restores}&quot;", "bash -c &quot;ln -s /shared/tmp/{backups,restores} $home/tmp&quot;", "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


(Jay Pfaffman) #2

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.


(Bob Ghosh) #3

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/’ was loaded over HTTPS, but requested an insecure image ‘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


(Just another happy Discourse user) #4

Hi @bobghosh, welcome to meta.discourse.org. :grinning:

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 instructions:
  • The one-click install may still have these issues:

(Stephen) #5

Mixed content errors are caused by not having “force_https” enabled in the site settings.


(Joshua Rosenfeld) #6

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.


(Stephen) #7

Really? I was sure I had seen URLs rewritten with that setting enabled.


(Joshua Rosenfeld) #8

Yep. Take a look at 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.