I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe the installation went fine and running "curl http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will be using exim and nginx with this installation.
It seems I am stuck with the nginx setup. I created a sitename.com.conf file in the /etc/nginx/conf.d folder. I have the following inputted there:
server {
listen 80;
server_name sitename.com;
location /static/ { alias /opt/mailman/web/static/; }
location / { include uwsgi_params; uwsgi_pass 172.19.199.3:8000; uwsgi_read_timeout 300; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } }
However when I go to http://sitename.com (obviously using an alias here for privacy reasons) I get the default nginx index page. Do I need to add anything to the main nginx.conf file to be able to see my mailman3 installation?
Thank you for any assistance, Brian Carpenter
is this the complete sitename.conf? I had a situation where I had a location / definition for caching before the mailman one.
On 19.12.18 16:03, brian@emwd.com wrote:
I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe the installation went fine and running "curl http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will be using exim and nginx with this installation.
It seems I am stuck with the nginx setup. I created a sitename.com.conf file in the /etc/nginx/conf.d folder. I have the following inputted there:
server { listen 80; server_name
sitename.com;location /static/ { alias /opt/mailman/web/static/; }
location / { include uwsgi_params; uwsgi_pass 172.19.199.3:8000; uwsgi_read_timeout 300; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } }
However when I go to http://sitename.com (obviously using an alias here for privacy reasons) I get the default nginx index page. Do I need to add anything to the main nginx.conf file to be able to see my mailman3 installation?
Thank you for any assistance, Brian Carpenter
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On 12/19/18 7:03 AM, brian@emwd.com wrote:
I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe the installation went fine and running "curl http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will be using exim and nginx with this installation. ... location / { include uwsgi_params; uwsgi_pass 172.19.199.3:8000; uwsgi_read_timeout 300; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } }
Since you can curl http://172.19.199.3:8000/postorius/lists/ and get the correct output, uwsgi or whatever your wsgi process is is working at that level, and I don't think you should be invoking uwsgi in nginx. I think you should be using proxy_pass.
See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=AttachFile&do=view&target=lm3o_nginx.txt> for the nginx config used on lists.mailman3.org.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks Mark. Are those settings used for the conf.d/sitename.conf file or for the main nginx.conf file? I am very new to nginx though it looks easier to use than Apache.
Brian
On December 19, 2018 11:31:37 AM EST, brian@emwd.com wrote:
Thanks Mark. Are those settings used for the conf.d/sitename.conf file or for the main nginx.conf file? I am very new to nginx though it looks easier to use than Apache.
They could be in a conf.d file, but in this case they are in sites-available/020-mailman.conf and symlinked from sites-enabled/020-mailman.conf.
-- Mark Sapiro <mark@msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.
Mark Sapiro wrote:
They could be in a conf.d file, but in this case they are in sites-available/020-mailman.conf and symlinked from sites-enabled/020-mailman.conf.
I am not sure what you mean. What documentation recommends using sites-enabled/020-mailman.conf or is this your own custom setup you have for lists.mailman3.org? I am using Docker which has nothing that references the use of such file paths/directories.
On 12/19/18 11:44 AM, brian@emwd.com wrote:
Mark Sapiro wrote:
They could be in a conf.d file, but in this case they are in sites-available/020-mailman.conf and symlinked from sites-enabled/020-mailman.conf.
I am not sure what you mean. What documentation recommends using sites-enabled/020-mailman.conf or is this your own custom setup you have for lists.mailman3.org? I am using Docker which has nothing that references the use of such file paths/directories.
My nginx.conf contains
include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;at the end of the 'http' section to include files from both conf.d/ and sites-enabled/. The name 020-mailman.conf is my own name.
In any case, Abhilash's answer at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...> is probably better than mine.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, Dec 19, 2018, at 8:18 AM, Mark Sapiro wrote:
On 12/19/18 7:03 AM, brian@emwd.com wrote:
I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe the installation went fine and running "curl http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will be using exim and nginx with this installation. ... location / { include uwsgi_params; uwsgi_pass 172.19.199.3:8000;
Change this to use port 8080 instead of 8000. 8000 is for HTTP protocol and 8080 is for uwsgi protocol.
See the docs1.
uwsgi_read_timeout 300; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr;} }
Since you can curl http://172.19.199.3:8000/postorius/lists/ and get the correct output, uwsgi or whatever your wsgi process is is working at that level, and I don't think you should be invoking uwsgi in nginx. I think you should be using proxy_pass.
See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=AttachFile&do=view&target=lm3o_nginx.txt> for the nginx config used on lists.mailman3.org.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
Abhilash Raj wrote:
On Wed, Dec 19, 2018, at 8:18 AM, Mark Sapiro wrote:
I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe
On 12/19/18 7:03 AM, brian(a)emwd.com wrote: the installation went fine and running "curl http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will be using exim and nginx with this installation. ...
location / { include uwsgi_params; uwsgi_pass 172.19.199.3:8000; Change this to use port 8080 instead of 8000. 8000 is for HTTP protocol and 8080 is for uwsgi protocol.
See the docs1.
Thanks Abhilash. It is working now. FYI, I made the change directly in the nginx.conf file. I got rid of trying to use the conf.d/sitename.conf file.
I now move on to getting exim to work. If I need help, I will start a separate thread.
Brian
participants (4)
-
Abhilash Raj -
brian＠emwd.com -
Hagen Bauer -
Mark Sapiro