On Mon, Aug 5, 2024 at 8:19 PM Mark Sapiro <mark@msapiro.net> wrote:
I am having an ugly-looking https://mm3-lists.kictanet.or.ke/archives/
On 8/5/24 07:04, Odhiambo Washington via Mailman-users wrote: page
because of cached content:
2024/08/05 17:00:31 [error] 694#694: *9562 open() "/opt/mailman/mm/static/CACHE/css/output.6dab123e4897.css" failed (2: No such file or directory), client: 172.70.111.39, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.6dab123e4897.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/" 2024/08/05 17:00:31 [error] 694#694: *9564 open() ... That IP address appearing there is not my actual IP, but Cloudflare's, which is acting as proxy for the site.I **think** you may have something like
location /static/ { alias /opt/mailman/web/static/; }in nginx on cloudflare, but since cloudflare is not the Mailman server, /opt/mailman/web/static/ doesn't exist there.
Actually, what I mean is that CF is proxying requests to the host named m3-lists.kictanet.or.ke. I do not have any configuration other than DNS proxying at CF.
I can't be sure on how to configure this without knowing the details of
how requests get from cloudflare to mm3-lists.kictanet.or.ke and from there to the wsgi server.
When you ping m3-lists.kictanet.or.ke, the IP you get is CFs, not the actual IP of the host. So when you talk to m3-lists.kictanet.or.ke via a browser, it's CF IP who you talk to and it in turn talks to the host directly. So the IP address you see in the logs is CF's IP address, not yours, not mine and CF are doing some caching. That's why they are requesting for expired files.
However, if cloudflare just proxies the request for /static/ to the Mailman server and nginx on that server has the above
locationdirective, that may do it.
I suppose it's possible to configure Nginx to NOT ALLOW caching of content from the /static/ location. Being new to Nginx, time to say hi to uncle G again.
-- 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]