# Wp-discourse SSL problem

**URL:** https://meta.discourse.org/t/wp-discourse-ssl-problem/63048
**Category:** WordPress
**Created:** [May 20, 2017, 5:03am UTC](https://meta.discourse.org/t/wp-discourse-ssl-problem/63048 "2017-05-20T05:03:19Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![deviant](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deviant/32/72521_2.png) [@deviant](https://meta.discourse.org/u/deviant)
#### Post date: [May 20, 2017, 5:03am UTC](https://meta.discourse.org/t/wp-discourse-ssl-problem/63048/1 "2017-05-20T05:03:19Z")

</div>

Elo Discoursers..

I have Discourse and Wordpress running on the same host, except that Discourse is inside a Docker container with Nginx setup “external” to docker using a reverse-proxy.

Installed **wp-discourse** on my Wordpress site, but it will not connect to Discourse.  
I do have the API key from my Discourse instance and the correct URL entered into Wordpress, but when I hit Save …

- IceCat browser says: `Secure Connection Failed`

- Chromium says: `No data received`

- Nginx log indicates:

```plaintext
SSL_shutdown() failed (SSL: error:140E0197:SSL routines:SSL_shutdown:shutdown while in init) while SSL handshaking

```

Discourse is installed using the Docker image. In my app.yml I have:

` - "templates/web.socketed.template.yml"`

.. so the Nginx conf has:

```plaintext
    location / {
        proxy_pass http://unix:/var/discourse/shared/standalone/nginx.http.sock:;
        proxy_set_header Host $http_host;
        proxy_http_version 1.1;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto https;
    }

```

I am sure this is an SSL issue. The Letsencrypt certs are installed and configured in the “exernal” host through Nginx:

```plaintext
    ssl_certificate /etc/letsencrypt/live/forum.librenet.co.za/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/forum.librenet.co.za/privkey.pem;

```

I have no idea how to troubleshoot or fix this. Where could the problem be? Is it the Location (“proxy\_pass”) directive?

Any input will be appreciated.

---

<div class="post-metadata">

### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)
#### Post date: [May 20, 2017, 6:28am UTC](https://meta.discourse.org/t/wp-discourse-ssl-problem/63048/2 "2017-05-20T06:28:47Z")

</div>

Could you try installing this WordPress plugin to test your site’s TLS 1.2 compatibility?

> **[TLS 1.2 Compatibility Test](https://wordpress.org/plugins/tls-1-2-compatibility-test/)**
>
> Verify TLS 1.2 support on your webserver for included API endpoints and diagnose a solution to enable compatibility.

Go to Tools/TLS 1.2 Compatibility test to run the test. You can run it with the PayPal API endpoint. I’ve run into problems when the php-curl extension isn’t installed on the server.

---

<div class="post-metadata">

### Author: ![deviant](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deviant/32/72521_2.png) [@deviant](https://meta.discourse.org/u/deviant)
#### Post date: [May 20, 2017, 8:51am UTC](https://meta.discourse.org/t/wp-discourse-ssl-problem/63048/3 "2017-05-20T08:51:38Z")

</div>

Thanks for the input, Simon.

I have not done that test yet, but what I _did_ do was upgrade Nginx to 1.12 (in the process I managed to nuke all my vhosts - so they all had to be recreated … \>.\<)

But after that exercise - wp-discourse shows connected!

So … unless there is an issue later with actual content moving between the apps, I think I’m all good for now 🙂