Interesting — thanks, @david. That certainly makes sense and also seems to line up more or less exactly with the timing on all of this.
I wonder if the WP Discourse plugin is having widespread issues with connections? It doesn’t seem to have any pending updates available as of this morning. And if that is indeed the cause (which seems logical), surely I wouldn’t be the only one experiencing it. I don’t seem to see any other posts about that here, though, curiously enough.
I’ll check in with Zapier on it now, meanwhile. In hindsight, I received the Zapier errors early on — in the morning hours of 9/30 (the same day that certificate change took place) — but then the integration continued to function after. So perhaps they already discovered the issue and addressed it sometime that morning.
The RSS feed is an interesting one. The feed itself still loads fine, with the API key passed along as a variable in the URL. But the plugin I’m using within WordPress to pull and display the most recent item from it keeps generating that “RSS ERROR – No RSS items found” message when accessing it. You’d think the fact that the feed itself is loading would be all that’d matter in that situation, but surely there must be some sort of connection to that and this certificate stuff. I’m just not entirely certain if it’d be on the end of the plugin, which is really just reading the (valid and accessible) RSS file, or if it could somehow be on the Discourse side with the way the API-requiring feed is being generated.