On 8/6/24 14:27, Mark Sapiro wrote:
Is this with only one browser? It's a long shot, but clearing browser cache might work.
Actually, I see the same issues from my browsers, so it's not a browser caching issue. The only thing left is nginx caching, but, while I know very little about nginx, I think it doesn't cache by default and I don't see where in your posted config it's enabled. Perhaps there's more in your config that you didn't post.
If there is a proxy_cache_path directive in your config try
find /the/proxy/cache/path -type f -delete
to clear the cache.
As a last resort, your /opt/mailman/mm/static/CACHE/ directory should
contain a css/ directory with 3 files and a js directory containing one
file and a manifest.json file with a template for the link directives
referencing those files.
The js/ directory is easy as its only one file, so your server is looking for /static/CACHE/js/output.3aaa7705d68a.js and you could create a symlink in the js/ directory from output.3aaa7705d68a.js to the actual file. For the css directory, your server is looking for output.158acc288604.css and output.6dab123e4897.css, and I don't see the third file in the logs you posted, but if I go to pages in your archive that I see as unstyled and look at the stylesheet references, they are to output.44ea6c55e917.css, output.e68c4908b3de.css and output.9efeb5f3d52b.css so you could just symlink those to the actual files, it doesn't matter which as all three are loaded on each page.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan