unable to login with default account and password

[changchichung]

What I do ?

1. clone the repo
2. update TAIGA_HOST to my docker host ip address in variables.env , update expose port in docker-compose.yml (807:80 , 44307:443)
3. docker-compose up

I can see the index page and I try to login with default account and password which is ( admin/123123 ) I believe.

there are no error messages in docker-compose logs

taiga-rabbit | 2022-05-30 01:26:35.040673+00:00 [info] <0.616.0> accepting AMQP connection <0.616.0> (192.168.160.2:44462 -> 192.168.160.4:5672)
taiga-rabbit | 2022-05-30 01:26:35.042539+00:00 [info] <0.616.0> connection <0.616.0> (192.168.160.2:44462 -> 192.168.160.4:5672): user 'taiga' authenticated and granted access to vhost 'taiga'
taiga-proxy | 192.168.11.34 - - [30/May/2022:01:26:54 +0000] "POST /api/v1/auth HTTP/1.1" 401 95 "http://192.168.11.13:807/login?next=%252Fdiscover" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:100.0) Gecko/20100101 Firefox/100.0" "-"
taiga-proxy | 192.168.11.34 - - [30/May/2022:01:27:00 +0000] "POST /api/v1/auth HTTP/1.1" 401 95 "http://192.168.11.13:807/login?next=%252Fdiscover" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:100.0) Gecko/20100101 Firefox/100.0" "-"

the login page shows that account/password incorrent

any suggestions to fix the problem ? or is there any command to create user/update password in cointainer ?

[w1ck3dg0ph3r]

Hadn't look at this for a while, but I believe you should update TAIGA_PORT in variables.env also if you change the exposed port, so that frontend knows where API is at.

[dannythunder]

Also got this problem:

taiga-docker: taiga-docker-taiga-gateway-1 | 172.27.0.1 - - [19/Sep/2022:13:08:53 +0000] "POST /api/v1/auth HTTP/1.1" 401 95 "http://localhost:9000/login" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5112.115 Safari/537.36" "-"

No other docker-log shows 401 or anything in log.

[Retr02332]

Any Update?

[w1ck3dg0ph3r]

This isn't reproducible as is. If you provide your docker-compose file and variables.env I can take a look.

[Retr02332]

Just login to the taiga backend docker and execute the following instruction:

python manage.py createsuperuser

Then log in taking into account the data you entered with the previous command.

[alvinbaena]

I had this issue happen as well.

If you are doing this in Windows with WSL2, the disk io is kind of slow. I had to start the database first without any of the other containers with docker compose --env-file variables.env up db, wait for the database to initialize completely, and then start the whole stack waiting for the taiga-back container to finish initialing (I waited until the celery service started on the taiga-back container). This last step takes a while, so be patient.

After this I could login with the default credentials.

[Jhousyfran]

I had the same problem. I decided to define the variable TAIGA_HOST=localhost. The frontend was calling the api as taiga.lan (default value), this causes login failure. In my case, using ubuntu + docker, running with docker-compose --env-file variables.env up

[joimaradoni]

solved

Hello, i had the same problem,

What I do ?

1. clone the repo
2. update TAIGA_HOST=localhost variables.env

TAIGA_HOST=taiga.lan #change to my sub domain that installed taiga TAIGA_SCHEME=http TAIGA_PORT=8081 TAIGA_BACK_HOST=back TAIGA_FRONT_HOST=front EVENTS_HOST=events TAIGA_SECRET=secret

3. i change docker-compose.yml in this part below

proxy: image: dockertaiga/proxy container_name: taiga-proxy restart: unless-stopped depends_on: - back - front - events networks: - default ports: - 8081:80 - 8043:443 volumes: #- ./cert:/taiga-cert - ./conf/proxy:/taiga-conf env_file: - variables.env

i change the ports

4. docker-compose up

please help how to solve it?

[Jhousyfran]

@joimaradoni See again, according to your information, you changed the values of TAIGA_HOST with TAIGA_PORT. It is the variable TAIGA_HOST that must be equal to localhost, not TAIGA_PORT

[joimaradoni]

@joimaradoni See again, according to your information, you changed the values of TAIGA_HOST with TAIGA_PORT. It is the variable TAIGA_HOST that must be equal to localhost, not TAIGA_PORT

Yes now resolved my issue, i changed the variable.env become

TAIGA_HOST=taiga**.p******.com #my sub domain that installed taiga TAIGA_SCHEME=http TAIGA_PORT=8081 TAIGA_BACK_HOST=back TAIGA_FRONT_HOST=front EVENTS_HOST=events TAIGA_SECRET=secret