With all due respect, there are many thousands of Discourse installs out there in the internet. Just in our hosting we run thousands, and there are many self-hosting too, and your instance is the only one reporting this issue. This means that your issue is most likely self-inflicted.
Since you are running a custom reverse proxy in front of Discourse, I’d start removing this and moving to our blessed standard install setup before reporting the bug upstream here.
