New site fails with 403 to javascript files

Hi all, I’m trying to set up a new site and everything looks fine in the journal, but the site itself is failing with 403 on the application javascript and other files. I checked the file permissions against a working site that I have and the permissions look fine. The only difference that I can see in the network calls, is that the site that is failing is getting a 304 temporary redirect from the company that I regsitered the domain with.

I see these errors in the peertube.error.log:

« GET /client/en-US/runtime.637c05f29d591f9a.js HTTP/2.0 » 403 564 « https://flashist.studio/ » « Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 »

« GET /client/en-US/polyfills.49fdee6c496b7b63.js HTTP/2.0 » 403 564 « https://flashist.studio/ » « Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 »

An update – I checked the nginx.conf files in both systems and while they are different, I didn’t see anything that looked suspicious in the site that doesn’t work. However, I checked with nginx -T and noticed that there were several packages missing from the list

STANDARD HTTP MODULES: Core, Proxy, Rewrite, Access, Gzip, Headers, HTTP/2, Log, Real IP, SSL, Thread Pool, Upstream, AIO Multithreading.

Does anyone know if I can add these packages to the current nginx or do I have to rebuild from scratch to include those?