Hi all.
Now I'm struggeling with configuring hyperkitty. It's not clear to me which base_url to set. Currently it's base_url: http://localhost:8001/hyperkitty/ but that leads to
Jan 04 21:01:39 2019 (8322) HyperKitty failure on http://localhost:8000/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> (401)
The api_key is set in /usr/share/mailman3-web/settings.py.
I suppose I'm doing it wrong. Any hints appreciated.
thanks and cheers t.
On 1/4/19 12:07 PM, Thomas Stein wrote:
Hi all.
Now I'm struggeling with configuring hyperkitty. It's not clear to me which base_url to set. Currently it's base_url: http://localhost:8001/hyperkitty/ but that leads to
That's wrong. base_url is set to the URL used to access Hyperkitty externally. It is used for things like the Archived-At: and List-Archive: headers in distributed posts. For example, for this installation it is
base_url: https://lists.mailman3.org/archives
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Friday, 4 January 2019 21:27:41 CET Mark Sapiro wrote:
On 1/4/19 12:07 PM, Thomas Stein wrote:
Hi all.
Now I'm struggeling with configuring hyperkitty. It's not clear to me which base_url to set. Currently it's base_url: http://localhost:8001/hyperkitty/ but that leads to
That's wrong. base_url is set to the URL used to access Hyperkitty externally. It is used for things like the Archived-At: and List-Archive: headers in distributed posts. For example, for this installation it is
It's working with base_url: http://localhost:8000/hyperkitty/.
Is that ok?
thanks and cheers t.
base_url: https://lists.mailman3.org/archives
On 1/4/19 12:30 PM, Thomas Stein wrote:
It's working with base_url: http://localhost:8000/hyperkitty/.
Is that ok?
I've just tested that locally and it seems to be OK. The Archived-At: and List-Archive: headers still show the correct external URLs.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
After changing the api_key to something else than the default one and adjusting settings.py accordingly, everything works. Sorry for the noise.
cheers t.
On Friday, 4 January 2019 21:07:18 CET Thomas Stein wrote:
Hi all.
Now I'm struggeling with configuring hyperkitty. It's not clear to me which base_url to set. Currently it's base_url: http://localhost:8001/hyperkitty/ but that leads to
Jan 04 21:01:39 2019 (8322) HyperKitty failure on http://localhost:8000/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> (401)
The api_key is set in /usr/share/mailman3-web/settings.py.
I suppose I'm doing it wrong. Any hints appreciated.
thanks and cheers t.
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/
Thomas, I just want to thank you for posting this note about your resolution. You never know when a seemingly minor thing makes a major difference to someone else! I have been struggling with the same "Hyperkitty failure on..." error message for days, and while I made sure, with copy/paste, again and again, that the api_key string matched the SECRET_ARCHIVER_KEY string, I was still using the string that came with the Django local settings file on install (32 character string of random characters).
I just changed the key (in both places) to something new and simple for testing and magically my archives are working! In fact every test message I've sent since initial setup is there (where were all those durn things hiding anyway???). I don't know if one of the characters in the original string is a no-no in Ubuntu, or if a non-printing character was hiding in there, or WHAT, but...
It works! It works!!
Thanks Mark S. as well for your help finding the logs and getting me pointed in the right direction.
Now that I've done it, turns out installing MM3 on Ubuntu 8.04 using the mailman3-full distro (w/ apache2, postgresql, postfix) is a VERY simple and straightforward process with relatively few steps (just a couple really critical, non-obvious ones!). I'll post a walkthru once I've tidied it up a bit.
~Kelly
kelly.close＠lrewater.com wrote:
Now that I've done it, turns out installing MM3 on Ubuntu 8.04 using the mailman3-full distro (w/ apache2, postgresql, postfix) is a VERY simple and straightforward process with relatively few steps (just a couple really critical, non-obvious ones!). I'll post a walkthru once I've tidied it up a bit.
Hi Kelly,
I for one will be looking forward to your walkthrough. I have a working MM3 installation using Docker on CentOS 7 platform but am wanting to do some testing using different methods of installing on other distros.
Thanks! Brian
On 1/8/19 11:13 AM, kelly.close@lrewater.com wrote:
I just changed the key (in both places) to something new and simple for testing and magically my archives are working! In fact every test message I've sent since initial setup is there (where were all those durn things hiding anyway???).
They were queued in Mailman's var/archives/hyperkitty/spool/ directory and retried on every post until they succeeded.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (4)
-
brian＠emwd.com -
kelly.close＠lrewater.com -
Mark Sapiro -
Thomas Stein