@simon we’re publishing the full post. There doesn’t seem to be an error from Discourse. Very odd.
Just wanted to add; we use CoSchedule on this particular instance. We do not on the others. Would this perhaps have something to do with it? I mean, I don’t really see how, but have there been any issues with CoSchedule before? It’s literally the only difference between the 3 instances we have running the Discourse plugin.
Our ops guys have also found “no helpful log information” either.