On Wed, Aug 7, 2024 at 2:08 AM Mark Sapiro <mark@msapiro.net> wrote:
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.
Could you allow me to revisit this issue since I haven't solved it? First, I bypassed CloudFlare DNS proxying just to ensure I have nothing is coming in between my browser and the web server. That did not help with the issue of the "missing" CSS files.
Ideally, I should not be creating these symlinks, right? On my old server the symlinks weren't necessary.
I have created some symlinks and that appears to help with Apache. I will test with Nginx and see how it goes.
root@eu:/opt/mailman/mm/static/CACHE/css# ls -al
total 196
drwxr-xr-x 2 mailman mailman 4096 Sep 29 10:40 .
drwxr-xr-x 4 mailman mailman 4096 Mar 21 2024 ..
lrwxrwxrwx 1 mailman mailman 23 Sep 29 10:40 output.ac23d5f5127c.css ->
output.d29798365ddb.css
lrwxrwxrwx 1 mailman mailman 23 Sep 29 10:31 output.bacec526ec98.css ->
output.e69dbb26da3b.css
-rw-r--r-- 1 mailman mailman 1209 Mar 21 2024 output.d29798365ddb.css
-rw-r--r-- 1 mailman mailman 569 Mar 21 2024 output.e68c4908b3de.css
-rw-r--r-- 1 mailman mailman 180904 Mar 21 2024 output.e69dbb26da3b.css
root@eu:/opt/mailman/mm/static/CACHE/css#
My question though: What is the source of truth for the files that should be in /opt/mailman/mm/static/CACHE/css/ ?? Maybe that is what I need to focus on. If need be, then I should *fix* the contents of that file so that it doesn't contain the nonexistent files, no?
Lastly, why is it that my https://mm3-lists.kictanet.or.ke/archives/ does not display content similar to what https://lists.mailman3.org/archives/ does? What change should I make in which settings.py?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]