docker-taiga / taiga

docker-compose.yml for simple taiga setup
215 stars 75 forks source link

Cannot access /admin when running on other port than 80 #43

Closed mrtolkien closed 3 years ago

mrtolkien commented 3 years ago

Hello again,

I have managed to get most of the project working on port 8080, but some features like /admin do not work. As the Taiga documentation is pretty laconic, I’m not sure if it’s supposed to be there but the behaviour is definitely weird.

Additionally, emails sending does not work either.

Steps to reproduce:

Result:

w1ck3dg0ph3r commented 3 years ago

Hi!

/admin and /api return Not Found - The requested resource was not found on this server. and not the standard Taiga 404 error

IIRC, django admin is sensitive to trailing slash, i.e. you should access http://taiga.host/admin/. As for the API - it's http://taiga.host/api/v1/, if you want to get the available endpoints .

/media weirdly redirect me to /media on the 80 port of the host

That's because /media is handled by nginx itself simply for serving files. Maybe we could fix that in nginx config, but I don't see the need for it. The attachments should work properly.

/events returns Upgrade Required

Events is a websocket service, so that is expected.

Sending emails to invite new users does not work (despite the UX saying it did)

As I remember, taiga is sending emails asynchronously with the default setup (with celery enabled), so you wouldn't get UI notifications. The problem should be indicated in taiga-back logs or your SMTP server logs. If the email backend is not configured, taiga would just dump the message body to the log, if I'm not mistaken.