mailman_web complains about hyperkitty (local) webcalls

[gmanic]

Installed working MM core/web. When writing a new list msg, no archive entry is being created, by starting a new thread on hyperkitty list page mailman_web log always complains:

ERROR 2019-05-30 20:29:57,016 22 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman_web:8000'. The domain name provided is not valid according to RFC 1034/1035.
WARNING 2019-05-30 20:29:57,016 22 django.request Bad Request: /api/mailman/archive
WARNING 2019-05-30 20:29:57,016 22 django.request Bad Request: /api/mailman/archive

Tried exact hostname as well as '*' as DJANGO_ALLOWED_HOSTS, but no change. According to Django 2.2 src https://docs.djangoproject.com/en/2.2/_modules/django/http/request/ this should not happen (domain -> present and allowed_host -> '*').

[issue-label-bot]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.69. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[gmanic]

Update. The error msg "domain name not valid according to RFC" goes away, if you define the hostname without _ (underline). Django's function "valid_hostname" checks on this.

Unfortunately, the "bad request" stays. mailman-core (different docker container to mailman-web) cannot fetch templates and no mails reach the archive.

[gmanic]

Solved.

Two comments. As mentioned on another list (actually, lists.mailman3.org, documentation is spread way to far apart), MAILMAN_HOST_IP must not be set to a hostname. This is very unfortunate in an environment with automagic provisioning.

Second, if you want to avoid Django's security problems (DJANGO_ALLOWED_HOSTS), use asterisk (*) instead of hyphenated asterisk ("*")