Trax/django produces HTTP 500 internal server errors about trax

[christianlupus]

OK, now I see. I was mislead. I thought I needed to log into the main django application. Instead is was sufficient to log into the admin interface. I managed to configure trax with my mattermost installation now, I think successfully. Thank you very much.

[christianlupus]

Oh, by the way. My modifications:

# diff env.example .env
7c7
< DJANGO_ADMIN_URL=
---
> DJANGO_ADMIN_URL=^admin/
14c14,15
< DJANGO_ALLOWED_HOSTS=.trax.io
---
> #DJANGO_ALLOWED_HOSTS=.trax.io
> DJANGO_ALLOWED_HOSTS=trax.example.com
35c36
< TIME_ZONE=UTC
---
> TIME_ZONE=Europe/Berlin

# diff docker-compose.*
36c36
<       - "0.0.0.0:8079:80"
---
>       - "127.0.0.1:8001:80"

[agateblue]

Hi @christianlupus! Inside the DJANGO_ALLOWED_HOSTS= variable, you should put the domain name used to access your trax instance (trax.example.com seems invalid in this case).

Can you try that, reload the process and let me know if it works?

[christianlupus]

I replaced my real domain name with example.com throughout all my comments. I wanted to avoid putting a semi-installed installation of trax publicly on the web while sharing the url to it. Is it save to do so and there are no preconfigured user accounts?

By reloading you mean docker-compose restart or down and up -d or even build?

[agateblue]

docker-compose up -d should do the trick, otherwise stop then start

It should be safe to share the URL, since you are creating the superuser by hand.

[christianlupus]

OK, I am ok with both. The url is https://trax.christian-wolf.click. I will add the .env file here as an attachment .env.

[agateblue]

Alright, I see nothing wrong with your env file. Without any log, it's hard to debug. You don't have anything at all in docker-compose logs django ?

[christianlupus]

Yes, there is quite something. I will attach the output of your command: django.log or without the color scripts django_clean.log.

[agateblue]

And no new logs when you are logging in?

EDIT: are you logging on /admin/?

[christianlupus]

Nope, nothing. This is the strange thing. I would have assumed some message to appear at least.

[christianlupus]

The only thing I could try additionally is set ALLOWED_HOSTS=* and opening a connection directly to the nginx or django directly using SSH port forwarding.

[agateblue]

Just to be sure, is the error happening on /admin/ or /accounts/login ?

[christianlupus]

I did not try to connect to /admin. Just putting in the credentials and submitting opens /accounts/login with the error.

Update: When trying the admin console, I can log in.

[agateblue]

Ok, if you can login to the admin, I think we can close the ticket, unless you have other configuration issues ?

I agree this is not ideal (and the other login page is confusing) but I really have no time to maintain Trax anymore these days :/

[agateblue]

Thank you!