On 6/24/20 7:28 AM, kelly.close@lrewater.com wrote:
Hi Mark - could you elaborate on this just a little? One of the things I did try was to include the https:// prefix in my base URL setting and it did not affect the issue. Is there a different way to use an https scheme in the base_url setting than just adding the 's'? I tried every combination I could think of for that setting, restarting both mailman and apache2 between each try I think, but maybe I missed something. ~Kelly
I don't know what the issue was in your case, but if it was fixed by changing the Appache config to not redirect http to https for requests from localhost, it should be fixed by just going to https in the first place unless there is some certificate issue at play. The relevant settings for this list are:
mailman-hyperkitty.cfg: [general] base_url: https://lists.mailman3.org/archives api_key: xxx
settings_local.py: MAILMAN_ARCHIVER_KEY = 'xxx' ALLOWED_HOSTS = ['localhost', '127.0.0.1', 'lists.mailman3.org', 'mail.mailman3.org', 'mailman.iad1.psf.io', 'mail.falconframework.org', '104.239.228.201', ]
(I'm sure the above is overkill, but ...)
MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1', '::ffff:127.0.0.1', '104.239.228.201', )
ACCOUNT_DEFAULT_HTTP_PROTOCOL = 'https'
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan