Found the Culprit! Like i posted earlier, turns out it was the Content-Security-Policy header doing something weird. I've commented it out for now (because I want to figure out the solution eventually), and everything works!
↧