Taiga-docker-taiga-db-1 FATAL: role "taiga" does not exist, taiga-docker-taiga-async-rabbitmq-1 | PLAIN login refused: user 'taiga' - invalid credentials error

Troubleshooting Self hosted Taiga
,
1

Hey, Would appreciate your help on this error as I am not sure what is wrong as I am using a very stock environment.

Running an updated Ubuntu 20.1 Server with the cloned Taiga-Docker repo found at (GitHub - kaleidos-ventures/taiga-docker)

Using the docker-compose command via ./launch-taiga.sh with default .env file settings for user/pass of each account to test out.

UFW disabled, NGINX established properly.

It yields this output error, it doesn’t resolve after waiting and results in a continuous string of fatal errors.

docker compose -f docker-compose.yml up
[+] Running 9/0
 ✔ Container taiga-docker-taiga-front-1            Created                                                                      0.0s 
 ✔ Container taiga-docker-taiga-protected-1        Created                                                                      0.0s 
 ✔ Container taiga-docker-taiga-db-1               Created                                                                      0.0s 
 ✔ Container taiga-docker-taiga-events-rabbitmq-1  Created                                                                      0.0s 
 ✔ Container taiga-docker-taiga-events-1           Created                                                                      0.0s 
 ✔ Container taiga-docker-taiga-async-rabbitmq-1   Created                                                                      0.0s 
 ✔ Container taiga-docker-taiga-async-1            Created                                                                      0.0s 
 ✔ Container taiga-docker-taiga-back-1             Created                                                                      0.0s 
 ✔ Container taiga-docker-taiga-gateway-1          Created                                                                      0.0s 
