On Mon, Aug 5, 2024 at 11:55 PM Mark Sapiro <mark@msapiro.net> wrote:
On 8/5/24 12:45, Odhiambo Washington via Mailman-users wrote:
Yes, those are Cloudflare IPs and I don't know why 2! All I know is that in DNS, I created an A record for the hostname and
chose
the "proxy" option in the cloudflare DNS management interface.
OK, I know nothing about how cloudflare proxying works, so ignoring that and assuming it's OK, ... ...
I don't know. However, those IPs you see in the Nginx logs, none belong to me! I have two possible IPs - one domiciled in KE and another domiciled in the US (when I use VPN).
I think I've misunderstood. Is it the case that the messages you report like /opt/mailman/mm/static/CACHE/css/output.6dab123e4897.css" failed (2: No such file or directory) ... are in the nginx log on the mailman server.
That's correct.
If so, see https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configurat....
Is that what you have?
Yes.
If not, post your nginx configuration.
In any case, here is my virtualhost config:
server {
if ($host = mm3-lists.kictanet.or.ke) {
return 301 https://$host$request_uri;
listen 80;
server_name mm3-lists.kictanet.or.ke;
return 301 https://mm3-lists.kictanet.or.ke$request_uri;
include snippets/letsencrypt.conf;
}
server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name mm3-lists.kictanet.or.ke;
ssl_certificate /etc/letsencrypt/live/
mm3-lists.kictanet.or.ke/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/
mm3-lists.kictanet.or.ke/privkey.pem;
ssl_trusted_certificate /etc/letsencrypt/live/
mm3-lists.kictanet.or.ke/chain.pem;
include snippets/ssl.conf;
include snippets/letsencrypt.conf;
access_log /var/log/nginx/mm3-lists_access.log;
error_log /var/log/nginx/mm3-lists_error.log;
location = /favicon.ico {
log_not_found off;
access_log off;
}
location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}
location /static/ {
alias /opt/mailman/mm/static/;
}
location / {
proxy_pass http://127.0.0.1:8010;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
}
}
-- 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]