Taiga it's not work

i download git clone GitHub - kaleidos-ventures/taiga-docker
End start all instruction. ./launch-all.sh


Something happened and the Taiga has captured the error to be able to work on it.

Take me home
use taiga-docker
i dont whera logs :frowning: help plz

Hi @zavgleb, and welcome to the community!

According to the link you provide in your “Take me home”, you’re serving Taiga in the address. What is your exact infrastructure?.

Apart from this, we would need more details to give a proper answer. For example:

  • What are your .env file settings?

  • What’s the status of the containers after running the ./launch-taiga.sh command.
    You can get this info executing docker ps .

  • What are the service logs?.
    You can have this data starting Taiga with docker compose up directly, or with docker compose logs.

  • Do you have a proxy? What’s your configuration?
    If it’s nginx, it should be under /etc/nginx/conf.d/default.conf

  • Any interesting logs or error in the browser’s console or network requests?
    You can open Chrome DevTools by pressing F12 and checking the Console and Network tabs

Thanks in advance

okay i done, thx. But now next problem :frowning: >(
i used lan link taiga.mycompany.com end show me

Oops, something went wrong…

According to the Taiga, your username/email or password are incorrect.

What used login end password?

Hi @zavgleb

If you have follow the guide “Taiga 30 min setup”, one of the steps is the super user creation, with the command

 ./taiga-manage.sh createsuperuser

In that step you define her username/password, and it’s by all means a valid user log in into Taiga.

By default it’s not enabled the public registration, but could also allow users to create their own accounts by following what’s described in the guide

You should introduce the following in the docker-compose.yml:

version: "3.5"


    image: taigaio/taiga-front:latest

Just by restarting Taiga you should be able to create new user clicking on the “create your free account here” link.

Hi @zavgleb,

Don’t worry for your hidden messages, I have a copy.
To avoid this in the future, please try not to share your passwords publicly (although it were fake or testing ones).

And regarding to your problem, with your console logs it seems there’s a communication problem between taiga-front and taiga-back, according to the 404 responses when requesting the api/v1 urls:
GET http://<your domain>/api/v1/stats
GET http://<your domain>/api/v1/discover/...

… and also the login request…
POST http://<your domain>/api/v1/auth

As you mentioned you where running a source-code installation, could you please post here your configuration for taiga-back and taiga-front, specially for these variables?:


TAIGA_SITES_DOMAIN = "taiga.mycompany.com"


    "api": "http://taiga.mycompany.com/api/v1/",
    "eventsUrl": "wss://taiga.mycompany.com/events",
    "baseHref": "/",

The front-end api variable should match the URL where taiga-back is listening.

Other thing to discard a back-end problem and verify its url, it’s to start it with ~/taiga-back [stable] $ DJANGO_SETTINGS_MODULE=settings.config python manage.py runserver and try to access http://taiga.mycompany.com/api/v1/

You should see something like the json shown in the image

As you mentioned you where running a source-code installation, could you please post here your configuration for taiga-back and taiga-front, specially for these variables?:


my code

TAIGA_SITES_DOMAIN = “taiga.link.com


my code
“api”: “http://taiga.link.com/api/v1/”,
“eventsUrl”: “wss://taiga.link.com/events”,
“baseHref”: “/taiga/”,

DJANGO_SETTINGS_MODULE=settings.config python manage.py runserver

Hi @zavglebz,

With the configuration you provided, Taiga is being served following a subpath approach in the following URLs :

It seems that your taiga-front configuration may be wong, as it’s missing the “/taiga” subpath to form the url where taiga-back (the API) is listening. Try to change your ~/taiga-front-dist/dist/conf.json to this:

“api”: “http://taiga.link.com/taiga/api/v1/”,
“eventsUrl”: “wss://taiga.link.com/taiga/events”,
“baseHref”: “/taiga/”,

You can have more details about “subdomain” vs “subpaths” settings in the documentation.