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.
There is nothing I didn't post :) I finally found a way to purge the files cached by Cloudflare. It's in their Dashboard. But not before I had migrated everything to apache2! So now I have all my sites configured in both webservers and I can use whichever I like.
Right now I am using apache2, but I am seeing something odd: https://mm3-lists.kictanet.or.ke/archives/ is empty. Is this normal? I am expecting my most active list to appear there or am I overthinking? Like this: https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke...
If there is a proxy_cache_path directive in your config try
find /the/proxy/cache/path -type f -delete
to clear the cache.
There isn't. All the caching mess was coming from Cloudflare proxy servers. If you host your DNS with CF, you will realize they proxy/cache your traffic by default unless you turn that off when creating an A record.
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
linkdirectives referencing those files.
I have seen 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
I did the symlinks and they helped with nginx, but because I have never had to do that before, I did not like it. That's why I switched to apache2 to see what the effects are and apache2 had/has no problem.
Because I have purged the CF cache, I reverted back to nginx and to see from the logs what they are looking for:
root@eu:/opt/mailman/mm/static/CACHE/js# tail -f
/var/log/nginx/mm3-lists_error.log
2024/08/16 17:19:55 [error] 2403078#2403078: *62 open()
"/usr/share/nginx/html/static/CACHE/css/output.44ea6c55e917.css" failed (2:
No such file or directory), client: 172.70.111.111, server:
mm3-lists.kictanet.or.ke, request: "GET
/static/CACHE/css/output.44ea6c55e917.css HTTP/2.0", host: "
mm3-lists.kictanet.or.ke", referrer: "
https://mm3-lists.kictanet.or.ke/archives/"
^C
root@eu:/opt/mailman/mm/static/CACHE/js# cd ../css/
root@eu:/opt/mailman/mm/static/CACHE/css# ls -al
total 196
drwxr-xr-x 2 mailman mailman 4096 Aug 16 16:55 .
drwxr-xr-x 4 mailman mailman 4096 Mar 21 15:55 ..
-rw-r--r-- 1 mailman mailman 1209 Mar 21 15:55 output.d29798365ddb.css
-rw-r--r-- 1 mailman mailman 569 Mar 21 15:55 output.e68c4908b3de.css
-rw-r--r-- 1 mailman mailman 180904 Mar 21 15:55 output.e69dbb26da3b.css
root@eu:/opt/mailman/mm/static/CACHE/css#
So I am left wondering why nginx is prefixing "usr/share/nginx/html" to /static.
I then decided to specify a root directive in the vhost pointing to /opt/mailman/mm/static, and I saw nginx prefixing that path to the /static/ again:
root@eu:/opt/mailman/mm/static/CACHE/css# cp /dev/null
/var/log/nginx/mm3-lists_error.log
root@eu:/opt/mailman/mm/static/CACHE/css# tail -f
/var/log/nginx/mm3-lists_error.log
2024/08/16 17:28:11 [error] 2404382#2404382: *239 open()
"/opt/mailman/mm/static/static/CACHE/css/output.44ea6c55e917.css" failed
(2: No such file or directory), client: 172.70.111.112, server:
mm3-lists.kictanet.or.ke, request: "GET
/static/CACHE/css/output.44ea6c55e917.css HTTP/2.0", host: "
mm3-lists.kictanet.or.ke", referrer: "
https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke/
"
Finally, I changed the root directory to /opt/mailman/mm and this time, I see nginx getting the path correctly, but still looking for the same nonexistent file from above and another file:
root@eu:/opt/mailman/mm/static/CACHE/css# tail -f
/var/log/nginx/mm3-lists_error.log
2024/08/16 17:32:25 [error] 2405076#2405076: *38 open()
"/opt/mailman/mm/static/CACHE/css/output.44ea6c55e917.css" failed (2: No
such file or directory), client: 172.70.111.112, server:
mm3-lists.kictanet.or.ke, request: "GET
/static/CACHE/css/output.44ea6c55e917.css HTTP/2.0", host: "
mm3-lists.kictanet.or.ke", referrer: "
https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke/
"
2024/08/16 17:36:17 [error] 2405080#2405080: *841 open()
"/opt/mailman/mm/static/CACHE/css/output.9efeb5f3d52b.css" failed (2: No
such file or directory), client: 108.162.238.56, server:
mm3-lists.kictanet.or.ke, request: "GET
/static/CACHE/css/output.9efeb5f3d52b.css HTTP/2.0", host: "
mm3-lists.kictanet.or.ke", referrer: "
https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke/message/YVEMMPACZNRMCFVSAMJBACO5RQKYJ6V2/
"
From the above logs, that IP making requests is not my IP! It's the CF proxies.
I then disabled the A record proxying for the site and accessed it from a browser that I havven't used in months, and there was still some errors: The IP showing is my IP.
root@eu:/opt/mailman/mm/static/CACHE/css# systemctl restart nginx
root@eu:/opt/mailman/mm/static/CACHE/css# tail -f
/var/log/nginx/mm3-lists_error.log
2024/08/16 17:41:11 [error] 2406218#2406218: *267 open()
"/opt/mailman/mm/static/CACHE/css/output.44ea6c55e917.css" failed (2: No
such file or directory), client: 185.199.102.24, server:
mm3-lists.kictanet.or.ke, request: "GET
/static/CACHE/css/output.44ea6c55e917.css HTTP/2.0", host: "
mm3-lists.kictanet.or.ke", referrer: "
https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke/
"
2024/08/16 17:41:11 [error] 2406218#2406218: *267 open()
"/opt/mailman/mm/static/CACHE/css/output.9efeb5f3d52b.css" failed (2: No
such file or directory), client: 185.199.102.24, server:
mm3-lists.kictanet.or.ke, request: "GET
/static/CACHE/css/output.9efeb5f3d52b.css HTTP/2.0", host: "
mm3-lists.kictanet.or.ke", referrer: "
https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke/
"
2024/08/16 17:41:12 [error] 2406218#2406218: *267 open()
"/opt/mailman/mm/static/CACHE/js/output.3aaa7705d68a.js" failed (2: No such
file or directory), client: 185.199.102.24, server: mm3-lists.kictanet.or.ke,
request: "GET /static/CACHE/js/output.3aaa7705d68a.js HTTP/2.0", host: "
mm3-lists.kictanet.or.ke", referrer: "
https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke/
"
And the issue is something about accessing the archives. Not sure if there is something to do for nginx to behave.
Apache does not display any single error.
-- 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]