[MM3-users] Re: Hyperkitty django.request forbidden

[Arpad Horvath via Mailman-users]

Unfortunately I don't remember the articles that I used when I migrated.
But this setting (no MAILMAN_ARCHIVER_FROM setting directly) does not seem to 
work.
Hyperkitty is clearly available from outside, but doesn't seem to be from 
inside (localhost).

I don't know how can I make it available on localhost with nginx.
Current nginx setting is quite long and I am not sure, what is sensitive there.
The structure is this

upstream mailman3 {
    server unix:/run/mailman3-web/uwsgi.sock fail_timeout=0;
}

server {
    listen 80;
    listen [::]:80;
    server_name lists.somewhere.xx;
  ...
}

server {
    listen 443;
    listen [::]:443;
    server_name lists.somewhere.xx;
  ...

    location / {
        uwsgi_pass mailman3;
        include /etc/nginx/uwsgi_params;
    }

    location /mailman3/static {
        alias /var/lib/mailman3/web/static;
    }

    location /mailman3/static/favicon.ico {
        alias /var/lib/mailman3/web/static/postorius/img/favicon.ico;
    }

    access_log /var/log/nginx/mailman3/access.log combined;
    error_log /var/log/nginx/mailman3/error.log;
}


Can I reach hyperkitty through the socket then or what do I need to do?
_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at: 
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/5WL7NOO5CMQFHWFGRRJUWEWO3WZ7VLC3/

This message sent to arch...@mail-archive.com