Need help setting up Taiga

276 views
Skip to first unread message

Rafael

unread,
Feb 21, 2021, 4:45:22 AMFeb 21
to taigaio
Hello, I'm trying to set up taiga-docker on my VPS but something isnt right, I log in with the superuser created with sudo ./taiga-manage.sh createsuperuser  and try to create a new proyect but it just stays loading, if I refresh the page after a long time it doesnt show in "my proyects" but, if I log out and go to the /discover page, it shows, but as Scrum instead of Kanban and like this: pic-selected-210221-0335-56.png

What could be wrong? This are the steps I followed:
  1. cloned the repo
  2. set up nginx with the step 1.9 from here https://taigaio.github.io/taiga-doc/dist/setup-production.html
  3. changed TAIGA_URL: "http://localhost:9000" TAIGA_WEBSOCKETS_URL: "ws://localhost:9000" to my domain
  4. ran $sudo ./launch-taiga.sh and $sudo ./taiga-manage.sh createsuperuser
After that I tried changing most variables to personalized names and passwords to no success.

I'm sorry for wasting your time and would appreciate any guidance.

Si se facilita ayudar en español, también funciona.

Muchas gracias.

Yamila Moreno

unread,
Feb 22, 2021, 9:39:00 AMFeb 22
to Rafael, taigaio
Hi Rafael,

On Sun, Feb 21, 2021 at 10:45 AM Rafael <r44...@gmail.com> wrote:
Hello, I'm trying to set up taiga-docker on my VPS but something isnt right, I log in with the superuser created with sudo ./taiga-manage.sh createsuperuser  and try to create a new proyect but it just stays loading, if I refresh the page after a long time it doesnt show in "my proyects" but, if I log out and go to the /discover page, it shows, but as Scrum instead of Kanban and like this: 

What could be wrong? This are the steps I followed:
  1. cloned the repo
  2. set up nginx with the step 1.9 from here https://taigaio.github.io/taiga-doc/dist/setup-production.html
  3. changed TAIGA_URL: "http://localhost:9000" TAIGA_WEBSOCKETS_URL: "ws://localhost:9000" to my domain
your domain being something like "taiga.mydomain.com", is that?
 
  1. ran $sudo ./launch-taiga.sh and $sudo ./taiga-manage.sh createsuperuser
After that I tried changing most variables to personalized names and passwords to no success.

you mean you tried to change the variables after launching taiga?
what do you see if you type `docker-compose ps` in the `taiga-docker` repository?
 
I'm sorry for wasting your time and would appreciate any guidance.

No problem at all! These kind of doubts help us improve the documentation or even discover a bug.
 
Si se facilita ayudar en español, también funciona.

Better in english, so it's more accesible to other people with the same problem.
 
Muchas gracias.

¡a ti! :)

--
Logo Kaleidos Yamila Moreno Suárez
COO & Cofounder  
kaleidos.net
 


Este mensaje y sus archivos adjuntos van dirigidos exclusivamente a su destinatario, y pudiendo contener información confidencial sometida a secreto profesional, o cuya divulgación esté legalmente prohibida. Cualquier opinión en él contenida es exclusiva de su autor y no representa necesariamente la opinión de la empresa. Si ha recibido este mensaje por error, le rogamos nos lo comunique de forma inmediata por esta misma vía y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. El correo electrónico vía Internet no es seguro y no se puede garantizar que no haya errores ya que puede ser interceptado, modificado, perdido o destruido, o contener virus. Cualquier persona que se ponga en contacto con nosotros por correo electrónico se considerará que asume estos riesgos.

KALEIDOS OPEN SOURCE se reserva las acciones legales que le correspondan contra todo tercero que acceda de forma ilegítima al contenido de cualquier mensaje externo procedente del mismo.

INFORMACIÓN PROTECCIÓN DE DATOS. Responsable: KALEIDOS OPEN SOURCE (B86241973)

Le informamos que sus datos identificativos y los contenidos en los correos electrónicos y ficheros adjuntos pueden ser incorporados a nuestras bases de datos con la finalidad de mantener relaciones profesionales y/o comerciales y, que serán conservados mientras se mantenga la relación. Si lo desea, puede ejercer su derecho a acceder, rectificar y suprimir sus datos y demás reconocidos normativamente dirigiéndose al correo emisor o en los datos del responsable. Para información y consultas visite nuestra web  https://kaleidos.net

Yamila Moreno

unread,
Feb 23, 2021, 2:36:54 AMFeb 23
to Rafael, taigaio
You can see taiga-async is failing (Exit). Can you check and share the logs of this container?

