Found it: it was indeed an issue with my nginx configuration that now accidentally emitted a Content-Security-Policy header that is too strict for Discourse.
Removing the Content-Security-Policy fixed my issue.
Found it: it was indeed an issue with my nginx configuration that now accidentally emitted a Content-Security-Policy header that is too strict for Discourse.
Removing the Content-Security-Policy fixed my issue.