It seems that having
example.com in the blogpost slug on
blog.example.com breaks the way Discourse does the
Referer header matching used for comments.
This is how the bug manifested on our instance earlier today:
We did not dig too deep into this, our quick workaround was to remove
. from the slug and replace it with
- and then regenerate the blog website (code diff). This made the issue go away, comment section loads fine now.
Not a big deal, but this seems like a bug in Discourse, so reporting here.