# An invalid response was returned from Discourse","http\_code":"","http\_body":""}
**URL:** https://meta.discourse.org/t/an-invalid-response-was-returned-from-discourse-http-code-http-body/385021
**Category:** WordPress
**Created:** [October 8, 2025, 1:30pm UTC](https://meta.discourse.org/t/an-invalid-response-was-returned-from-discourse-http-code-http-body/385021 "2025-10-08T13:30:36Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@haydenjames](https://meta.discourse.org/u/haydenjames)
#### Post date: [October 8, 2025, 1:30pm UTC](https://meta.discourse.org/t/an-invalid-response-was-returned-from-discourse-http-code-http-body/385021/1 "2025-10-08T13:30:36Z")
Updated the wp-discourse plugin, and it breaks things again. Error:
You are not connected to Discourse. Check that your connection settings are correct. If the issue persists, enable connection logs and check Logs.
Connection log:
[2025-10-08 13:29:13] connection.INFO: check\_connection\_status.failed\_to\_connect {“error”:“wpdc\_response\_error”,“message”:“An invalid response was returned from Discourse”,“http\_code”:“”,“http\_body”:“”}
I’m at a lost I have not changed anything other than updating the WP-Discourse plugin, I just published a post as usual and noticed that it’s no longer connected.
---
### Author:  [@Lilly](https://meta.discourse.org/u/Lilly)
#### Post date: [October 8, 2025, 1:33pm UTC](https://meta.discourse.org/t/an-invalid-response-was-returned-from-discourse-http-code-http-body/385021/2 "2025-10-08T13:33:17Z")
looks similar to this:
> [@Cannot connect Discourse to WordPress](https://meta.discourse.org/t/cannot-connect-discourse-to-wordpress/229073/2):
>
> Hey @CMASFO, welcome to meta slight_smile For this kind of issue please see my response here In particular: I’d recommend you press your hosting provider a bit more, asking them why there’d be an inability to make a cURL request to a domain. If they have some more specific reason to think it’s an issue with the WP Discourse plugin, and not say, an incorrect cURL version on the server (which on the face of it is more likely), they’re welcome to post here, or even pm me, and I’d be happy t…
---
### Author:  [@haydenjames](https://meta.discourse.org/u/haydenjames)
#### Post date: [October 8, 2025, 2:33pm UTC](https://meta.discourse.org/t/an-invalid-response-was-returned-from-discourse-http-code-http-body/385021/3 "2025-10-08T14:33:49Z")
Thanks for hinting me in the right direction. The issue was expired TLS cert. It had expired ~ 4 days ago.
I use Cloudflare, so I didn’t catch that was the issue. I should have had a 💡 but didn’t at the time, as I was traveling. So I just lowered CF’s SSL/TLS encryption mode from Strict to Full via mobile when the forums had ssl\_browser error.
Anyway today I used the opportunity to switch to the stable branch. Edited `/var/discourse/containers/app.yml` to uncomment “version” and set it to **stable** :
Then did:
```plaintext
sudo ./launcher rebuild app
```
Retested forum cert from the blog server:
Works:
So, in summary, this is completely my goof. Sorry and thanks!
**Edit:** checked the cron `crontab -l` (its there) and did a `--force` renewal, which was successful, so the autorenew _should_ work the next time. 🤞
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [November 7, 2025, 2:34pm UTC](https://meta.discourse.org/t/an-invalid-response-was-returned-from-discourse-http-code-http-body/385021/4 "2025-11-07T14:34:25Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.