listen_https not being honoured?

I am trying to use reverse proxying to access my gitlab-ce instance. The configuration is basically identical to #480 (closed) and #1331 (closed), but it's not working properly. Even though I've set listen_https to false, it looks as though nginx is expecting some keys.

I'm using: gitlab-ce 8.8.0-ce.0

With the following configuration in /etc/gitlab/gitlab.rb:

external_url 'https://[DOMAIN]'

nginx['listen_addresses'] = ['127.0.0.1']
nginx['listen_port'] = 8888
nginx['listen_https'] = false
nginx['proxy_set_headers'] = {
  "X-Forwarded-Proto" => "https",
  "X-Forwarded-Ssl" => "on"
}

Despite having nginx['listen_https'] = false, running gitlab-ctl reconfigure produces a /var/opt/gitlab/nginx/conf/http-registry.confwith a number of SSL settings in it:

  ## Strong SSL Security
  ## https://raymii.org/s/tutorials/Strong_SSL_Security_On_nginx.html & https://cipherli.st/
  ssl on;
  ssl_certificate /etc/gitlab/ssl/[DOMAINNAME].crt;
  ssl_certificate_key /etc/gitlab/ssl/[DOMAINNAME].key;

Resulting in the following in the /var/opt/gitlab/nginx/logs/error.log:

2016/05/22 19:27:34 [emerg] 31368#0: BIO_new_file("/etc/gitlab/ssl/[DOMAINNAME].crt") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/gitlab/ssl/[DOMAINNAME].crt','r') error:2006D080:BIO routines:BIO_new_file:no such file)

This is causing the gitlab nginx server not to start and results in a 502 Bad Gateway error from my reverse proxy. It feels like listen_https somehow isn't be honoured. Any ideas?