Attaching to taiga-docker-taiga-async-1, taiga-docker-taiga-async-rabbitmq-1, taiga-docker-taiga-back-1, taiga-docker-taiga-db-1, taiga-docker-taiga-events-1, taiga-docker-taiga-events-rabbitmq-1, taiga-docker-taiga-front-1, taiga-docker-taiga-gateway-1, taiga-docker-taiga-protected-1
taiga-docker-taiga-protected-1        | Give permission to taiga:taiga
taiga-docker-taiga-protected-1        | Starting Taiga Protected
taiga-docker-taiga-events-rabbitmq-1  | 
taiga-docker-taiga-events-rabbitmq-1  | warning: /var/lib/rabbitmq/.erlang.cookie contents do not match RABBITMQ_ERLANG_COOKIE
taiga-docker-taiga-events-rabbitmq-1  | 
taiga-docker-taiga-events-rabbitmq-1  | 
taiga-docker-taiga-events-rabbitmq-1  | WARNING: '/var/lib/rabbitmq/.erlang.cookie' was populated from '$RABBITMQ_ERLANG_COOKIE', which will no longer happen in 3.9 and later! (https://github.com/docker-library/rabbitmq/pull/424)
taiga-docker-taiga-front-1            | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
taiga-docker-taiga-front-1            | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
taiga-docker-taiga-front-1            | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
taiga-docker-taiga-front-1            | 10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
taiga-docker-taiga-db-1               | 
taiga-docker-taiga-db-1               | PostgreSQL Database directory appears to contain a database; Skipping initialization
taiga-docker-taiga-db-1               | 
taiga-docker-taiga-db-1               | 
taiga-docker-taiga-async-rabbitmq-1   | 
taiga-docker-taiga-async-rabbitmq-1   | warning: /var/lib/rabbitmq/.erlang.cookie contents do not match RABBITMQ_ERLANG_COOKIE
taiga-docker-taiga-async-rabbitmq-1   | 
taiga-docker-taiga-async-rabbitmq-1   | 
taiga-docker-taiga-async-rabbitmq-1   | WARNING: '/var/lib/rabbitmq/.erlang.cookie' was populated from '$RABBITMQ_ERLANG_COOKIE', which will no longer happen in 3.9 and later! (https://github.com/docker-library/rabbitmq/pull/424)
taiga-docker-taiga-async-rabbitmq-1   | 
taiga-docker-taiga-db-1               | 2023-08-15 23:50:48.441 UTC [1] LOG:  starting PostgreSQL 12.3 (Debian 12.3-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
taiga-docker-taiga-db-1               | 2023-08-15 23:50:48.447 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
taiga-docker-taiga-db-1               | 2023-08-15 23:50:48.448 UTC [1] LOG:  listening on IPv6 address "::", port 5432
taiga-docker-taiga-db-1               | 2023-08-15 23:50:48.451 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
taiga-docker-taiga-db-1               | 2023-08-15 23:50:48.541 UTC [25] LOG:  database system was shut down at 2023-08-15 23:49:56 UTC
taiga-docker-taiga-db-1               | 2023-08-15 23:50:48.553 UTC [1] LOG:  database system is ready to accept connections
taiga-docker-taiga-events-1           | Starting Taiga events
taiga-docker-taiga-front-1            | 10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf differs from the packaged version
taiga-docker-taiga-front-1            | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
taiga-docker-taiga-front-1            | /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
taiga-docker-taiga-front-1            | /docker-entrypoint.sh: Launching /docker-entrypoint.d/30_config_env_subst.sh
taiga-docker-taiga-front-1            | /docker-entrypoint.sh: Configuration complete; ready for start up
taiga-docker-taiga-db-1               | 2023-08-15 23:50:50.742 UTC [39] FATAL:  role "taiga" does not exist

//LATER ON IN THE OUTPUT

taiga-docker-taiga-async-1            | [2023-08-15 23:51:12,312: ERROR/MainProcess] consumer: Cannot connect to amqp://taiga:**@taiga-async-rabbitmq:5672/taiga: [Errno 111] Connection refused.
taiga-docker-taiga-async-1            | Trying again in 2.00 seconds... (1/100)
taiga-docker-taiga-async-1            | 
taiga-docker-taiga-async-1            | 
taiga-docker-taiga-async-rabbitmq-1   | WARNING: 'docker-entrypoint.sh' generated/modified the RabbitMQ configuration file, which will no longer happen in 3.9 and later! (https://github.com/docker-library/rabbitmq/pull/424)
taiga-docker-taiga-async-rabbitmq-1   | 
taiga-docker-taiga-async-rabbitmq-1   | Generated end result, for reference:
taiga-docker-taiga-async-rabbitmq-1   | ------------------------------------
taiga-docker-taiga-async-rabbitmq-1   | loopback_users.guest = false
taiga-docker-taiga-async-rabbitmq-1   | 
taiga-docker-taiga-async-rabbitmq-1   | listeners.tcp.default = 5672
taiga-docker-taiga-async-rabbitmq-1   | 
taiga-docker-taiga-async-rabbitmq-1   | default_pass = thisisatestpassword
taiga-docker-taiga-async-rabbitmq-1   | 
taiga-docker-taiga-async-rabbitmq-1   | default_user = taiga
taiga-docker-taiga-async-rabbitmq-1   | 
taiga-docker-taiga-async-rabbitmq-1   | default_vhost = taiga
taiga-docker-taiga-async-rabbitmq-1   | 
taiga-docker-taiga-async-rabbitmq-1   | management.tcp.port = 15672
taiga-docker-taiga-async-rabbitmq-1   | ------------------------------------
taiga-docker-taiga-async-rabbitmq-1   | 
taiga-docker-taiga-events-rabbitmq-1  | WARNING: 'docker-entrypoint.sh' generated/modified the RabbitMQ configuration file, which will no longer happen in 3.9 and later! (https://github.com/docker-library/rabbitmq/pull/424)
taiga-docker-taiga-events-rabbitmq-1  | 
taiga-docker-taiga-events-rabbitmq-1  | Generated end result, for reference:
taiga-docker-taiga-events-rabbitmq-1  | ------------------------------------
taiga-docker-taiga-events-rabbitmq-1  | 
taiga-docker-taiga-events-rabbitmq-1  | loopback_users.guest = false
taiga-docker-taiga-events-rabbitmq-1  | 
taiga-docker-taiga-events-rabbitmq-1  | listeners.tcp.default = 5672
taiga-docker-taiga-events-rabbitmq-1  | 
taiga-docker-taiga-events-rabbitmq-1  | default_pass = thisisatestpassword
taiga-docker-taiga-events-rabbitmq-1  | 
taiga-docker-taiga-events-rabbitmq-1  | default_user = taiga
taiga-docker-taiga-events-rabbitmq-1  | 
taiga-docker-taiga-events-rabbitmq-1  | default_vhost = taiga
taiga-docker-taiga-events-rabbitmq-1  | 
taiga-docker-taiga-events-rabbitmq-1  | management.tcp.port = 15672
taiga-docker-taiga-events-rabbitmq-1  | 
taiga-docker-taiga-events-rabbitmq-1  | ------------------------------------
taiga-docker-taiga-async-1            | [2023-08-15 23:51:14,369: ERROR/MainProcess] consumer: Cannot connect to amqp://taiga:**@taiga-async-rabbitmq:5672/taiga: [Errno 111] Connection refused.

Appreciate your help as I have troubleshooted everything I can on my own.

2

Hi, @87cb5fm0

taiga-docker-taiga-db-1               | 2023-08-15 23:50:50.742 UTC [39] FATAL:  role "taiga" does not exist

Typically this error is caused by first initializing the database postgresql with a certain username or password and then changing the settings to other values.

Here are two options:

  • access the database and change the owner
  • or, if data loss is not a problem, delete the volume from the database (taiga-db)

I hope this can help.

Best regards

1 Like
3

@david.barragan

Thank you, after troubleshooting with your help I was able to find the problem and recreate it, the instance is running perfectly fine now.

This is an area to improve in documentation as it wasn’t clear that In the .env file I am not able to change the POSTGRES_USER to a new value, such as randomuser123. Not sure why but it ends up calling the postgres database randomuser123 as well on startup and throws an error “FATAL ERROR: database randomuser123 cannot be found”

What’s interesting is that the docker-compose.yml defines what the database name should be, “taiga”

Here’s the part of the .env file in question:

Taiga’s Database settings - Variables to create the Taiga database and connect to it

POSTGRES_USER=taiga # user to connect to PostgreSQL Suggest adding disclaimer here to not change this username.
POSTGRES_PASSWORD=taiga # database user’s password

4

Also found there is a character limit before 128 characters for passwords, might be good to define what the limits and special character requirements are.

5

I’m glad everything is working now :slight_smile:

Well, since the database services and rabbitmq run on an internal network that no one who doesn’t have access to the host machine will be able to access, it doesn’t make much sense to change those default values. Security will not be increased.

I think maybe we should “hide” those settings for those users who require more advanced customization. For most cases, changing the SECRET, configuring the smtp server for the mailing and configuring the URLs would be enough.