taigaio
[BUG] According to the Taiga, your username/email or password are incorrect.
Hi
I just did a Docker pull and I am getting this error in the browser According to the Taiga, your username/email or password are incorrect. Bear in mind that my Taiga was working perfectly just before that.
I have already defined a reabbit version based on the previopus botched pull.
taiga-events-rabbitmq:
image: rabbitmq:3.8-management-alpine
The inspector shows these errrors
So I am not sure what I can do, I am locked out now. This is perplexing, everytime I do a docker pull this is broken, which you can see from my previous bug posts :(
I am in the middle of a project and all my bugs and tasks are in Taiga, and I cant acces them and my delivery is in couple weeks :(
taiga-gateway_1 | 192.168.2.4 - - [26/Aug/2021:01:14:07 +0000] "GET /events HTTP/1.1" 502 560 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-"
taiga-gateway_1 | 192.168.2.4 - - [26/Aug/2021:01:14:09 +0000] "GET /events HTTP/1.1" 502 560 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-"
taiga-gateway_1 | 2021/08/26 01:14:09 [error] 31#31: *2319 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.2.4, server: , request: "GET /events HTTP/1.1", upstream: "http://172.26.0.7:88
88/events", host: "taiga.lan:25080"
taiga-gateway_1 | 192.168.2.4 - - [26/Aug/2021:01:14:10 +0000] "POST /api/v1/auth HTTP/1.1" 502 560 "http://taiga.lan:25080/login?force_login" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-"
taiga-gateway_1 | 2021/08/26 01:14:10 [error] 31#31: *2321 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.2.4, server: , request: "POST /api/v1/auth HTTP/1.1", upstream: "http://172.26.0.8:8000/api/v1/auth", host: "taiga.lan:25080", referrer: "http://taiga.lan:25080/login?force_login"
taiga-gateway_1 | 192.168.2.4 - - [26/Aug/2021:01:14:11 +0000] "GET /events HTTP/1.1" 502 560 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-"
taiga-gateway_1 | 2021/08/26 01:14:11 [error] 31#31: *2323 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.2.4, server: , request: "GET /events HTTP/1.1", upstream: "http://172.26.0.7:8888/events", host: "taiga.lan:25080"
taiga-gateway_1 | 2021/08/26 01:14:11 [error] 31#31: *2325 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.2.4, server: , request: "GET /events HTTP/1.1", upstream: "http://172.26.0.7:88
88/events", host: "taiga.lan:25080"
taiga-gateway_1 | 192.168.2.4 - - [26/Aug/2021:01:14:11 +0000] "GET /events HTTP/1.1" 502 560 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-"
taiga-gateway_1 | 2021/08/26 01:14:11 [error] 31#31: *2327 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.2.4, server: , request: "GET /events HTTP/1.1", upstream: "http://172.26.0.7:88
88/events", host: "taiga.lan:25080"
taiga-gateway_1 | 192.168.2.4 - - [26/Aug/2021:01:14:11 +0000] "GET /events HTTP/1.1" 502 560 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-"
taiga-gateway_1 | 2021/08/26 01:14:12 [error] 31#31: *2329 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.2.4, server: , request: "GET /events HTTP/1.1", upstream: "http://172.26.0.7:88
88/events", host: "taiga.lan:25080"
Maybe this is a db issue at the same time?
88/events", host: "taiga.lan:25080"
taiga-gateway_1 | 2021/08/26 04:18:17 [error] 32#32: *1545 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.2.4, server: , request: "GET /events HTTP/1.1", upstream: "http://172.18.0.7:88
88/events", host: "taiga.lan:25080"
taiga-gateway_1 | 192.168.2.4 - - [26/Aug/2021:04:18:17 +0000] "GET /events HTTP/1.1" 502 560 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-"
taiga-db_1 | 2021-08-26 04:18:18.188 UTC [26] LOG: redo starts at 0/43E3BB8
taiga-db_1 | 2021-08-26 04:18:18.188 UTC [26] LOG: invalid record length at 0/43E3CD8: wanted 24, got 0
taiga-db_1 | 2021-08-26 04:18:18.188 UTC [26] LOG: redo done at 0/43E3CA0
taiga-gateway_1 | 2021/08/26 04:18:18 [error] 32#32: *1547 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.2.4, server: , request: "GET /events HTTP/1.1", upstream: "http://172.18.0.7:88
88/events", host: "taiga.lan:25080"
taiga-gateway_1 | 192.168.2.4 - - [26/Aug/2021:04:18:18 +0000] "GET /events HTTP/1.1" 502 560 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36" "-"
taiga-gateway_1 | 2021/08/26 04:18:19 [error] 32#32: *1549 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.2.4, server: , request: "GET /events HTTP/1.1", upstream: "http://172.18.0.7:88
88/events", host: "taiga.lan:25080"
taiga-gateway_1 | 192.168.2.4 - - [26/Aug/2021:04:18:19 +0000] "GET /events HTTP/1.1" 502 560 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36"
After struggling for many hours with this, I reverted it back to tag 6.2.0 using the Docker release tag and it works again. So it is clear that a change is in 6.3.0 is breaking my deployment not sure if anyone else has the same issue.
I can confirm this bug too, tried 6.3.0 but it says my username/password are wrong and if I try to recover it, it says it doesn't exist.
Hi @gerroon,
Thanks for reporting this. In order to help us understand your context, can you send us a start up docker-compose logs report, your docker-compose.yml regarding the affected services, and, if exists, your Ngix or your proxy configuration?
Thank in advance
I can confirm the same issue here. It looks like there is no user created at all. Current release does not work with docker-compose up.
@gerroon How did you make it work? When checking out 6.2.0 tag it still pulls in the latest releases frontend, backend , etc.
Best, Chris
@gerroon How did you make it work? When checking out 6.2.0 tag it still pulls in the latest releases frontend, backend , etc.
Best, Chris
I just used something like this for all the taiga containers image: taigaio/taiga-back:6.2.0
Hi @gerroon,
Thanks for reporting this. In order to help us understand your context, can you send us a start up
docker-compose logsreport, yourdocker-compose.ymlregarding the affected services, and, if exists, your Ngix or your proxy configuration?Thank in advance
I actually do not want to go back to 6.3 since that was quite painful. I am back to 6.2 so I cant provide you any logs but here is my docker compose
version: "3.5"
x-environment:
&default-back-environment
# Database settings
POSTGRES_DB: taiga
POSTGRES_USER: taiga
POSTGRES_PASSWORD: taiga
POSTGRES_HOST: taiga-db
# Taiga settings
TAIGA_SECRET_KEY: "xxx"
TAIGA_SITES_DOMAIN: "taiga.lan:10000"
TAIGA_SITES_SCHEME: "http"
TAIGA_SUBPATH: ""
# Email settings. Uncomment following lines and configure your SMTP server
# EMAIL_BACKEND: "django.core.mail.backends.smtp.EmailBackend"
# DEFAULT_FROM_EMAIL: "[email protected]"
# EMAIL_USE_TLS: "False"
# EMAIL_USE_SSL: "False"
# EMAIL_HOST: "smtp.host.example.com"
# EMAIL_PORT: 587
# EMAIL_HOST_USER: "user"
# EMAIL_HOST_PASSWORD: "password"
# Rabbitmq settings
# Should be the same as in taiga-async-rabbitmq and taiga-events-rabbitmq
RABBITMQ_USER: taiga
RABBITMQ_PASS: taiga
# Telemetry settings
ENABLE_TELEMETRY: "False"
x-volumes:
&default-back-volumes
- /media/taiga2/data:/taiga-back/static
- /media/taiga2/meddata:/taiga-back/media
# - ./config.py:/taiga-back/settings/config.py
services:
taiga-db:
image: postgres:12.3
environment:
POSTGRES_DB: taiga
POSTGRES_USER: taiga
POSTGRES_PASSWORD: taiga
volumes:
- /media/taiga2/datab:/var/lib/postgresql/data
networks:
- taiga
taiga-back:
image: taigaio/taiga-back:6.2.0
environment: *default-back-environment
volumes: *default-back-volumes
networks:
- taiga
depends_on:
- taiga-db
- taiga-events-rabbitmq
- taiga-async-rabbitmq
taiga-async:
image: taigaio/taiga-back:6.2.0
entrypoint: ["/taiga-back/docker/async_entrypoint.sh"]
environment: *default-back-environment
volumes: *default-back-volumes
networks:
- taiga
depends_on:
- taiga-db
- taiga-back
- taiga-async-rabbitmq
taiga-async-rabbitmq:
image: rabbitmq:3.8-management-alpine
environment:
RABBITMQ_ERLANG_COOKIE: secret-erlang-cookie
RABBITMQ_DEFAULT_USER: taiga
RABBITMQ_DEFAULT_PASS: taiga
RABBITMQ_DEFAULT_VHOST: taiga
volumes:
- /media/taiga2/rb:/var/lib/rabbitmq
networks:
- taiga
taiga-front:
image: taigaio/taiga-front:6.2.0
environment:
TAIGA_URL: "http://taiga.lan:10000"
TAIGA_WEBSOCKETS_URL: "ws://taiga.lan:10000"
TAIGA_SUBPATH: "/"
PUBLIC_REGISTER_ENABLED: "true"
networks:
- taiga
# volumes:
# - ./conf.json:/usr/share/nginx/html/conf.json
taiga-events:
image: taigaio/taiga-events:6.2.0
environment:
RABBITMQ_USER: taiga
RABBITMQ_PASS: taiga
TAIGA_SECRET_KEY: "xxxxx"
networks:
- taiga
depends_on:
- taiga-events-rabbitmq
taiga-events-rabbitmq:
image: rabbitmq:3.8-management-alpine
environment:
RABBITMQ_ERLANG_COOKIE: secret-erlang-cookie
RABBITMQ_DEFAULT_USER: taiga
RABBITMQ_DEFAULT_PASS: taiga
RABBITMQ_DEFAULT_VHOST: taiga
volumes:
- /media/taiga2/rb:/var/lib/rabbitmq
networks:
- taiga
taiga-protected:
image: taigaio/taiga-protected:6.2.0
environment:
MAX_AGE: 360
SECRET_KEY: "xxxx"
networks:
- taiga
taiga-gateway:
image: nginx:1.19-alpine
ports:
- "10000:80"
- "8000:8000"
volumes:
- ./taiga-gateway/taiga.conf:/etc/nginx/conf.d/default.conf
- /media/taiga2/data:/taiga/static
- /media/taiga2/meddata:/taiga/media
networks:
- taiga
depends_on:
- taiga-front
- taiga-back
- taiga-events
volumes:
taiga-static-data:
taiga-media-data:
taiga-db-data:
taiga-async-rabbitmq-data:
taiga-events-rabbitmq-data:
networks:
taiga:
Hi, somehow the switchback to tag 6.2.0 had no effect. The default login user:password admin:123123 did not work.
Message (frontend):
Oops, something went wrong... According to the Taiga, your username/email or password are incorrect.
Also when entering the "admin" username on the forget-page no user of name admin is found.
Message:
Oops, something went wrong... According to the Taiga, you are not registered yet.
So it still looks like the user is not present at all in the database i guess.
Best, Chris
Just to mention: After modifying the /taiga-back/taiga/projects/management/commands/sample_data.py and hardcoding (for testing) the admin username, rerunning python manage.py sample_data it works.
Just to mention: After modifying the /taiga-back/taiga/projects/management/commands/sample_data.py and hardcoding (for testing) the admin username, rerunning
python manage.py sample_datait works.
Sure, but how would that work for existing database with existing users?
I missed the fact that you run an existing instance. But the same/related issue occured for initial setups as well. When i pull the latest image with persistent data already in place, it works as expected at using the latest (modified for my domain and volumes) docker-compose.yml from this repo assuming that my inital setup was configured like mentioned above.
I experienced some delays during rabbitmq startup which also caused the same error.
Could there be any issues with your nginx or possibly reverse proxy configs?
@gerroon I „also“ faced the same issue when the
RABBITMQ_ERLANG_COOKIE could not be set due to disk space issues which can happen quite easily with docker setups.
Maybe It is working for you now because you have started the data with 6.3? I have a lot of space where my Docker data is stored, and I have not changed any of my proxy settings between 6.2 and 6.3 pull, so it can't be that either. 6.2 works as expected so those are no issues as far as I can tell. Someone else also reported to have the same problem above.
Same problem here with docker v20.10.10 running @ windows. Sorry I am a numb user concerning docker.
Followed the basic installation steps
Same problem here with docker v20.10.10 running @ windows. Sorry I am a numb user concerning docker.
Followed the basic installation steps
I am having the same issue
The issue, for me, seemed to be that taiga-back did not wait until taiga-db was actually ready to listen to connections to 5432 (the readiness for docker-compose is too early compared to the actual readiness of the postgres server). So taiga-back committed seppuku because of django being unable to reach taiga-db:5432:
docker-compose ps
Name Command State Ports
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
taiga-docker_taiga-async-rabbitmq_1 docker-entrypoint.sh rabbi ... Up 15671/tcp, 15672/tcp, 15691/tcp, 15692/tcp, 25672/tcp, 4369/tcp, 5671/tcp, 5672/tcp
taiga-docker_taiga-async_1 /taiga-back/docker/async_e ... Up 8000/tcp
taiga-docker_taiga-back_1 ./docker/entrypoint.sh Exit 1
taiga-docker_taiga-db_1 docker-entrypoint.sh postgres Up 5432/tcp
taiga-docker_taiga-events-rabbitmq_1 docker-entrypoint.sh rabbi ... Up 15671/tcp, 15672/tcp, 15691/tcp, 15692/tcp, 25672/tcp, 4369/tcp, 5671/tcp, 5672/tcp
taiga-docker_taiga-events_1 ./docker/entrypoint.sh Up 8888/tcp
taiga-docker_taiga-front_1 /docker-entrypoint.sh ngin ... Up 80/tcp
taiga-docker_taiga-gateway_1 /docker-entrypoint.sh ngin ... Up 0.0.0.0:9000->80/tcp,:::9000->80/tcp
taiga-docker_taiga-protected_1 ./docker/entrypoint.sh Up 8003/tcp
Logs
...
taiga-back_1 | django.db.utils.OperationalError: could not connect to server: Connection refused
taiga-back_1 | Is the server running on host "taiga-db" (172.21.0.5) and accepting
taiga-back_1 | TCP/IP connections on port 5432?
Restarting the container (by sending another docker-compose up -d 1/2 min after the initial start) fixed the problem for me
Does something, but still having the same error.
docker-compose up -d
WARNING: Found orphan containers (taiga-docker_penpot-backend_1, taiga-docker_penpot-exporter_1, taiga-docker_penpot-frontend_1, taiga-docker_penpot-redis_1, taiga-docker_penpot-postgres_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
taiga-docker_taiga-db_1 is up-to-date
taiga-docker_taiga-protected_1 is up-to-date
taiga-docker_taiga-async-rabbitmq_1 is up-to-date
taiga-docker_taiga-front_1 is up-to-date
taiga-docker_taiga-events-rabbitmq_1 is up-to-date
Recreating taiga-docker_taiga-back_1 ...
Recreating taiga-docker_taiga-back_1 ... done
Recreating taiga-docker_taiga-async_1 ... done
Recreating taiga-docker_taiga-gateway_1 ... done
We did a complete re-installation.
launch-all.sh
docker-compose up -d
WARNING: Found orphan containers (taiga-docker_penpot-backend_1, taiga-docker_penpot-redis_1, taiga-docker_penpot-exporter_1, taiga-docker_penpot-postgres_1, taiga-docker_penpot-frontend_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
taiga-docker_taiga-db_1 is up-to-date
taiga-docker_taiga-protected_1 is up-to-date
taiga-docker_taiga-async-rabbitmq_1 is up-to-date
taiga-docker_taiga-front_1 is up-to-date
taiga-docker_taiga-events-rabbitmq_1 is up-to-date
Recreating taiga-docker_taiga-back_1 ...
Recreating taiga-docker_taiga-back_1 ... done
Recreating taiga-docker_taiga-async_1 ... done
Recreating taiga-docker_taiga-gateway_1 ... done
taiga-manage.sh createsuperuser
Still the same error Dockker is upped to version 4.3.0 (71786)
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.
