How to fix: [Django] ERROR (EXTERNAL IP)
This feels like something that I should have working. I know I've not been attending to things all that well, so the thing that has happened, that's got us from, "possibly doing nothing," to throwing this error is that I went to update my mail server, and in the update, Mailman3 stopped working entirely (it was a variety of things), but now it's launching, and will load the main web interface... but
Going to any of the list pages, gives the above Error. Well, not exactly the above error, Django is in square brackets. OK, that will work better for me with the how to fix.
How to fix, probably isn't quite what I'm looking for, it's how to diagnose.
The error tells me that the IP address is 127.0.0.1 and that 127.0.0.1 is in the ALLOWED_HOSTS. I *mostly* see this coming from Google, but when I go and look at the webpage, I get:
normal page at /mailman3/lists/
But my lists, all give me...
Something went wrong HTTP error 500: {"title": "500 Internal Server Error"}
I've tried to figure out where to go from here, and right now I'm not making any progress, so I thought I'd ask here.
On 10/31/24 16:30, Jigme Datse wrote:
Going to any of the list pages, gives the above Error. Well, not exactly the above error, Django is in square brackets. OK, that will work better for me with the how to fix.
What's in Django's logs?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Thu, 31 Oct 2024 20:07:00 -0700 Mark Sapiro <mark@msapiro.net> wrote:
On 10/31/24 16:30, Jigme Datse wrote:
Going to any of the list pages, gives the above Error. Well, not exactly the above error, Django is in square brackets. OK, that will work better for me with the how to fix.
What's in Django's logs?
Attached logs (I hope that works). A couple are currently empty?
On 10/31/24 21:18, Jigme Datse wrote:
On Thu, 31 Oct 2024 20:07:00 -0700 Mark Sapiro <mark@msapiro.net> wrote:
What's in Django's logs?
Attached logs (I hope that works). A couple are currently empty?
I suspect the django_q error is because you need to run django-admin migrate[1], but it isn't responsible for your inability to get list pages.
Again, what's in Django's logs? These are not the uwsgi logs. If you don't know where they are, look in your Django settings in the LOGGING definition for the filename setting for the file handler.
[1] The actual name of the Django admin command may be django-admin,
python manage.py or something else depending on how Mailman web is
installed.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Fri, 1 Nov 2024 12:29:56 -0700 Mark Sapiro <mark@msapiro.net> wrote:
On 10/31/24 21:18, Jigme Datse wrote:
On Thu, 31 Oct 2024 20:07:00 -0700 Mark Sapiro <mark@msapiro.net> wrote:
What's in Django's logs?
Attached logs (I hope that works). A couple are currently empty?
I suspect the django_q error is because you need to run
django-admin migrate[1], but it isn't responsible for your inability to get list pages.Again, what's in Django's logs? These are not the uwsgi logs. If you don't know where they are, look in your Django settings in the LOGGING definition for the filename setting for the file handler.
[1] The actual name of the Django admin command may be
django-admin,python manage.pyor something else depending on how Mailman web is installed.
Thank you,
A couple of things, running django-admin complains about:
Note that only Django core commands are listed as settings are not properly configured (error: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.).
which *that* error gets replaced by:
django.core.exceptions.ImproperlyConfigured: settings.DATABASES is improperly configured. Please supply the ENGINE value. Check settings documentation for more details.
with the command:
python venv/lib/python3.12/site-packages/mailman_web/manage.py migrate
which *might* be the wrong manage.py but other than the change with the migrate command, without it looks to throw the same output.
The Django log was at that time empty it's now attached (larger than I'd like).
It does seem like some configuration isn't quite working. Maybe *badly* not working with some change that happened.
It's not a huge deal, this is more a "fun project" for me. This part of it isn't so much fun.
On 11/1/24 20:14, Jigme Datse wrote:
python venv/lib/python3.12/site-packages/mailman_web/manage.py migrate
which *might* be the wrong manage.py but other than the change with the migrate command, without it looks to throw the same output.
The Django log was at that time empty it's now attached (larger than I'd like).
It is not necessary to post the entire log which repeats the same ERROR and traceback over 300 times. The errors all seem to be disallowed hosts. 321 from IP 45.79.102.219, 5 from mail01.datsemultimedia.com and a few others. The PTR from IP 45.79.102.219 is mail01.datsemultimedia.com and its A is 45.79.102.219. Is this your server, if so add both 45.79.102.219 and mail01.datsemultimedia.com to ALLOWED_HOSTS.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Fri, 1 Nov 2024 20:56:42 -0700 Mark Sapiro <mark@msapiro.net> wrote:
On 11/1/24 20:14, Jigme Datse wrote:
python venv/lib/python3.12/site-packages/mailman_web/manage.py migrate
which *might* be the wrong manage.py but other than the change with the migrate command, without it looks to throw the same output.
The Django log was at that time empty it's now attached (larger than I'd like).
It is not necessary to post the entire log which repeats the same ERROR and traceback over 300 times. The errors all seem to be disallowed hosts. 321 from IP 45.79.102.219, 5 from mail01.datsemultimedia.com and a few others. The PTR from IP 45.79.102.219 is mail01.datsemultimedia.com and its A is 45.79.102.219. Is this your server, if so add both 45.79.102.219 and mail01.datsemultimedia.com to ALLOWED_HOSTS.
Thank you... I while helpful, I think I'll abandon this project... Appreciate the help.
participants (2)
-
Jigme Datse -
Mark Sapiro