Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unable to login with default account and password #58

Open
changchichung opened this issue May 30, 2022 · 10 comments
Open

unable to login with default account and password #58

changchichung opened this issue May 30, 2022 · 10 comments

Comments

@changchichung
Copy link

changchichung commented May 30, 2022

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
Copy link
Member

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
Copy link

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
Copy link

Any Update?

@w1ck3dg0ph3r
Copy link
Member

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

@Retr02332
Copy link

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
Copy link

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
Copy link

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

This comment was marked as resolved.

@Jhousyfran
Copy link

@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
Copy link

joimaradoni commented May 21, 2024

@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

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants