Hello, I'm hoping someone can help me configure hyperkitty correctly. I've got mailman3 installed and working. I created a test list and can send/receive, moderate message. However, archiving does not seem to be working. Below is a copy of my (sanitized) hyperkitty.cfg file and settings.py file(edited) along with the errors being logged to mailman.log hyperkitty.cfg
# Mailman-Hyperkitty Archiver plugin [general] base_url: http://localhost:8002/ api_key:
settings.py # Mailman API credentials MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = '' MAILMAN_REST_API_PASS = '' MAILMAN_ARCHIVER_KEY = '' MAILMAN_ARCHIVER_FROM = ('my.host.name', 'myIPaddress', '127.0.0.1', '::1')
This is the error being sent to maillog.log
Oct 05 01:54:59 2018 (15127) Exception in "hyperkitty" archiver Traceback (most recent call last): File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connection.py", line 171, in _new_ conn (self._dns_host, self.port), self.timeout, **extra_kw) File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/util/connection.py", line 79, in c reate_connection raise err File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/util/connection.py", line 69, in c reate_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 600, in urlopen chunked=chunked) File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 354, in _make_request conn.request(method, url, **httplib_request_kw) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1239, in request self._send_request(method, url, body, headers, encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1285, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1234, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1026, in _send_output self.send(msg) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 964, in send self.connect() File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connection.py", line 196, in connect conn = self._new_conn() File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connection.py", line 180, in _new_conn self, "Failed to establish a new connection: %s" % e) urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f0ba1c22048>: Failed to establish a new connection: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Thanks in advance, Enrique J. Terrazas
On Fri, Oct 5, 2018, at 12:06 AM, Enrique Terrazas wrote:
Hello, I'm hoping someone can help me configure hyperkitty correctly. I've got mailman3 installed and working. I created a test list and can send/ receive, moderate message. However, archiving does not seem to be working. Below is a copy of my (sanitized) hyperkitty.cfg file and settings.py file(edited) along with the errors being logged to mailman.log hyperkitty.cfg
# Mailman-Hyperkitty Archiver plugin [general] base_url: http://localhost:8002/
Which PORT is your Django listening on? This seems like pointing to 8002 port, are you actually listening on that port?
The error below seems to suggest that either the Django isn't running or you are using wrong address.
api_key:
settings.py # Mailman API credentials MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = '' MAILMAN_REST_API_PASS = '' MAILMAN_ARCHIVER_KEY = '' MAILMAN_ARCHIVER_FROM = ('my.host.name', 'myIPaddress', '127.0.0.1', ':: 1')
This is the error being sent to maillog.log
Oct 05 01:54:59 2018 (15127) Exception in "hyperkitty" archiver Traceback (most recent call last): File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/ connection.py", line 171, in _new_ conn (self._dns_host, self.port), self.timeout, **extra_kw) File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/util/ connection.py", line 79, in c reate_connection raise err File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/util/ connection.py", line 69, in c reate_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/ connectionpool.py", line 600, in urlopen chunked=chunked) File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/ connectionpool.py", line 354, in _make_request conn.request(method, url, **httplib_request_kw) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1239, in request self._send_request(method, url, body, headers, encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1285, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1234, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1026, in _send_output self.send(msg) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 964, in send self.connect() File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/ connection.py", line 196, in connect conn = self._new_conn() File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/ connection.py", line 180, in _new_conn self, "Failed to establish a new connection: %s" % e) urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f0ba1c22048>: Failed to establish a new connection: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Thanks in advance, Enrique J. Terrazas
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)
Thank you Abhilash, The port was in fact the problem. Django is listening on a different port as specified in my uwsgi.ini file
To be sure I understand this correctly: In uwsgi.ini I am specifying: http-socket = my.host.name:8000
And in hyperkitty.cfg: base_url: http://my.host.name:8000/hyperkitty/
Hyperkitty is now archiving messages as expected.
Best regards, Enrique
On Oct 5, 2018, at 9:57 AM, Abhilash Raj <maxking@asynchronous.in<mailto:maxking@asynchronous.in>> wrote:
On Fri, Oct 5, 2018, at 12:06 AM, Enrique Terrazas wrote: Hello, I'm hoping someone can help me configure hyperkitty correctly. I've got mailman3 installed and working. I created a test list and can send/ receive, moderate message. However, archiving does not seem to be working. Below is a copy of my (sanitized) hyperkitty.cfg file and settings.py file(edited) along with the errors being logged to mailman.log hyperkitty.cfg
# Mailman-Hyperkitty Archiver plugin [general] base_url: http://localhost:8002/
Which PORT is your Django listening on? This seems like pointing to 8002 port, are you actually listening on that port?
The error below seems to suggest that either the Django isn't running or you are using wrong address.
api_key:
settings.py # Mailman API credentials MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = '' MAILMAN_REST_API_PASS = '' MAILMAN_ARCHIVER_KEY = '' MAILMAN_ARCHIVER_FROM = ('my.host.name', 'myIPaddress', '127.0.0.1', ':: 1')
This is the error being sent to maillog.log
Oct 05 01:54:59 2018 (15127) Exception in "hyperkitty" archiver Traceback (most recent call last): File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/ connection.py", line 171, in _new_ conn (self._dns_host, self.port), self.timeout, **extra_kw) File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/util/ connection.py", line 79, in c reate_connection raise err File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/util/ connection.py", line 69, in c reate_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/ connectionpool.py", line 600, in urlopen chunked=chunked) File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/ connectionpool.py", line 354, in _make_request conn.request(method, url, **httplib_request_kw) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1239, in request self._send_request(method, url, body, headers, encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1285, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1234, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1026, in _send_output self.send(msg) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 964, in send self.connect() File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/ connection.py", line 196, in connect conn = self._new_conn() File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/ connection.py", line 180, in _new_conn self, "Failed to establish a new connection: %s" % e) urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f0ba1c22048>: Failed to establish a new connection: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Thanks in advance, Enrique J. Terrazas
Mailman-users mailing list -- mailman-users@mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org<mailto:mailman-users-leave@mailman3.org> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mailm...
-- thanks, Abhilash Raj (maxking)
On Fri, Oct 5, 2018, at 8:25 AM, Enrique Terrazas wrote:
Thank you Abhilash, The port was in fact the problem. Django is listening on a different port as specified in my uwsgi.ini file> To be sure I understand this correctly: In uwsgi.ini I am specifying: http-socket = my.host.name:8000
And in hyperkitty.cfg: base_url: http://my.host.name:8000/hyperkitty/
That is the correct thing to do!
thanks, Abhilash
Hyperkitty is now archiving messages as expected.
Best regards, Enrique
On Oct 5, 2018, at 9:57 AM, Abhilash Raj <maxking@asynchronous.in> wrote:>>
On Fri, Oct 5, 2018, at 12:06 AM, Enrique Terrazas wrote:
Hello, I'm hoping someone can help me configure hyperkitty correctly. I've got>>> mailman3 installed and working. I created a test list and can send/>>> receive, moderate message. However, archiving does not seem to be>>> working. Below is a copy of my (sanitized) hyperkitty.cfg file and>>> settings.py file(edited) along with the errors being logged to mailman.log hyperkitty.cfg
# Mailman-Hyperkitty Archiver plugin [general] base_url: http://localhost:8002/
Which PORT is your Django listening on? This seems like pointing to 8002 port, are you actually listening on that port?>> The error below seems to suggest that either the Django isn't running or you are using wrong address.>>
api_key:
settings.py # Mailman API credentials MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = '' MAILMAN_REST_API_PASS = '' MAILMAN_ARCHIVER_KEY = '' MAILMAN_ARCHIVER_FROM = ('my.host.name', 'myIPaddress', '127.0.0.1', '::>>> 1')
This is the error being sent to maillog.log
Oct 05 01:54:59 2018 (15127) Exception in "hyperkitty" archiver Traceback (most recent call last): File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/>>> connection.py", line 171, in _new_ conn (self._dns_host, self.port), self.timeout, **extra_kw) File "/opt/mailman/mailman/lib64/python3.6/site- packages/urllib3/util/>>> connection.py", line 79, in c reate_connection raise err File "/opt/mailman/mailman/lib64/python3.6/site- packages/urllib3/util/>>> connection.py", line 69, in c reate_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:>>> Traceback (most recent call last): File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/>>> connectionpool.py", line 600, in urlopen chunked=chunked) File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/>>> connectionpool.py", line 354, in _make_request conn.request(method, url, **httplib_request_kw) File "/opt/rh/rh- python36/root/usr/lib64/python3.6/http/client.py",>>> line 1239, in request self._send_request(method, url, body, headers, encode_chunked) File "/opt/rh/rh- python36/root/usr/lib64/python3.6/http/client.py",>>> line 1285, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/opt/rh/rh- python36/root/usr/lib64/python3.6/http/client.py",>>> line 1234, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/opt/rh/rh- python36/root/usr/lib64/python3.6/http/client.py",>>> line 1026, in _send_output self.send(msg) File "/opt/rh/rh- python36/root/usr/lib64/python3.6/http/client.py",>>> line 964, in send self.connect() File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/>>> connection.py", line 196, in connect conn = self._new_conn() File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/>>> connection.py", line 180, in _new_conn self, "Failed to establish a new connection: %s" % e) urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f0ba1c22048>: Failed to>>> establish a new connection: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:>>> ------
Thanks in advance, Enrique J. Terrazas
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mailman3.org%2Fmailman3%2Flists%2Fmailman-users.mailman3.org%2F&data=02%7C01%7Cenrique.terrazas%40utsa.edu%7C11f17ae4e6cc4251ccb308d62ad2e2ce%7C3a228dfbc64744cb88357b20617fc906%7C0%7C0%7C636743482595968268&sdata=H0%2Fqe3iPb3hi55DKqZRBgJJ2N4EsMR8qAXild%2FTY%2B4E%3D&reserved=0>>
-- thanks, Abhilash Raj (maxking)
-- thanks, Abhilash Raj (maxking)
Excellent! Thanks again for your guidance.
I have a follow up question, I tried setting the base_url to https but received SSL errors in the mailman.log. The nginx.conf is using a valid certificate from a CA and the sites(Django admin, Postorius, Hyperkitty) all load with https in the browser, they are redirected from http as well. But it seems that internal communication is failing when I try to specify https in the base_url Is this something that I should be concerned about and can be configured? Thank you, Enrique
On Oct 5, 2018, at 11:25 AM, Abhilash Raj <maxking@asynchronous.in<mailto:maxking@asynchronous.in>> wrote:
On Fri, Oct 5, 2018, at 8:25 AM, Enrique Terrazas wrote: Thank you Abhilash, The port was in fact the problem. Django is listening on a different port as specified in my uwsgi.ini file
To be sure I understand this correctly: In uwsgi.ini I am specifying: http-socket = my.host.name:8000
That is the correct thing to do!
thanks, Abhilash
Hyperkitty is now archiving messages as expected.
Best regards, Enrique
On Oct 5, 2018, at 9:57 AM, Abhilash Raj <maxking@asynchronous.in<mailto:maxking@asynchronous.in>> wrote:
On Fri, Oct 5, 2018, at 12:06 AM, Enrique Terrazas wrote:
Hello, I'm hoping someone can help me configure hyperkitty correctly. I've got mailman3 installed and working. I created a test list and can send/ receive, moderate message. However, archiving does not seem to be working. Below is a copy of my (sanitized) hyperkitty.cfg file and settings.py file(edited) along with the errors being logged to mailman.log hyperkitty.cfg
# Mailman-Hyperkitty Archiver plugin [general] base_url: http://localhost:8002/
Which PORT is your Django listening on? This seems like pointing to 8002 port, are you actually listening on that port?
The error below seems to suggest that either the Django isn't running or you are using wrong address.
api_key:
settings.py # Mailman API credentials MAILMAN_REST_API_URL = 'http://localhost:8001<http://localhost:8001/>' MAILMAN_REST_API_USER = '' MAILMAN_REST_API_PASS = '' MAILMAN_ARCHIVER_KEY = '' MAILMAN_ARCHIVER_FROM = ('my.host.name', 'myIPaddress', '127.0.0.1', ':: 1')
This is the error being sent to maillog.log
Oct 05 01:54:59 2018 (15127) Exception in "hyperkitty" archiver Traceback (most recent call last): File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/ connection.py", line 171, in _new_ conn (self._dns_host, self.port), self.timeout, **extra_kw) File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/util/ connection.py", line 79, in c reate_connection raise err File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/util/ connection.py", line 69, in c reate_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/ connectionpool.py", line 600, in urlopen chunked=chunked) File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/ connectionpool.py", line 354, in _make_request conn.request(method, url, **httplib_request_kw) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1239, in request self._send_request(method, url, body, headers, encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1285, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1234, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1026, in _send_output self.send(msg) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 964, in send self.connect() File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/ connection.py", line 196, in connect conn = self._new_conn() File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/ connection.py", line 180, in _new_conn self, "Failed to establish a new connection: %s" % e) urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f0ba1c22048>: Failed to establish a new connection: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Thanks in advance, Enrique J. Terrazas
Mailman-users mailing list -- mailman-users@mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org<mailto:mailman-users-leave@mailman3.org> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mailman3.org%2Fmailman3%2Flists%2Fmailman-users.mailman3.org%2F&data=02%7C01%7Cenrique.terrazas%40utsa.edu%7C11f17ae4e6cc4251ccb308d62ad2e2ce%7C3a228dfbc64744cb88357b20617fc906%7C0%7C0%7C636743482595968268&sdata=H0%2Fqe3iPb3hi55DKqZRBgJJ2N4EsMR8qAXild%2FTY%2B4E%3D&reserved=0<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mailman3.org%2Fmailman3%2Flists%2Fmailman-users.mailman3.org%2F&data=02%7C01%7Cenrique.terrazas%40utsa.edu%7C000997aab2394c7ea77b08d62adf256f%7C3a228dfbc64744cb88357b20617fc906%7C0%7C0%7C636743535264070931&sdata=W9PAu%2FfWmReNNzaLSuqoOIq8RdUEAC1HjA2wy83C878%3D&reserved=0>
-- thanks, Abhilash Raj (maxking)
-- thanks, Abhilash Raj (maxking)
On 10/05/2018 09:39 AM, Enrique Terrazas wrote:
I have a follow up question, I tried setting the base_url to https but received SSL errors in the mailman.log. The nginx.conf is using a valid certificate from a CA and the sites(Django admin, Postorius, Hyperkitty) all load with https in the browser, they are redirected from http as well. But it seems that internal communication is failing when I try to specify https in the base_url Is this something that I should be concerned about and can be configured?
I have
base_url: https://host.name/...
without a port in mailman-hyperkitty.cfg on several servers and that works fine. I think the issue is when you specify https://host.name:8000/... you are going directly to Django and bypassing nginx and it's nginx that has your SSL certificates.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Abhilash Raj
-
Enrique Terrazas
-
Mark Sapiro