Thank you @jericson for looking into this.
Looks like there is currently a conflict with an experimental site setting that was just announced: Content-Security-Policy now uses 'strict-dynamic'.
Until a fix for the subscription plugin is in place you will need to make sure content security policy strict dynamic is disabled.