Last Update:
Issue solved, found the root cause, not discourse-related (sorry guys!). The issue was that the Certificate was updated and served through a HAP, we were not using a HAP before and Discourse was serving it itself, we forgot about this detail, which implied that we got that CORS error.
Lessons learned:
- Rolling back Discourse is not a thing, better have a backup of the entire machine (that was the case, thankfully).
- I’m yet to find out why it was so difficult to rebuild with a specific SHA following the instructions I read here, I was unable to do so.
- Better to always serve the certs from the HAP but don’t forget about it. (As a note for anyone else, it’s necessary to add the flag
'set-header X-Forwarded-Proto https'because Discourse has its own NGINX, and this is where it was failing). - The fact that no one was reporting the same issue (even considering that this is a corner-case since the plugin is not official) pointed to that direction (Community as intended
) - The issue only manifested late (to the point that we didn’t remember the Cert change) because of the rebuild triggered by the update, which is where it failed.
Once again, thanks and sorry for the noise!