Force restarting creates maximum GZIP gibberish (Nginx)

[QuiteAFancyEmerald]

Problem:

Occasionally upon doing npm run kill then npm start the application will error. This happens even with GZIP disabled on Nginx. It is possible to be a cache conflict between pm2 and nginx although we cannot find any documentation for it. Originally thought it was a mismatch between GZIP on NGINX and HU LTS. We use GZIP for our DOM masquerading feature where you can disguise pages as .ico files.

Current Solution:

systemctl restart nginx
npm run kill
npm run fresh-start

Repeat once or twice to retain normal behavior.

[yetval]

hey! not 100% sure but i think i might know whats going on here

two things that could be causing this:

1. race between the server and a background rebuild - when pm2 starts, InvisiProxyLTS-src-refresh immediately kicks off another build. that build deletes and recreates views/dist while the server is already running. if a request hits in the tiny window between "files copied" and "files gzip-compressed", the server serves plain html as gzip and the decompressor loses it

2. pkill node kills the pm2 daemon too - npm run kill uses pkill node which nukes every node process including pm2 itself. nginx is then left holding stale connections to the old backend, which is porbably why restarting nginx fixes it

quick fixes if this is on the right track:

• build into views/dist-new first, then rename to views/dist - eliminates the race
• swap pkill node for npx pm2 kill; pkill -f "node backend.js" || true

happy to PR if useful!

[QuiteAFancyEmerald]

This is incredibly useful! Feel free to PR

[yetval]

Thank You I have just opened up a PR for this, please LMK your feedback!