I’m facing an issue while connecting Discourse to WordPress using the Discourse Plugin. I’m running Discourse on a Digital Ocean droplet. The setup was performed exactly as mentioned here (https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md). The droplet itself sits behind CloudFlare and HTTPS was setup using Let’s Encrypt (using Setting up HTTPS support with Let's Encrypt). The WordPress site is deployed on SiteGround, also behind CloudFlare.
When I add the forum’s root address, API key and administrator username in the plugin settings, in WordPress’ console, it still keeps saying “You’re not connected to Discourse”. Upon further investigating I’ve found that this particular request /site.json%20?api_key=[FILTERED]&api_username=<username> is returning 403 Forbidden even with a fresh, valid API Key and a valid administrator username.
The request to site.json is checking that an API request can be made with the values supplied for the API Key and Publishing Username that are set on WordPress. If you make the request with curl from your local computer, is it working for you? For example, this request with $api_key set to your API key:
curl -X GET 'https://forum.example.com/site.json?api_key=$api_key&api_username=system'
If this is woking for you, you could try installing the WordPress Health Check plugin and looking at the Secure communication row on the Site Status tab to see if it’s finding any issues with communicating with external services using secure connections (SSL.)
Did you ever get this to work? I have the same setup (Discourse on Digital Ocean, WordPress on Siteground, both behind Cloudflare) and the same error. Curl works without issue from my local machine.
How is your SSL configured at cloudflare side? are you using cloudflare performance optimization on discourse?
You should really be running cloudflare SSL in full mode not flexible
If you have cloudflare performance optimization enabled on discourse, disable it by creating a page rule.
When I SSH into the shared server (which is hosted by SiteGround) and manually run a curl command to request my discourse install, I receive the same error message;
I even created a new wordpress site, using a new domain (although on the same Siteground server) without Cloudflare operating DNS and received the same error message.
Solved. This was one of those annoying cases where it just “started working” without a clear solution becoming known. I am going to assume it was a DNS propagation issue and for some reason Siteground’s DNS resolver was slow.
If someone else runs into this problem, my only suggestion is to wait 48 hours and try again. :-/