On Mon, Feb 22, 2021 at 8:49 PM Rafael <r44...@gmail.com> wrote:
Hello!

1) Yes, my domain is taiga.mydomain.com

2) I have tried in three different servers, once I changed them after starting all the containers with the default parameters (and ran the ./launch-taiga.sh script again to rebuild the containers), the second one I used my own parameters (changing names, passwords, etc. always keeping it consistent across the different services) and now, finally, trying to find what went wrong, I'm just using the default parameters changing only my domain.

What's interesting is that every single attempt had the same problem as mentioned in my original mail (the screenshot).

Now, regarding docker-compose ps

pic-selected-210222-1335-43.png

What would be useful to share? and, should I keep sharing screenshots? maybe it's better to share the text.

Thank you very much.

Yamila Moreno

unread,
Feb 23, 2021, 4:41:22 AMFeb 23
to Rafael, taigaio
Rafael, don't forget to "REPLY ALL" as this will be helpful to others.

This are the logs from taiga-async,

[2021-02-23 09:17:48,447: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@None:5672//: failed to resolve broker hostname.
Trying again in 2.00 seconds...

[2021-02-23 09:17:50,476: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@None:5672//: failed to resolve broker hostname.
Trying again in 4.00 seconds...

[2021-02-23 09:17:50,856: INFO/Beat] beat: Starting...
[2021-02-23 09:17:52,971: ERROR/Beat] beat: Connection error: failed to resolve broker hostname. Trying again in 4.0 seconds...
[2021-02-23 09:17:54,505: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@None:5672//: failed to resolve broker hostname.
Trying again in 6.00 seconds...

[2021-02-23 09:17:56,992: ERROR/Beat] beat: Connection error: failed to resolve broker hostname. Trying again in 6.0 seconds...
[2021-02-23 09:18:00,521: ERROR/MainProcess] consumer: Cannot connect to amqp://gp

this mean that the configuration of taiga-async is not correct. "guest:guest" are default values that should be overriden. Something with the configuration is messed up.
 
and found out that I needed to use CELERY_BROKER_URL pointing at  point at amqp://user:password@broker:5672 to fix that, so I just added:

EVENTS_PUSH_BACKEND_URL: "amqp://taiga:taiga@taiga-events-rabbitmq:5672/taiga"
CELERY_BROKER_URL: "amqp://taiga:taiga@taiga-async-rabbitmq:5672/taiga"

You don't need this necessarily; this is an advanced setting, but if you're using default docker-compose they are not mandatory.
 
to docker-compose.yml, rebuild the containers and everything worked!

ok cool that it worked!

If I modify the user and password I would have to change those in these variables, right?

If you modify the user and password where? Not sure I understand this question.
 
One last thing, the installation guide doesn't say that you need these variables:
pic-selected-210223-0330-12.png
Is there a reason I needed them? the only thing out of the ordinary is that I was using http instead of https.

If you're using default docker-compose, you only need:
RABBITMQ_USER
RABBITMQ_PASS
It will use by default "taiga-async-rabbitmq" as host and 5672 as port.

If you're using these containers in a k8s cluster or in a different way than docker-compose, you may want to configure the whole amqp URL. But as far as I see, this is not your case.

Nonetheless, if it worked, you can keep them, as they are also a legit way to configure it.

Cheers!

Rafael

unread,
Feb 24, 2021, 3:57:37 AMFeb 24
to Yamila Moreno, taigaio
Everything worked on http but couldn't make it work on https, I tried the whole day to no success...
could someone guide me on how to debug this?

I think this is all what's relevant:

docker-compose.yml, docker-compose-inits.yml, my nginx server configuration and the output of docker-compose ps.


nginx server config:

server {
server_name taiga.mydomain.com;
  location / {
    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Scheme $scheme;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_redirect off;
    proxy_pass http://localhost:9000/;
  }
  # Events
  location /events {
      proxy_pass http://localhost:9000/events;
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection "upgrade";
      proxy_connect_timeout 7d;
      proxy_send_timeout 7d;
      proxy_read_timeout 7d;
  }
   listen [::]:443 ssl; # managed by Certbot
   listen 443 ssl; # managed by Certbot
   ssl_certificate /etc/letsencrypt/live/mydomain.com/fullchain.pem; # managed by Certbot
   ssl_certificate_key /etc/letsencrypt/live/mydomain.com/privkey.pem; # managed by Certbot
   include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
   ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
    if ($host = taiga.mydomain.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot
       server_name taiga.mydomain.com;
    listen [::]:80 ;
    listen 80 ;
   return 404; # managed by Certbot
}

docker-compose.yml:

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: "taiga-back-secret-key"
  TAIGA_SITES_DOMAIN: "taiga.mydomain.com"
  TAIGA_SITES_SCHEME: "https"
  RABBITMQ_USER: taiga
  RABBITMQ_PASS: taiga
  # Telemetry settings
  ENABLE_TELEMETRY: "True"
  
x-volumes:
  &default-back-volumes
  - taiga-static-data:/taiga-back/static
  - taiga-media-data:/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:
      - taiga-db-data:/var/lib/postgresql/data
    networks:
      - taiga

  taiga-back:
    image: taigaio/taiga-back:latest
    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:latest
    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-management-alpine
    environment:
      RABBITMQ_ERLANG_COOKIE: secret-erlang-cookie
      RABBITMQ_DEFAULT_USER: taiga
      RABBITMQ_DEFAULT_PASS: taiga
      RABBITMQ_DEFAULT_VHOST: taiga
    networks:
      - taiga

  taiga-front:
    image: taigaio/taiga-front:latest
    environment:
      TAIGA_URL: "https://taiga.mydomain.com"
      TAIGA_WEBSOCKETS_URL: "ws://taiga.mydomain.com"
    networks:
      - taiga
    # volumes:
    #   - ./conf.json:/usr/share/nginx/html/conf.json

  taiga-events:
    image: taigaio/taiga-events:latest
    environment:
      RABBITMQ_USER: taiga
      RABBITMQ_PASS: taiga
      TAIGA_SECRET_KEY: "taiga-back-secret-key"
    networks:
      - taiga
    depends_on:
      - taiga-events-rabbitmq

  taiga-events-rabbitmq:
    image: rabbitmq:3-management-alpine
    environment:
      RABBITMQ_ERLANG_COOKIE: secret-erlang-cookie
      RABBITMQ_DEFAULT_USER: taiga
      RABBITMQ_DEFAULT_PASS: taiga
      RABBITMQ_DEFAULT_VHOST: taiga
    networks:
      - taiga

  taiga-protected:
    image: taigaio/taiga-protected:latest
    environment:
      MAX_AGE: 360
      SECRET_KEY: "taiga-back-secret-key"
    networks:
      - taiga

  taiga-gateway:
    image: nginx:1.19-alpine
    ports:
      - "9000:80"
    volumes:
      - ./taiga-gateway/taiga.conf:/etc/nginx/conf.d/default.conf
      - taiga-static-data:/taiga/static
      - taiga-media-data:/taiga/media
    networks:
      - taiga
    depends_on:
      - taiga-front
      - taiga-back
      - taiga-events

volumes:
  taiga-static-data:
  taiga-media-data:
  taiga-db-data:

networks:
  taiga:

docker-compose ps:

             
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           Up      8000/tcp                                                                          
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                                                              
taiga-docker_taiga-protected_1         ./docker/entrypoint.sh           Up      8003/tcp         

docker-compose-inits.yml is identical to the one on the installation guide.
                                                                  

Thank you very much for your help

Yamila Moreno

unread,
Feb 24, 2021, 4:02:45 AMFeb 24
to Rafael, taigaio
Hi Rafael, in your docker-compose.yml:

      TAIGA_WEBSOCKETS_URL: "ws://taiga.mydomain.com"

should be "wss://taiga.mydomain.com"

Rafael

unread,
Feb 24, 2021, 4:44:07 AMFeb 24
to Yamila Moreno, taigaio
Thank you! EVERYTHING WORKS

Yamila Moreno

unread,
Feb 24, 2021, 4:46:46 AMFeb 24
to Rafael, taigaio
great!!

Дмитрий Вербецкий

unread,
Mar 2, 2021, 8:19:44 AMMar 2
to taigaio
hello

I have the same setting with topic starter 
and my taiga works, But I have WebSocket connections error in F12-console
also it strange problem if I go to taiga.domain/com/admin/  - css style doesn't load due to the error in console


среда, 24 февраля 2021 г. в 11:46:46 UTC+2, Yamila Moreno:

Marshalleq

unread,
Aug 14, 2021, 6:36:05 PMAug 14
to taigaio
I noticed this ws should be wss thing too - I'm not sure if Taiga realise this is actually stored this way in their original config files - and comes down via git pull.  That should really be updated by them to stop this re-occurring.
Reply all
Reply to author
Forward
0 new messages