Yes, Global, single user (myself, admin). WP Discourse does not connect.
- Discourse hosted by DO
- Not sure about custom plugins.
3a. Health Check & Troubleshooting (aka Site Check) has been installed for some time. One questionable “critical issue” reported by Yoast SEO is “Your site cannot be found by search engines.” Further troubleshooting instructions state that “if Google can run the Mobile-Friendly Test, Google can also crawl the domain. In that case, the Ryte warning is wrong.” Both domain and subdomain pass the test.
3b. Tried this previously and once again. All plugins except WP Discourse disabled. WP Discourse does not connect.
UPDATE: I’ve been playing with this for several days and there are several things I don’t understand, probably because almost all of this is totally new to me.
-
The DNS “A” record for discourse subdomain points to the IP assigned by DO (same IP I use for SSH) but
dig discourse.example.compoints to three different IP apparently asssigned by Cloudflare anddig https://discourse.example.compoints to another IPwhois BAREFRUIT-ERRORHANDLINGin GB. Something doesn’t smell right here! -
I assume WP Discourse uses cURL to connect with Discourse so I have been experimenting with cURL and the Discourse API. I have three API keys (including the key confirmed, above). Until yesterday all three indicated Never Used. Yesterday, I noticed the original key created last August now indicates it was used one day ago! The other two still indicate Never Used. I assume this likely means that one or more of my cURL experiments actually did connect; unfortunately, I don’t know which actually worked. I have also noted that cURL commands that produce http 200 do not change the API Last Used info (remains Never Used).
Both #1 and #2, above, seem important to me but I can’t yet determine the issues.
I apologize for the delay; sometimes life interferes. Again, @angus, thanks for your assist.