[MM3-users] Re: Hyperkitty no longer archiving

Mark Sapiro writes:

On 11/21/22 16:33, Hirayama, Pat wrote:

...

mailmansuite.log is full of:

ERROR 2022-11-22 00:25:40,365 7 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP 172.31.0.1, your MAILMAN_ARCHIVER_FROM setting may be misconfigured

Set

MAILMAN_ARCHIVER_FROM = '172.31.0.1'

in your Django settings, or to accept any IP set

MAILMAN_ARCHIVER_FROM = '*'

Hm. Pat wrote:

settings_local.py:

MAILMAN_ARCHIVER_FROM = ('172.18.8.14', '172.31.0.1', '172.31.0.2', '172.31.0.3', '172.31.0.4', '172.31.0.5', '127.0.0.1', '::1')

where '172.31.0.1' is the second element. So we need to figure out where HyperKitty is getting its setting for MAILMAN_ARCHIVER_FROM.

1. Are there multiple copies of settings_local.py lying around?
2. Does settings.py have "from settings_local import *" in it?
3. Are there multiple copies of settings.py lying around?
4. What else may have changed in the migration? Any software upgrades in mailman, hyperkitty, mailman-web (or wherever the settings*.py are coming from)?

Steve