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:
- cloned the repo
- set up nginx with the step 1.9 from here https://taigaio.github.io/taiga-doc/dist/setup-production.html
- changed TAIGA_URL: "http://localhost:9000" TAIGA_WEBSOCKETS_URL: "ws://localhost:9000" to my domain
- 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 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 |
Hello!1) Yes, my domain is taiga.mydomain.com2) 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 psWhat would be useful to share? and, should I keep sharing screenshots? maybe it's better to share the text.Thank you very much.
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
and found out that I needed to use CELERY_BROKER_URL pointing at point atamqp://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"
to docker-compose.yml, rebuild the containers and everything worked!
If I modify the user and password I would have to change those in these variables, right?
One last thing, the installation guide doesn't say that you need these variables:
Is there a reason I needed them? the only thing out of the ordinary is that I was using http instead of https.
docker-compose.yml: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/;}# Eventslocation /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 Certbotlisten 443 ssl; # managed by Certbotssl_certificate /etc/letsencrypt/live/mydomain.com/fullchain.pem; # managed by Certbotssl_certificate_key /etc/letsencrypt/live/mydomain.com/privkey.pem; # managed by Certbotinclude /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbotssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot}server {if ($host = taiga.mydomain.com) {return 301 https://$host$request_uri;} # managed by Certbotserver_name taiga.mydomain.com;listen [::]:80 ;listen 80 ;return 404; # managed by Certbot}
version: "3.5"x-environment:&default-back-environment# Database settingsPOSTGRES_DB: taigaPOSTGRES_USER: taigaPOSTGRES_PASSWORD: taigaPOSTGRES_HOST: taiga-db# Taiga settingsTAIGA_SECRET_KEY: "taiga-back-secret-key"TAIGA_SITES_DOMAIN: "taiga.mydomain.com"TAIGA_SITES_SCHEME: "https"RABBITMQ_USER: taigaRABBITMQ_PASS: taiga# Telemetry settingsENABLE_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.pyservices:taiga-db:image: postgres:12.3environment:POSTGRES_DB: taigaPOSTGRES_USER: taigaPOSTGRES_PASSWORD: taigavolumes:- taiga-db-data:/var/lib/postgresql/datanetworks:- taigataiga-back:image: taigaio/taiga-back:latestenvironment: *default-back-environmentvolumes: *default-back-volumesnetworks:- taigadepends_on:- taiga-db- taiga-events-rabbitmq- taiga-async-rabbitmqtaiga-async:image: taigaio/taiga-back:latestentrypoint: ["/taiga-back/docker/async_entrypoint.sh"]environment: *default-back-environmentvolumes: *default-back-volumesnetworks:- taigadepends_on:- taiga-db- taiga-back- taiga-async-rabbitmqtaiga-async-rabbitmq:image: rabbitmq:3-management-alpineenvironment:RABBITMQ_ERLANG_COOKIE: secret-erlang-cookieRABBITMQ_DEFAULT_USER: taigaRABBITMQ_DEFAULT_PASS: taigaRABBITMQ_DEFAULT_VHOST: taiganetworks:- taigataiga-front:image: taigaio/taiga-front:latestenvironment:TAIGA_URL: "https://taiga.mydomain.com"TAIGA_WEBSOCKETS_URL: "ws://taiga.mydomain.com"networks:- taiga# volumes:# - ./conf.json:/usr/share/nginx/html/conf.jsontaiga-events:image: taigaio/taiga-events:latestenvironment:RABBITMQ_USER: taigaRABBITMQ_PASS: taigaTAIGA_SECRET_KEY: "taiga-back-secret-key"networks:- taigadepends_on:- taiga-events-rabbitmqtaiga-events-rabbitmq:image: rabbitmq:3-management-alpineenvironment:RABBITMQ_ERLANG_COOKIE: secret-erlang-cookieRABBITMQ_DEFAULT_USER: taigaRABBITMQ_DEFAULT_PASS: taigaRABBITMQ_DEFAULT_VHOST: taiganetworks:- taigataiga-protected:image: taigaio/taiga-protected:latestenvironment:MAX_AGE: 360SECRET_KEY: "taiga-back-secret-key"networks:- taigataiga-gateway:image: nginx:1.19-alpineports:- "9000:80"volumes:- ./taiga-gateway/taiga.conf:/etc/nginx/conf.d/default.conf- taiga-static-data:/taiga/static- taiga-media-data:/taiga/medianetworks:- taigadepends_on:- taiga-front- taiga-back- taiga-eventsvolumes:taiga-static-data:taiga-media-data:taiga-db-data:networks:taiga:
docker-compose-inits.yml is identical to the one on the installation guide.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/tcptaiga-docker_taiga-async_1 /taiga-back/docker/async_e ... Up 8000/tcptaiga-docker_taiga-back_1 ./docker/entrypoint.sh Up 8000/tcptaiga-docker_taiga-db_1 docker-entrypoint.sh postgres Up 5432/tcptaiga-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/tcptaiga-docker_taiga-events_1 ./docker/entrypoint.sh Up 8888/tcptaiga-docker_taiga-front_1 /docker-entrypoint.sh ngin ... Up 80/tcptaiga-docker_taiga-gateway_1 /docker-entrypoint.sh ngin ... Up 0.0.0.0:9000->80/tcptaiga-docker_taiga-protected_1 ./docker/entrypoint.sh Up 8003/tcp