kaleidos-ventures / taiga-docker Goto Github PK
View Code? Open in Web Editor NEWLicense: Mozilla Public License 2.0
License: Mozilla Public License 2.0
Is it OK that in docker-compose service images point to taigaio/ repos instead of kaleidos-ventures/ ones?
Hiya,
not sure if this is a bug or something I've done wrong.
I've tried this both with the old git and this one and get the same error (browser console):
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. taiga:9000
Your conf.json file is not a valid json file, please review it. app-loader.js:1:1451
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8000/api/v1/projects?discover_mode=true&order_by=-total_activity_last_year. (Reason: CORS request did not succeed).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8000/api/v1/stats/discover. (Reason: CORS request did not succeed).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8000/api/v1/projects?discover_mode=true&order_by=-total_activity_last_year. (Reason: CORS request did not succeed).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8000/api/v1/projects?discover_mode=true&order_by=-total_fans_last_year. (Reason: CORS request did not succeed).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8000/api/v1/projects?discover_mode=true&is_featured=true. (Reason: CORS request did not succeed).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8000/api/v1/stats/discover. (Reason: CORS request did not succeed).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8000/api/v1/projects?discover_mode=true&order_by=-total_fans_last_year. (Reason: CORS request did not succeed).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8000/api/v1/projects?discover_mode=true&is_featured=true. (Reason: CORS request did not succeed).
I don't see any errors in the logs after doing docker-compose up -d
or ./launch-taiga.sh
/ ./launch-all.sh
(I had an issue originally with not being able to create superuser but solved it with populating the database using python manage.py loaddata initial_user
)
in journalctl I see some messages about sending mail, so probably not related:
[2021-05-16 10:16:29,589: INFO/MainProcess] Received task: taiga.projects.notifications.tasks.send_bulk_email
[2021-05-16 10:16:29,583: INFO/Beat] Scheduler: Sending due task send-bulk-emails
in my docker-compose files I have only changed the passwords, site from which to serve to the hostname of the server instead of "localhost:9000" as well as adding PUBLIC_REGISTER_ENABLED: "True"
to the end of &default-back-environment and taiga-front
I have nginx-proxy-manager setup and forward to the hostname on port 9000, using this in the advanced tab:
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://the-hostname:9000/;
}
I use nginx-proxy-manager for SSL termination which might cause some troubles but I had this working a few days ago with the old taigaio/taiga-docker. However, I get the same error whether connecting directly to http://the-hostname:9000 on the local network or https://the.public.url
The only difference in the compose files is that I added the public_register enabled env var and the penpot related stuff was pulled.
I didnt do anything with the Advanced config so not sure why it is complaining about an invalid json file.
edit: I copied the file referenced the advanced config and mapped it to the suggested location and still get teh same error re: invalid json file
Your conf.json file is not a valid json file, please review it.
<anonymous> app-loader.js:1
jQuery 4
i
fireWith
_
o
v elements.js:9
value elements.js:9
value elements.js:9
value elements.js:9
o elements.js:9
m elements.js:9
Hi
I am using this Docker setup. As far as I can tell everything works except opening the attachments in the Issues or Kanban issues.
I am able to attach them to the issues alright without error. I also see them written to the media volume I provided. So theya re definetely uploaded, it seems to be an issue with showing them in the frontend when clicked on them.
My url is http:\\taiga.lan:9090
I had to change the port since it was taken already. I added taiga.lan
to my hosts
I am accessing it from the local network so no proxy is involved. Looking at the error, it seems like the media serving is not considering the port.
I get
http://taiga.lan/media/attachments/0/2/2/a/24f30eb70431157a3cdd7f32d839ed2fa4de50f3f42bbbc75936ba599a17/szegedzsinagoga.jpg?token=YL109w%3AIopecqMaCfzOz6g_F44Yo8FKIfn3pyUEzbK_Isiagcw3HPvwCNcUtsDbD7cLI2LGjxBuvxegBJlAt1xS-NFQEA 404 (Not Found)
Image (async)
a @ app.js:3022
Show 197 more frames
/media/attachments/0/2/2/a/24f30eb70431157a3cdd7f32d839ed2fa4de50f3f42bbbc75936ba599a17/szegedzsinagoga.jpg?token=YL11Bg%3AZT-gW0b8xyOXbDaTuCMyAdbiOiK-ThAi2TaqvWFC4oL-hA_ZhlfoZNizHi-6olBmwX1-V7mb4jUux0awebMiPA#_taiga-refresh=userstory:4:1 GET http://taiga.lan/media/attachments/0/2/2/a/24f30eb70431157a3cdd7f32d839ed2fa4de50f3f42bbbc75936ba599a17/szegedzsinagoga.jpg?token=YL11Bg%3AZT-gW0b8xyOXbDaTuCMyAdbiOiK-ThAi2TaqvWFC4oL-hA_ZhlfoZNizHi-6olBmwX1-V7mb4jUux0awebMiPA 4
Hello I have deployed Taiga on my server, I am not able to sign up through /register
and ./taiga-manage.sh test_email <my email>
is giving the error shown below
Traceback (most recent call last):
File "manage.py", line 17, in <module>
execute_from_command_line(sys.argv)
File "/opt/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
utility.execute()
File "/opt/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/opt/venv/lib/python3.7/site-packages/django/core/management/base.py", line 323, in run_from_argv
self.execute(*args, **cmd_options)
File "/opt/venv/lib/python3.7/site-packages/django/core/management/base.py", line 364, in execute
output = self.handle(*args, **options)
File "/taiga-back/taiga/base/management/commands/test_emails.py", line 52, in handle
membership.invited_by = get_user_model().objects.all().order_by("?").first()
AttributeError: 'NoneType' object has no attribute 'invited_by'
ERROR: 1
could anyone help me with it.
Hello, I am new to Taiga and just tried to implement the Taiga in my server.
When I tried to customisation. I tried a lot of still but still got
ERROR: The Compose file './docker-compose.yml' is invalid because:
Unsupported config option for services.taiga-front: 'PUBLIC_REGISTER_ENABLED' And my yml file as below
taiga-front:
PUBLIC_REGISTER_ENABLED: "True"
image: taigaio/taiga-front:latest
environment:
TAIGA_URL: "http://localhost:9000"
TAIGA_WEBSOCKETS_URL: "ws://localhost:9000"
TAIGA_SUBPATH: "" # "" or "/subpath"
networks:
- taiga
Any idea?
Many thanks!
The port is exposed when I check with ss
but the socket path isn't created. Is there any way to fix it? This is causing taiga-back
to exit with the following error:
Traceback (most recent call last):
File "manage.py", line 17, in <module>
execute_from_command_line(sys.argv)
File "/opt/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
utility.execute()
File "/opt/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/opt/venv/lib/python3.7/site-packages/django/core/management/base.py", line 323, in run_from_argv
self.execute(*args, **cmd_options)
File "/opt/venv/lib/python3.7/site-packages/django/core/management/base.py", line 364, in execute
output = self.handle(*args, **options)
File "/opt/venv/lib/python3.7/site-packages/django/core/management/base.py", line 83, in wrapped
res = handle_func(*args, **kwargs)
File "/opt/venv/lib/python3.7/site-packages/django/core/management/commands/migrate.py", line 87, in handle
executor = MigrationExecutor(connection, self.migration_progress_callback)
File "/opt/venv/lib/python3.7/site-packages/django/db/migrations/executor.py", line 18, in __init__
self.loader = MigrationLoader(self.connection)
File "/opt/venv/lib/python3.7/site-packages/django/db/migrations/loader.py", line 49, in __init__
self.build_graph()
File "/opt/venv/lib/python3.7/site-packages/django/db/migrations/loader.py", line 212, in build_graph
self.applied_migrations = recorder.applied_migrations()
File "/opt/venv/lib/python3.7/site-packages/django/db/migrations/recorder.py", line 73, in applied_migrations
if self.has_table():
File "/opt/venv/lib/python3.7/site-packages/django/db/migrations/recorder.py", line 56, in has_table
return self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor())
File "/opt/venv/lib/python3.7/site-packages/django/db/backends/base/base.py", line 256, in cursor
return self._cursor()
File "/opt/venv/lib/python3.7/site-packages/django/db/backends/base/base.py", line 233, in _cursor
self.ensure_connection()
File "/opt/venv/lib/python3.7/site-packages/django/db/backends/base/base.py", line 217, in ensure_connection
self.connect()
File "/opt/venv/lib/python3.7/site-packages/django/db/utils.py", line 89, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/opt/venv/lib/python3.7/site-packages/django/db/backends/base/base.py", line 217, in ensure_connection
self.connect()
File "/opt/venv/lib/python3.7/site-packages/django/db/backends/base/base.py", line 195, in connect
self.connection = self.get_new_connection(conn_params)
File "/opt/venv/lib/python3.7/site-packages/django/db/backends/postgresql/base.py", line 178, in get_new_connection
connection = Database.connect(**conn_params)
File "/opt/venv/lib/python3.7/site-packages/psycopg2/__init__.py", line 127, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
django.db.utils.OperationalError: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
Dockerhub has rate limits people often run into. It would be great if the taiga images were published on another registry. I happen to like quay.io, which is free for public Open Source projects.
Describe the bug
have configured the "django.core.mail.backends.smtp.EmailBackend"
and run sendtestemail
it report sendmail success, but not received email, and check the email account, found that have not call the smtp server/
+ exec docker-compose -f docker-compose.yml -f docker-compose-inits.yml run --rm taiga-manage sendtestemail -v 3 --traceback [email protected]
Creating taiga-6_taiga-manage_run ... done
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Test email from d5ae5d04ac2c on 2021-05-04 12:51:35.201950+00:00
From: [email protected]
To: [email protected]
Date: Tue, 04 May 2021 12:51:35 -0000
Message-ID: <162013269520.1.6033746653539765163@d5ae5d04ac2c>
If you're reading this, it was successful.
How can we reproduce the behavior
Workarounds
Screenshots
Taiga environment
taiga 6.0.2 in docker
Desktop (please complete the following information):
Additional context
Please describe the problem / need you are trying to solve.
As a docker noob I have trouble finding out how to do a minor update, for example 6.0 to 6.1.
Describe the feature or the improvement you'd like and what are you trying to achieve.
I would love to see an addition to the wiki that explains the docker container update process with copy & pastable code snippets.
Describe alternatives you've considered
I looked through the docs but only found documentation regarding big upgrades, for example Taiga 5 to Taiga 6.
But I have a good server is ARM64 architecture. So I want to use it to deploy the experience
Hi there,
after setting up the Docker, Taiga is now running. However, apparently, the media URL is None. If I e.g. try to change my profile picture, it is not shown and inspecting the page yields the URL https://none/media/user/a/7/e/a/7e3d550e5d01f081ddb9a0868bbf58ff5ec9dcb650326502810cfc3972af/profile_pic.png.80x80_q85_crop.jpg?token=<token>
. I tried setting the old MEDIA_URL variable in taiga-front
, but this didn't work.
Please find by docker-compose files attached.
Thanks in advance!
docker-compose.txt
docker-compose-inits.txt
Describe the bug
I don't know which versions of images used my docker-compose
docker image ls
taigaio/taiga-front latest dfa8f667da00 6 days ago 48MB
How can we reproduce the behavior
See https://github.com/kaleidos-ventures/taiga-docker/#taiga-docker
Workarounds
Change all latest
tags to specific version tags.
Thank you.
Hi there,
How would I be able to go about changing some of the resources, mostly png files for the application, if im using the Taiga-docker.
An example would be using a different Taiga logo in the app.
Thanks
Hi,
Taiga containers are crashing randomly. Logs from, for example, nginx:1.19-alpine (latest part, which looks weird):
...
34.96.130.15 - - [01/Oct/2021:14:15:01 +0000] "GET / HTTP/1.1" 200 140730 "-" "Expanse indexes the network perimeters of our customers. If you have any questions or concerns, please reach out to: [email protected]" "-"
2021/10/01 15:43:36 [warn] 31#31: 18462 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/4/52/0000002524 while reading upstream, client: 34.86.35.7, server: , request: "GET / HTTP/1.1", upstream: "http://172.18.0.4:80/", host: "admin.gdnet.ar"
34.86.35.7 - - [01/Oct/2021:15:43:36 +0000] "GET / HTTP/1.1" 200 140730 "-" "Expanse indexes the network perimeters of our customers. If you have any questions or concerns, please reach out to: [email protected]" "-"
146.0.74.162 - - [01/Oct/2021:17:44:26 +0000] "\x03\x00\x00/\xE0\x00\x00\x00\x00\x00Cookie: mstshash=Administr" 400 158 "-" "-" "-"
2021/10/01 17:50:38 [warn] 31#31: 18465 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/5/52/0000002525 while reading upstream, client: 104.206.128.14, server: , request: "GET / HTTP/1.1", upstream: "http://172.18.0.4:80/", host: "200.80.30.243:9000"
104.206.128.14 - - [01/Oct/2021:17:50:39 +0000] "GET / HTTP/1.1" 200 140730 "-" "https://gdnplus.com:Gather Analyze Provide." "-"
172.18.0.1 - - [01/Oct/2021:19:07:10 +0000] "GET / HTTP/1.1" 200 140730 "https://www.google.com" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.90 Safari/537.36" "192.99.18.122"
2021/10/01 19:13:10 [warn] 31#31: 18469 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/6/52/0000002526 while reading upstream, client: 34.86.35.19, server: , request: "GET / HTTP/1.1", upstream: "http://172.18.0.4:80/", host: "www.gdnet.ar"
34.86.35.19 - - [01/Oct/2021:19:13:10 +0000] "GET / HTTP/1.1" 200 140730 "-" "Expanse indexes the network perimeters of our customers. If you have any questions or concerns, please reach out to: [email protected]" "-"
167.94.138.59 - - [01/Oct/2021:20:24:33 +0000] "\x16\x03\x01\x00{\x01\x00\x00w\x03\x03d$\xFC\x05\xF2\x86\x02\x08\xA25hc)\x16\x0F'8\xEB\xE1 \xB8\x04\x8Df\x18\xA1\xACS\x92\x82v\x0E\x00\x00\x1A\xC0/\xC0+\xC0\x11\xC0\x07\xC0\x13\xC0\x09\xC0\x14\xC0" 400 158 "-" "-" "-"
167.94.138.59 - - [01/Oct/2021:20:24:33 +0000] "GET / HTTP/1.1" 200 109299 "-" "-" "-"
167.94.138.59 - - [01/Oct/2021:20:24:34 +0000] "GET / HTTP/1.1" 200 140730 "-" "Mozilla/5.0 (compatible; CensysInspect/1.1; +https://about.censys.io/)" "-"
45.146.164.110 - - [01/Oct/2021:21:35:14 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xC2\x06\x00\x0B\x09REMOTE_ADDR127.0.0.1\x0B\x09SERVER_ADDR127.0.0.1\x0F\x08SERVER_PROTOCOLHTTP/1.1\x0E\x02CONTENT_LENGTH52\x0E\x04REQUEST_METHODPOST" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:15 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xCC\x04\x00\x094PHP_VALUEauto_prepend_file = php://input" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:15 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xD4\x04\x00\x11\x0BGATEWAY_INTERFACEFastCGI/1.0\x0E\x04REQUEST_METHODPOST\x0B\x09SERVER_NAMElocalhost\x0F\x08SERVER_PROTOCOLHTTP/1.1\x0F\x16PHP_ADMIN_VALUEallow_url_include = On\x0B\x04REMOTE_PORT9985\x0B\x02SERVER_PORT80\x0E\x02CONTENT_LENGTH52\x094PHP_VALUEauto_prepend_file = php://input" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:16 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xE4\x04\x00\x11\x0BGATEWAY_INTERFACEFastCGI/1.0\x0F#SCRIPT_FILENAME/opt/bitnami/php/lib/php/System.php\x0B#SCRIPT_NAME/opt/bitnami/php/lib/php/System.php\x0B\x09SERVER_NAMElocalhost\x0E\x02CONTENT_LENGTH52\x0F\x16PHP_ADMIN_VALUEallow_url_include = On\x0E\x04REQUEST_METHODPOST" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:16 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xD8\x00\x00\x0E\x04REQUEST_METHODPOST\x0B\x1DSCRIPT_NAME/usr/local/lib/php/System.php\x0C\x00QUERY_STRING\x0B\x04REMOTE_PORT9985\x0B\x09SERVER_NAMElocalhost\x094PHP_VALUEauto_prepend_file = php://input" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:17 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:17 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xBA\x06\x00\x11\x0BGATEWAY_INTERFACEFastCGI/1.0\x0B\x0ESCRIPT_NAME/app/index.php" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:18 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:18 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xCE\x02\x00\x0B\x04REMOTE_PORT9985\x0B\x09SERVER_ADDR127.0.0.1\x0C\x10CONTENT_TYPEapplication/text\x0E\x02CONTENT_LENGTH52\x0E\x04REQUEST_METHODPOST\x0C\x00QUERY_STRING" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:25 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:25 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xCC\x04\x00\x0B\x09REMOTE_ADDR127.0.0.1\x0B\x04REMOTE_PORT9985\x0C\x10CONTENT_TYPEapplication/text\x0F\x16PHP_ADMIN_VALUEallow_url_include = On\x0E\x02CONTENT_LENGTH52\x094PHP_VALUEauto_prepend_file = php://input" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:26 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xD4\x04\x00\x0B\x02SERVER_PORT80\x0E\x02CONTENT_LENGTH52\x0B\x1BSCRIPT_NAME/usr/local/lib/php/PEAR.php\x0B\x09SERVER_ADDR127.0.0.1\x0E\x04REQUEST_METHODPOST\x0C\x10CONTENT_TYPEapplication/text\x0B\x04REMOTE_PORT9985\x0B\x09SERVER_NAMElocalhost\x094PHP_VALUEauto_prepend_file = php://input" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:26 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xE4\x04\x00\x0C\x10CONTENT_TYPEapplication/text\x0F\x16PHP_ADMIN_VALUEallow_url_include = On\x0E\x04REQUEST_METHODPOST\x0B\x04REMOTE_PORT9985\x0F\x08SERVER_PROTOCOLHTTP/1.1\x0B\x02SERVER_PORT80\x0B\x09SERVER_NAMElocalhost\x094PHP_VALUEauto_prepend_file = php://input" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:27 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xD8\x00\x00\x11\x0BGATEWAY_INTERFACEFastCGI/1.0\x0E\x04REQUEST_METHODPOST\x0B\x04REMOTE_PORT9985\x0F\x08SERVER_PROTOCOLHTTP/1.1\x0C\x10CONTENT_TYPEapplication/text\x0E\x02CONTENT_LENGTH52\x094PHP_VALUEauto_prepend_file = php://input" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:27 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xCC\x04\x00\x0B\x17SCRIPT_NAME/var/www/html/index.php\x0B\x09REMOTE_ADDR127.0.0.1\x0B\x09SERVER_ADDR127.0.0.1\x0B\x09SERVER_NAMElocalhost\x0C\x00QUERY_STRING\x0B\x04REMOTE_PORT9985\x0F\x08SERVER_PROTOCOLHTTP/1.1\x094PHP_VALUEauto_prepend_file = php://input" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:28 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xBA\x06\x00\x0E\x02CONTENT_LENGTH52\x11\x0BGATEWAY_INTERFACEFastCGI/1.0\x0F\x0ESCRIPT_FILENAME/app/index.php\x0B\x0ESCRIPT_NAME/app/index.php\x0B\x09REMOTE_ADDR127.0.0.1\x0E\x04REQUEST_METHODPOST\x0C\x00QUERY_STRING\x0F\x0ESERVER_SOFTWAREphp/fcgiclient\x0F\x16PHP_ADMIN_VALUEallow_url_include = On" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:29 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xC8\x00\x00\x0F\x15SCRIPT_FILENAME/app/public/index.php\x0C\x00QUERY_STRING\x0B\x09SERVER_ADDR127.0.0.1\x0B\x09SERVER_NAMElocalhost\x0E\x04REQUEST_METHODPOST\x0F\x08SERVER_PROTOCOLHTTP/1.1\x0C\x10CONTENT_TYPEapplication/text\x094PHP_VALUEauto_prepend_file = php://input" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:35:29 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xCE\x02\x00\x0E\x02CONTENT_LENGTH52\x11\x0BGATEWAY_INTERFACEFastCGI/1.0\x0F\x18SCRIPT_FILENAME/usr/local/bin/phar.phar\x0B\x04REMOTE_PORT9985\x0B\x09SERVER_ADDR127.0.0.1\x0E\x04REQUEST_METHODPOST\x0C\x10CONTENT_TYPEapplication/text\x0F\x16PHP_ADMIN_VALUEallow_url_include = On\x0F\x08SERVER_PROTOCOLHTTP/1.1\x094PHP_VALUEauto_prepend_file = php://input" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:36:30 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xC2\x06\x00\x0B\x04REMOTE_PORT9985\x094PHP_VALUEauto_prepend_file = php://input" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:36:31 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xCC\x04\x00\x0F\x17SCRIPT_FILENAME/usr/share/php/PEAR.php\x0B\x17SCRIPT_NAME/usr/share/php/PEAR.php\x0F\x0ESERVER_SOFTWAREphp/fcgiclient\x11\x0BGATEWAY_INTERFACEFastCGI/1.0\x0C\x00QUERY_STRING\x0B\x09SERVER_NAMElocalhost\x0F\x08SERVER_PROTOCOLHTTP/1.1\x0C\x10CONTENT_TYPEapplication/text\x094PHP_VALUEauto_prepend_file = php://input" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:36:31 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xD4\x04\x00\x0B\x09SERVER_ADDR127.0.0.1\x11\x0BGATEWAY_INTERFACEFastCGI/1.0\x0F\x1BSCRIPT_FILENAME/usr/local/lib/php/PEAR.php\x0B\x1BSCRIPT_NAME/usr/local/lib/php/PEAR.php\x0F\x0ESERVER_SOFTWAREphp/fcgiclient\x0F\x16PHP_ADMIN_VALUEallow_url_include = On\x0E\x04REQUEST_METHODPOST\x0B\x04REMOTE_PORT9985\x0F\x08SERVER_PROTOCOLHTTP/1.1\x0E\x02CONTENT_LENGTH52\x0C\x00QUERY_STRING\x0B\x09SERVER_NAMElocalhost\x0C\x10CONTENT_TYPEapplication/text" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:36:32 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xE4\x04\x00\x0E\x04REQUEST_METHODPOST\x0F#SCRIPT_FILENAME/opt/bitnami/php/lib/php/System.php\x094PHP_VALUEauto_prepend_file = php://input" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:36:33 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xD8\x00\x00" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:36:33 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:36:34 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xBA\x06\x00\x11\x0BGATEWAY_INTERFACEFastCGI/1.0\x0B\x09SERVER_ADDR127.0.0.1\x0B\x02SERVER_PORT80\x0F\x08SERVER_PROTOCOLHTTP/1.1\x0C\x10CONTENT_TYPEapplication/text\x0B\x04REMOTE_PORT9985\x0E\x02CONTENT_LENGTH52\x0E\x04REQUEST_METHODPOST\x0F\x0ESCRIPT_FILENAME/app/index.php" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:36:34 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xC8\x00\x00\x0E\x04REQUEST_METHODPOST\x0C\x10CONTENT_TYPEapplication/text\x094PHP_VALUEauto_prepend_file = php://input" 400 158 "-" "-" "-"
45.146.164.110 - - [01/Oct/2021:21:36:35 +0000] "\x01\x01\x00\x01\x00\x08\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x01\x04\x00\x01\x01\xCE\x02\x00\x094PHP_VALUEauto_prepend_file = php://input" 400 158 "-" "-" "-"
146.0.74.162 - - [01/Oct/2021:23:20:56 +0000] "\x03\x00\x00/\xE0\x00\x00\x00\x00\x00Cookie: mstshash=Administr" 400 158 "-" "-" "-"
146.0.74.162 - - [01/Oct/2021:23:40:48 +0000] "\x03\x00\x00/\xE0\x00\x00\x00\x00\x00Cookie: mstshash=Administr" 400 158 "-" "-" "-"
172.18.0.1 - - [02/Oct/2021:03:01:18 +0000] "GET /.well-known/acme-challenge/local-check-6157cb7eac5af3.60928825 HTTP/1.1" 200 140730 "-" "KeyHelp/21.2 (https://www.keyhelp.de/en) PHP/7.4.3 curl/7.68.0" "200.80.30.242"
93.174.95.106 - - [02/Oct/2021:03:13:13 +0000] "GET / HTTP/1.1" 200 140730 "-" "Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2228.0 Safari/537.36" "-"
93.174.95.106 - - [02/Oct/2021:03:13:14 +0000] "GET /v-1626363023890/images/favicon.png HTTP/1.1" 200 6979 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:80.0) Gecko/20100101 Firefox/80.0" "-"
93.174.95.106 - - [02/Oct/2021:03:13:18 +0000] "\x03K\xCEWa\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00" 400 158 "-" "-" "-"
2021/10/02 03:14:39 [warn] 31#31: *18513 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/7/52/0000002527 while reading upstream, client: 34.79.68.246, server: , request: "GET / HTTP/1.1", upstream: "http://172.18.0.4:80/", host: "200.80.30.242:9000"
34.79.68.246 - - [02/Oct/2021:03:14:39 +0000] "GET / HTTP/1.1" 200 140291 "-" "python-requests/2.26.0" "-"
2021/10/02 04:15:13 [warn] 31#31: *18515 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/8/52/0000002528 while reading upstream, client: 167.248.133.43, server: , request: "GET / HTTP/1.1", upstream: "http://172.18.0.4:80/", host: "200.80.30.244:9000"
167.248.133.43 - - [02/Oct/2021:04:15:13 +0000] "GET / HTTP/1.1" 200 140730 "-" "Mozilla/5.0 (compatible; CensysInspect/1.1; +https://about.censys.io/)" "-"
162.142.125.195 - - [02/Oct/2021:05:41:04 +0000] "\x16\x03\x01\x00{\x01\x00\x00w\x03\x03\xC9\x85\xC8\x9E\xC2\x93_z\xF3\x0F\x99\x81q\xD0~!\xA3\x95\xB5d93-7b\x03\x00\x8A\x07\xFFTd\x00\x00\x1A\xC0/\xC0+\xC0\x11\xC0\x07\xC0\x13\xC0\x09\xC0\x14\xC0" 400 158 "-" "-" "-"
162.142.125.195 - - [02/Oct/2021:05:41:05 +0000] "GET / HTTP/1.1" 200 109299 "-" "-" "-"
162.142.125.195 - - [02/Oct/2021:05:41:05 +0000] "GET / HTTP/1.1" 200 140730 "-" "Mozilla/5.0 (compatible; CensysInspect/1.1; +https://about.censys.io/)" "-"
If need you more data/conf/etc, let me know.
OS: Ubuntu 20.04
Thanks.
Describe the bug
https://github.com/kaleidos-ventures/taiga-docker/#gitlab-settings
As well as, section 1.5 under "Gitlab settings" https://docs.taiga.io/setup-production.html#setup-prod-with-docker
Explains how to configure Taiga to login via GitLab, but this feature when configured does not appear to work nor are the scopes one must configure in GitLab (https://{YOUR-GITLAB}/admin/applications
How can we reproduce the behavior
Configure as your documentation describes with a self hosted GitLab, such as https://github.com/sameersbn/docker-gitlab
Workarounds
N/A
Screenshots
N/A
Taiga environment
Self-hosted. Nothing in logs from tagia-front nor taiga-back.
Arch Linux latest Chrome browser
Additional context
N/A
Hello, I am having trouble getting slack notifications to work. First of all say that what I use is Rocket.chat, but I understand that it is 100% compatible. This is my scenario:
I know that Slack is integrated by default at the docker images according to the 30 minutes guide, but the problem persists.
This is all the configuration that i am using:
version: "3.5"
x-volumes:
&default-back-volumes
- taiga-static-data:/taiga-back/static
- ./data/taiga-media-data:/taiga-back/media
- ./settings/config.py:/taiga-back/settings/config.py
services:
taiga-back:
image: taigaio/taiga-back:latest
volumes: *default-back-volumes
environment:
ENABLE_SLACK: "True"
networks:
- taiga
depends_on:
- taiga-events-rabbitmq
- taiga-async-rabbitmq
ports:
- 8000:8000
taiga-async:
image: taigaio/taiga-back:latest
entrypoint: ["/taiga-back/docker/async_entrypoint.sh"]
volumes: *default-back-volumes
networks:
- taiga
depends_on:
- 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: rabbit_password
RABBITMQ_DEFAULT_VHOST: taiga
volumes:
- ./data/taiga-async-rabbitmq-data:/var/lib/rabbitmq
networks:
- taiga
taiga-events:
image: taigaio/taiga-events:latest
environment:
RABBITMQ_USER: taiga
RABBITMQ_PASS: rabbit_password
TAIGA_SECRET_KEY: "taiga_secret"
networks:
- taiga
depends_on:
- taiga-events-rabbitmq
ports:
- 8888:8888
taiga-events-rabbitmq:
image: rabbitmq:3-management-alpine
environment:
RABBITMQ_ERLANG_COOKIE: secret-erlang-cookie
RABBITMQ_DEFAULT_USER: taiga
RABBITMQ_DEFAULT_PASS: rabbit_password
RABBITMQ_DEFAULT_VHOST: taiga
volumes:
- ./data/taiga-events-rabbitmq-data:/var/lib/rabbitmq
networks:
- taiga
taiga-front:
image: taigaio/taiga-front
environment:
ENABLE_SLACK: "true"
networks:
- taiga
volumes:
- ./settings/conf.json:/usr/share/nginx/html/conf.json
ports:
- 8082:80
taiga-protected:
image: taigaio/taiga-protected:latest
volumes: #*default-back-volumes
- ./data/taiga-media-data:/taiga-protected/media
environment:
MAX_AGE: 360
SECRET_KEY: "taiga_secret"
networks:
- taiga
ports:
- 8003:8003
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
- ./data/taiga-media-data:/taiga/media
networks:
- taiga
depends_on:
- taiga-front
- taiga-back
- taiga-events
volumes:
taiga-static-data:
networks:
taiga:
- nginx vhost of taiga-gateway is exactly like this
- conf.json
{
"api": "https://projects.example.com/api/v1/",
"eventsUrl": null,
"eventsMaxMissedHeartbeats": 5,
"eventsHeartbeatIntervalTime": 60000,
"eventsReconnectTryInterval": 10000,
"debug": false,
"debugInfo": false,
"defaultLanguage": "es",
"themes": ["taiga"],
"defaultTheme": "taiga",
"defaultLoginEnabled": true,
"loginFormType": "ldap",
"publicRegisterEnabled": false,
"feedbackEnabled": false,
"supportUrl": "https://www.example.com",
"privacyPolicyUrl": null,
"termsOfServiceUrl": null,
"maxUploadFileSize": null,
"contribPlugins": [],
"tagManager": { "accountId": null },
"tribeHost": null,
"enableAsanaImporter": false,
"enableGithubImporter": false,
"enableJiraImporter": false,
"enableTrelloImporter": false,
"gravatar": false,
"rtlLanguages": ["ar", "fa", "he"]
}
# -*- coding: utf-8 -*-
import os
from .common import * # noqa, pylint: disable=unused-wildcard-import
#########################################
## GENERIC
#########################################
DEBUG = False
#ADMINS = (
# ("Admin", "[email protected]"),
#)
DATABASES = {
...my database config...
}
}
SECRET_KEY = "taiga_secret"
TAIGA_URL = "https://projects.example.com"
SITES = {
"api": {"domain": "projects.example.com", "scheme": "https", "name": "api"},
"front": {"domain": "projects.example.com", "scheme": "https", "name": "front"}
}
# Setting DEFAULT_PROJECT_SLUG_PREFIX to false
# removes the username from project slug
DEFAULT_PROJECT_SLUG_PREFIX = False
#########################################
## MEDIA AND STATIC
#########################################
MEDIA_ROOT = '/taiga-back/media'
MEDIA_URL = f"{ TAIGA_URL }/media/"
DEFAULT_FILE_STORAGE = "taiga_contrib_protected.storage.ProtectedFileSystemStorage"
THUMBNAIL_DEFAULT_STORAGE = DEFAULT_FILE_STORAGE
STATIC_ROOT = '/static'
STATIC_URL = f"{ TAIGA_URL }/static/"
#########################################
## EMAIL
#########################################
.. my email config...
#########################################
## EVENTS
#########################################
EVENTS_PUSH_BACKEND = "taiga.events.backends.rabbitmq.EventsPushBackend"
EVENTS_PUSH_BACKEND_OPTIONS = {
"url": "amqp://taiga:rabbit_password@taiga6_taiga-events-rabbitmq_1:5672/taiga"
}
#########################################
## TAIGA ASYNC
#########################################
CELERY_ENABLED = os.getenv('CELERY_ENABLED', 'True') == 'True'
from kombu import Queue # noqa
CELERY_BROKER_URL = "amqp://taiga:rabbit_password@taiga6_taiga-events-rabbitmq_1:5672/taiga"
CELERY_RESULT_BACKEND = None # for a general installation, we don't need to store the results
CELERY_ACCEPT_CONTENT = ['pickle', ] # Values are 'pickle', 'json', 'msgpack' and 'yaml'
CELERY_TASK_SERIALIZER = "pickle"
CELERY_RESULT_SERIALIZER = "pickle"
CELERY_TIMEZONE = 'Europe/Madrid'
CELERY_TASK_DEFAULT_QUEUE = 'tasks'
CELERY_QUEUES = (
Queue('tasks', routing_key='task.#'),
Queue('transient', routing_key='transient.#', delivery_mode=1)
)
CELERY_TASK_DEFAULT_EXCHANGE = 'tasks'
CELERY_TASK_DEFAULT_EXCHANGE_TYPE = 'topic'
CELERY_TASK_DEFAULT_ROUTING_KEY = 'task.default'
#########################################
## CONTRIBS
#########################################
INSTALLED_APPS += [
"taiga_contrib_ldap_auth_ext"
]
ALLOWED_HOSTS = ['*', ]
ENABLE_SLACK: "True"
#########################################
## LDAP CONFIG
#########################################
...... my ldap config....
ENABLE_TELEMETRY = False
PUBLIC_REGISTER_ENABLED = False
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://taiga-gateway:9000/;
}
I have also checked that the ENABLE_SLACK variable is defined in front and back. But when I enter into a project configuration I can't see the slack plugin:
I have also tried to install slack on my own with the slack_contrib_plugin with no results.
Please, could you help me?
> READ THIS FIRST!: We recently announced Taiga plans for the future and they greatly affect how we manage this repository and the current Taiga 6 release. Check it here.chore: readme announce taiga-next
PUBLIC_REGISTER_ENABLED: "True"
under X-environment: + on taiga-front doesn't to be working at all. If I commented it out Taiga will work. But when its not commented out I got a blank pages.Hi,
I want to know the full settings needed for Apache reverse proxy. So far I can't make it work:
Taiga (does not work, error page):
ProxyPreserveHost On
ProxyPass http://localhost:9000/
ProxyPassReverse http://localhost:9000/RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule ^/events/(.*) ws://localhost:9000/events/$1 [P,L]
Penpot (blank page):
ProxyPass http://localhost:9001/
ProxyPassReverse http://localhost:9001/
Nothing was changed in docker files, just default as it is.
Thanks in advance.
Hi, the FAQ mentions that USER_EMAIL_ALLOWED_DOMAINS can be used to restrict user register, but it doesn't seem that it can be set on docker environment.
If it is the case, could we migrate this to a feature request issue? If it works like other configs, would be a nice config to have no docker. Thanks!!
I've installed taiga on my server and not able to get past the discovery screen to log in. Checking dev tools I can see these errors appear in the communication layer.
500 (Internal Server Error)
WebSocket connection to 'wss://xx.xx.xx.xx:9000/events' failed:
I have opened port 9000 in shorewall although not certain if other ports are required.
> READ THIS FIRST!: We recently announced Taiga plans for the future and they greatly affect how we manage this repository and the current Taiga 6 release. Check it here.chore: readme announce taiga-next
I run docker installation to the dot and so far upon completion taiga did run but I can see nothing accept this screen
This error message shown during my first running ./taiga-manage.sh createsuperuser
You have 51 unapplied migration(s). Your project may not work properly until you apply the migrations for app(s): projects, references, sessions, settings, tasks, telemetry, timeline, token_denylist, users, userstorage, userstories, votes, webhooks, wiki.
Run 'python manage.py migrate' to apply them.
my step-by-step:
Pre Installation:
OS: Debian Bullseye
Docker: 20.10.12
Docker Compose: 1.29.2
NGINX Reverse Proxy installed
More help is needed. Thanks
Describe the bug
service taiga-events crashed, and reported
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli '/usr/local/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'run',
1 verbose cli 'start:production'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose config Skipping project config: /taiga-events/.npmrc. (matches userconfig)
5 verbose run-script [ 'prestart:production', 'start:production', 'poststart:production' ]
6 info lifecycle [email protected]~prestart:production: [email protected]
7 info lifecycle [email protected]~start:production: [email protected]
8 verbose lifecycle [email protected]~start:production: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~start:production: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/taiga-events/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
10 verbose lifecycle [email protected]~start:production: CWD: /taiga-events
11 silly lifecycle [email protected]~start:production: Args: [ '-c', 'NODE_ENV=production node ./src/index.js' ]
12 silly lifecycle [email protected]~start:production: Returned: code: 1 signal: null
13 info lifecycle [email protected]~start:production: Failed to exec start:production script
14 verbose stack Error: [email protected] start:production: `NODE_ENV=production node ./src/index.js`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
14 verbose stack at EventEmitter.emit (events.js:314:20)
14 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
14 verbose stack at ChildProcess.emit (events.js:314:20)
14 verbose stack at maybeClose (internal/child_process.js:1022:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
15 verbose pkgid [email protected]
16 verbose cwd /taiga-events
17 verbose Linux 4.4.0-130-generic
18 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "start:production"
19 verbose node v12.20.1
20 verbose npm v6.14.10
21 error code ELIFECYCLE
22 error errno 1
23 error [email protected] start:production: `NODE_ENV=production node ./src/index.js`
23 error Exit status 1
24 error Failed at the [email protected] start:production script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]
How can we reproduce the behavior
Workarounds
Screenshots
Taiga environment
taiga 6.0.4
Desktop (please complete the following information):
Additional context
In taiga-doc we should add the recommended way to backup & restore Taiga
Please tell me the correct way to fix invalid conf.json file.
After I cloned from git, this commands runs.
$ ./launch-taiga.sh
$ ./taiga-manage.sh createsuperuser
Because I wanted to view taiga, I visited to http://localhost:5900
. But it was displayed on the screen.
Something happened and the Taiga has captured the error to be able to work on it.
And in chrome dev tool console Your conf.json file is not a valid json file, please review it.
So I checked the conf.json by accesing http://localhost:5900/conf.json
.
My conf.json is below.
{
"api": "http://localhost:9000/api/v1/",
"eventsUrl": "ws://localhost:9000/events",
"eventsMaxMissedHeartbeats": 5,
"eventsHeartbeatIntervalTime": 60000,
"eventsReconnectTryInterval": 10000,
"debug": false,
"debugInfo": false,
"defaultLanguage": "en",
"themes": ["taiga"],
"defaultTheme": "taiga",
"defaultLoginEnabled": true,
"publicRegisterEnabled": ,
"feedbackEnabled": true,
"supportUrl": "https://resources.taiga.io",
"privacyPolicyUrl": null,
"termsOfServiceUrl": null,
"maxUploadFileSize": null,
"contribPlugins": [
"/plugins/slack/slack.json",
"/plugins/github-auth/github-auth.json",
"/plugins/gitlab-auth/gitlab-auth.json"
],
"gitHubClientId": "",
"gitLabClientId": "",
"gitLabUrl": "",
"tagManager": { "accountId": null },
"tribeHost": null,
"enableAsanaImporter": false,
"enableGithubImporter": ,
"enableJiraImporter": ,
"enableTrelloImporter": ,
"gravatar": false,
"rtlLanguages": ["fa"]
}
There were four parts where the structure is broken.
"publicRegisterEnabled": ,
So, I modified conf.json on the fly (by editing /usr/share/nginx/html/conf.json), but how should I modify it?
Hello,
I installed taigo following the tutorial, everything works except the admin account. I go to the /admin/
page,
I enter admin
and 123123
But it doesn't work, I don't see any errors (just : "Please fill in the "username" and "password" fields of an authorised account correctly. Please note that both fields may be case sensitive."
)
For information, I use portainer & Nginx proxy manager
i've read the "1.1. How can I change the domain name?" on the FAQ page.
it seems it's for the source installation. while for the docker installation, what conf should be updated?
thanks
Bug i install on my local success
If i install on cloud error
Something happened and the Taiga has captured the error to be able to work on it.
My local data is still taken to the cloud installation, even though I installed it fresh.
How can solved it?
Describe the bug
After an upgrade from taiga 5 to taiga 6 following guidelines documented here, the taiga-back and taiga-async does not start with following logs:
For taiga-async:
Give permission to taiga:taiga,
Starting Celery...,
error: failed switching to "taiga": operation not permitted,
For taiga-back:
Executing pending migrations,
Operations to perform:,
Apply all migrations: admin, attachments, auth, bitbucket, contact, contenttypes, custom_attributes, djmail, easy_thumbnails, epics, external_apps, feedback, github, gitlab, gogs, history, issues, likes, milestones, notifications, projects, references, sessions, settings, tasks, telemetry, timeline, users, userstorage, userstories, votes, webhooks, wiki,
Running migrations:,
No migrations to apply.,
Load default templates,
Installed 2 object(s) from 1 fixture(s),
Give permission to taiga:taiga,
Starting Taiga API...,
error: failed switching to "taiga": operation not permitted,
How can we reproduce the behavior
I use bind mounts for media, static and settings folders (attaching the modified docker-compose) and external postgres db, by simply issuing docker-compose up
, brings the errors.
version: "3.5"
networks:
default:
external:
name: webproxy
x-environment:
&default-back-environment
# Database settings
POSTGRES_DB: [-REDACTED-]
POSTGRES_USER: [-REDACTED-]
POSTGRES_PASSWORD: [-REDACTED-]
POSTGRES_HOST: [-REDACTED-]
# Taiga settings
TAIGA_SECRET_KEY: "[-REDACTED-]"
TAIGA_SITES_DOMAIN: "pm.bancolini.com"
TAIGA_SITES_SCHEME: "https"
# Email settings. Uncomment following lines and configure your SMTP server
EMAIL_BACKEND: 'django.core.mail.backends.smtp.EmailBackend'
DEFAULT_FROM_EMAIL: "[-REDACTED-]"
EMAIL_USE_TLS: "True"
EMAIL_HOST: 'smtp-relay.gmail.com'
EMAIL_PORT: 587
EMAIL_HOST_USER: ''
EMAIL_HOST_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: "True"
PUBLIC_REGISTER_ENABLED: "False"
x-volumes:
&default-back-volumes
- /home/docker/persistence/taiga6-data/static:/taiga-back/static
- /home/docker/persistence/taiga6-data/media:/taiga-back/media
- /home/docker/persistence/taiga6-data/settings:/taiga-back/settings
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:
build: .
environment: *default-back-environment
volumes: *default-back-volumes
depends_on:
- taiga-events-rabbitmq
- taiga-async-rabbitmq
taiga-async:
build: .
entrypoint: ["/taiga-back/docker/async_entrypoint.sh"]
environment: *default-back-environment
volumes: *default-back-volumes
depends_on:
- 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
volumes:
- /home/docker/persistence/taiga6-data/rabbitmq-async:/var/lib/rabbitmq
taiga-front:
image: taigaio/taiga-front:latest
environment:
TAIGA_URL: "https://pm.bancolini.com"
TAIGA_WEBSOCKETS_URL: "wss://pm.bancolini.com"
volumes:
- /home/docker/persistence/taiga6-data/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: "[-REDACTED-]"
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
volumes:
- /home/docker/persistence/taiga6-data/rabbitmq-events:/var/lib/rabbitmq
taiga-protected:
image: taigaio/taiga-protected:latest
environment:
MAX_AGE: 360
SECRET_KEY: "[-REDACTED-]"
taiga-gateway:
image: nginx:1.19-alpine
ports:
- "9000:80"
environment:
VIRTUAL_HOST: pm.bancolini.com
LETSENCRYPT_HOST: pm.bancolini.com
LETSENCRYPT_EMAIL: [email protected]
volumes:
- /home/docker/persistence/taiga6-data/nginx.conf:/etc/nginx/conf.d/default.conf
- /home/docker/persistence/taiga6-data/static:/taiga/static
- /home/docker/persistence/taiga6-data/media:/taiga/media
depends_on:
- taiga-front
- taiga-back
- taiga-events
Workarounds
No workarounds found: cannot use Taiga.
Taiga environment
Self hosted taiga with docker.
Traceback (most recent call last):
File "manage.py", line 17, in <module>
execute_from_command_line(sys.argv)
File "/opt/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
utility.execute()
File "/opt/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/opt/venv/lib/python3.7/site-packages/django/core/management/base.py", line 323, in run_from_argv
self.execute(*args, **cmd_options)
File "/opt/venv/lib/python3.7/site-packages/django/core/management/base.py", line 361, in execute
self.check()
File "/opt/venv/lib/python3.7/site-packages/django/core/management/base.py", line 390, in check
include_deployment_checks=include_deployment_checks,
File "/opt/venv/lib/python3.7/site-packages/django/core/management/commands/migrate.py", line 64, in _run_checks
issues = run_checks(tags=[Tags.database])
File "/opt/venv/lib/python3.7/site-packages/django/core/checks/registry.py", line 72, in run_checks
new_errors = check(app_configs=app_configs)
File "/opt/venv/lib/python3.7/site-packages/django/core/checks/database.py", line 9, in check_database_backends
for conn in connections.all():
File "/opt/venv/lib/python3.7/site-packages/django/db/utils.py", line 216, in all
return [self[alias] for alias in self]
File "/opt/venv/lib/python3.7/site-packages/django/db/utils.py", line 213, in __iter__
return iter(self.databases)
File "/opt/venv/lib/python3.7/site-packages/django/utils/functional.py", line 80, in __get__
res = instance.__dict__[self.name] = self.func(instance)
File "/opt/venv/lib/python3.7/site-packages/django/db/utils.py", line 147, in databases
self._databases = settings.DATABASES
File "/opt/venv/lib/python3.7/site-packages/django/conf/__init__.py", line 79, in __getattr__
self._setup(name)
File "/opt/venv/lib/python3.7/site-packages/django/conf/__init__.py", line 66, in _setup
self._wrapped = Settings(settings_module)
File "/opt/venv/lib/python3.7/site-packages/django/conf/__init__.py", line 176, in __init__
raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.
Describe the bug
It seems that when running ./launch-taiga.sh without any changes, rabbitmq and async fails after some time. re-running ./launch-taiga.sh doesn't seem to solve the issue.
How can we reproduce the behavior
Workarounds
Screenshots
Taiga environment
self-hosted Taiga
Desktop (please complete the following information):
Additional context
root@docker-s-1vcpu-1gb-ams3-01:~/taiga-docker# docker-compose logs
Attaching to taiga-docker_taiga-back_1, taiga-docker_taiga-events_1, taiga-docker_taiga-db_1, taiga-docker_taiga-protected_1, taiga-docker_taiga-front_1, taiga-docker_taiga-async-rabbitmq_1, taiga-docker_taiga-events-rabbitmq_1
taiga-db_1 |
taiga-db_1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
taiga-db_1 |
taiga-db_1 | 2021-05-24 09:38:43.887 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-db_1 | 2021-05-24 09:38:43.897 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
taiga-db_1 | 2021-05-24 09:38:43.897 UTC [1] LOG: listening on IPv6 address "::", port 5432
taiga-db_1 | 2021-05-24 09:38:43.903 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
taiga-db_1 | 2021-05-24 09:38:44.115 UTC [23] LOG: database system was shut down at 2021-05-24 09:34:57 UTC
taiga-db_1 | 2021-05-24 09:38:44.179 UTC [1] LOG: database system is ready to accept connections
taiga-back_1 | Executing pending migrations
taiga-front_1 | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
taiga-front_1 | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
taiga-front_1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
taiga-front_1 | 10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
taiga-protected_1 | Give permission to taiga:taiga
taiga-protected_1 | Starting Taiga Protected
root@docker-s-1vcpu-1gb-ams3-01:~/taiga-docker# docker-compose logs -f --tail="all"
Attaching to taiga-docker_taiga-gateway_1, taiga-docker_taiga-async_1, taiga-docker_taiga-back_1, taiga-docker_taiga-events_1, taiga-docker_taiga-db_1, taiga-docker_taiga-protected_1, taiga-docker_taiga-front_1, taiga-docker_taiga-async-rabbitmq_1, taiga-docker_taiga-events-rabbitmq_1
taiga-async_1 | Give permission to taiga:taiga
taiga-back_1 | Executing pending migrations
taiga-db_1 |
taiga-db_1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
taiga-db_1 |
taiga-db_1 | 2021-05-24 09:38:43.887 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-db_1 | 2021-05-24 09:38:43.897 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
taiga-db_1 | 2021-05-24 09:38:43.897 UTC [1] LOG: listening on IPv6 address "::", port 5432
taiga-db_1 | 2021-05-24 09:38:43.903 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
taiga-db_1 | 2021-05-24 09:38:44.115 UTC [23] LOG: database system was shut down at 2021-05-24 09:34:57 UTC
taiga-db_1 | 2021-05-24 09:38:44.179 UTC [1] LOG: database system is ready to accept connections
taiga-events_1 | Starting Taiga events
taiga-events_1 |
taiga-events_1 | > [email protected] start:production /taiga-events
taiga-events_1 | > NODE_ENV=production node ./src/index.js
taiga-events_1 |
taiga-front_1 | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
taiga-front_1 | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
taiga-front_1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
taiga-front_1 | 10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
taiga-front_1 | 10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf differs from the packaged version
taiga-front_1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
taiga-front_1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
taiga-front_1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/30_config_env_subst.sh
taiga-front_1 | /docker-entrypoint.sh: Configuration complete; ready for start up
taiga-gateway_1 | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
taiga-gateway_1 | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
taiga-gateway_1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
taiga-gateway_1 | 10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
taiga-gateway_1 | 10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf differs from the packaged version
taiga-gateway_1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
taiga-gateway_1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
taiga-gateway_1 | /docker-entrypoint.sh: Configuration complete; ready for start up
taiga-protected_1 | Give permission to taiga:taiga
taiga-protected_1 | Starting Taiga Protected
taiga-protected_1 | [2021-05-24 09:38:47 +0000] [1] [INFO] Starting gunicorn 19.9.0
taiga-protected_1 | [2021-05-24 09:38:47 +0000] [1] [INFO] Listening at: http://0.0.0.0:8003 (1)
taiga-protected_1 | [2021-05-24 09:38:47 +0000] [1] [INFO] Using worker: sync
taiga-protected_1 | [2021-05-24 09:38:47 +0000] [12] [INFO] Booting worker with pid: 12
taiga-protected_1 | [2021-05-24 09:38:47 +0000] [13] [INFO] Booting worker with pid: 13
taiga-protected_1 | [2021-05-24 09:38:47 +0000] [14] [INFO] Booting worker with pid: 14
taiga-protected_1 | [2021-05-24 09:38:47 +0000] [15] [INFO] Booting worker with pid: 15
taiga-events_1 | {"message":"WS server is started","level":"info","service":"taiga-events","timestamp":"2021-05-24 09:38:58"}
taiga-events_1 | {"message":"Liveness / Readiness server was started in http://localhost:3023/healthz","level":"info","service":"taiga-events","timestamp":"2021-05-24 09:38:58"}
taiga-async_1 | Starting Celery...
taiga-back_1 | Operations to perform:
taiga-back_1 | Apply all migrations: admin, attachments, auth, bitbucket, contact, contenttypes, custom_attributes, djmail, easy_thumbnails, epics, external_apps, feedback, github, gitlab, gogs, history, issues, likes, milestones, notifications, projects, references, sessions, settings, tasks, telemetry, timeline, users, userstorage, userstories, votes, webhooks, wiki
taiga-back_1 | Running migrations:
taiga-back_1 | No migrations to apply.
taiga-back_1 | Load default templates
taiga-events-rabbitmq_1 | Configuring logger redirection
taiga-async-rabbitmq_1 | Configuring logger redirection
taiga-async_1 |
taiga-async_1 | -------------- celery@4a70ca2d80b2 v4.3.0 (rhubarb)
taiga-async_1 | ---- **** -----
taiga-async_1 | --- * *** * -- Linux-5.4.0-52-generic-x86_64-with-debian-10.9 2021-05-24 09:39:35
taiga-async_1 | -- * - **** ---
taiga-async_1 | - ** ---------- [config]
taiga-async_1 | - ** ---------- .> app: taiga:0x7fa2cc5149d0
taiga-async_1 | - ** ---------- .> transport: amqp://taiga:**@taiga-async-rabbitmq:5672/taiga
taiga-async_1 | - ** ---------- .> results: disabled://
taiga-async_1 | - *** --- * --- .> concurrency: 4 (prefork)
taiga-async_1 | -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
taiga-async_1 | --- ***** -----
taiga-async_1 | -------------- [queues]
taiga-async_1 | .> tasks exchange=tasks(topic) key=task.default
taiga-async_1 |
taiga-async_1 |
taiga-async_1 | [tasks]
taiga-async_1 | . djmail.tasks.retry_send_messages
taiga-async_1 | . djmail.tasks.send_messages
taiga-async_1 | . taiga.export_import.tasks.delete_project_dump
taiga-async_1 | . taiga.export_import.tasks.dump_project
taiga-async_1 | . taiga.export_import.tasks.load_project_dump
taiga-async_1 | . taiga.projects.contact.services.send_contact_email
taiga-async_1 | . taiga.projects.notifications.tasks.send_bulk_email
taiga-async_1 | . taiga.projects.services.projects.delete_project
taiga-async_1 | . taiga.projects.services.projects.delete_projects
taiga-async_1 | . taiga.projects.userstories.services.update_open_or_close_conditions_if_status_has_been_changed
taiga-async_1 | . taiga.telemetry.tasks.send_telemetry
taiga-async_1 | . taiga.timeline.service.push_to_timelines
taiga-async_1 | . taiga.webhooks.tasks.change_webhook
taiga-async_1 | . taiga.webhooks.tasks.create_webhook
taiga-async_1 | . taiga.webhooks.tasks.delete_webhook
taiga-async_1 | . taiga.webhooks.tasks.resend_webhook
taiga-async_1 | . taiga.webhooks.tasks.test_webhook
taiga-async_1 |
taiga-back_1 | Installed 2 object(s) from 1 fixture(s)
taiga-back_1 | Give permission to taiga:taiga
taiga-async-rabbitmq_1 | 2021-05-24 09:39:39.614 [debug] <0.289.0> Lager installed handler error_logger_lager_h into error_logger
taiga-events-rabbitmq_1 | 2021-05-24 09:39:39.611 [debug] <0.289.0> Lager installed handler error_logger_lager_h into error_logger
taiga-async-rabbitmq_1 | 2021-05-24 09:39:39.899 [debug] <0.292.0> Lager installed handler lager_forwarder_backend into error_logger_lager_event
taiga-events-rabbitmq_1 | 2021-05-24 09:39:39.899 [debug] <0.292.0> Lager installed handler lager_forwarder_backend into error_logger_lager_event
taiga-events-rabbitmq_1 | 2021-05-24 09:39:39.900 [debug] <0.295.0> Lager installed handler lager_forwarder_backend into rabbit_log_lager_event
taiga-async-rabbitmq_1 | 2021-05-24 09:39:39.899 [debug] <0.295.0> Lager installed handler lager_forwarder_backend into rabbit_log_lager_event
taiga-async-rabbitmq_1 | 2021-05-24 09:39:39.900 [debug] <0.298.0> Lager installed handler lager_forwarder_backend into rabbit_log_channel_lager_event
taiga-events-rabbitmq_1 | 2021-05-24 09:39:39.900 [debug] <0.298.0> Lager installed handler lager_forwarder_backend into rabbit_log_channel_lager_event
taiga-events-rabbitmq_1 | 2021-05-24 09:39:39.900 [debug] <0.301.0> Lager installed handler lager_forwarder_backend into rabbit_log_connection_lager_event
taiga-async-rabbitmq_1 | 2021-05-24 09:39:39.900 [debug] <0.301.0> Lager installed handler lager_forwarder_backend into rabbit_log_connection_lager_event
taiga-async-rabbitmq_1 | 2021-05-24 09:39:39.900 [debug] <0.304.0> Lager installed handler lager_forwarder_backend into rabbit_log_feature_flags_lager_event
taiga-events-rabbitmq_1 | 2021-05-24 09:39:39.900 [debug] <0.304.0> Lager installed handler lager_forwarder_backend into rabbit_log_feature_flags_lager_event
taiga-async-rabbitmq_1 | 2021-05-24 09:39:39.900 [debug] <0.307.0> Lager installed handler lager_forwarder_backend into rabbit_log_federation_lager_event
taiga-events-rabbitmq_1 | 2021-05-24 09:39:39.900 [debug] <0.307.0> Lager installed handler lager_forwarder_backend into rabbit_log_federation_lager_event
taiga-async-rabbitmq_1 | 2021-05-24 09:39:39.971 [debug] <0.310.0> Lager installed handler lager_forwarder_backend into rabbit_log_ldap_lager_event
taiga-events-rabbitmq_1 | 2021-05-24 09:39:39.973 [debug] <0.310.0> Lager installed handler lager_forwarder_backend into rabbit_log_ldap_lager_event
taiga-async-rabbitmq_1 | 2021-05-24 09:39:40.004 [debug] <0.313.0> Lager installed handler lager_forwarder_backend into rabbit_log_mirroring_lager_event
taiga-events-rabbitmq_1 | 2021-05-24 09:39:40.008 [debug] <0.313.0> Lager installed handler lager_forwarder_backend into rabbit_log_mirroring_lager_event
taiga-async-rabbitmq_1 | 2021-05-24 09:39:40.061 [debug] <0.316.0> Lager installed handler lager_forwarder_backend into rabbit_log_prelaunch_lager_event
taiga-events-rabbitmq_1 | 2021-05-24 09:39:40.062 [debug] <0.316.0> Lager installed handler lager_forwarder_backend into rabbit_log_prelaunch_lager_event
taiga-async-rabbitmq_1 | 2021-05-24 09:39:40.088 [debug] <0.285.0> Lager installed handler lager_backend_throttle into lager_event
taiga-events-rabbitmq_1 | 2021-05-24 09:39:40.087 [debug] <0.285.0> Lager installed handler lager_backend_throttle into lager_event
taiga-async-rabbitmq_1 | 2021-05-24 09:39:40.131 [debug] <0.319.0> Lager installed handler lager_forwarder_backend into rabbit_log_queue_lager_event
taiga-events-rabbitmq_1 | 2021-05-24 09:39:40.131 [debug] <0.319.0> Lager installed handler lager_forwarder_backend into rabbit_log_queue_lager_event
taiga-async-rabbitmq_1 | 2021-05-24 09:39:40.180 [debug] <0.322.0> Lager installed handler lager_forwarder_backend into rabbit_log_ra_lager_event
taiga-events-rabbitmq_1 | 2021-05-24 09:39:40.181 [debug] <0.322.0> Lager installed handler lager_forwarder_backend into rabbit_log_ra_lager_event
taiga-async-rabbitmq_1 | 2021-05-24 09:39:40.235 [debug] <0.325.0> Lager installed handler lager_forwarder_backend into rabbit_log_shovel_lager_event
taiga-events-rabbitmq_1 | 2021-05-24 09:39:40.236 [debug] <0.325.0> Lager installed handler lager_forwarder_backend into rabbit_log_shovel_lager_event
taiga-events-rabbitmq_1 | 2021-05-24 09:39:40.303 [debug] <0.328.0> Lager installed handler lager_forwarder_backend into rabbit_log_upgrade_lager_event
taiga-async-rabbitmq_1 | 2021-05-24 09:39:40.303 [debug] <0.328.0> Lager installed handler lager_forwarder_backend into rabbit_log_upgrade_lager_event
taiga-async-rabbitmq_1 | 2021-05-24 09:39:40.748 [info] <0.44.0> Application lager started on node rabbit@21543dd5f6f8
taiga-events-rabbitmq_1 | 2021-05-24 09:39:40.749 [info] <0.44.0> Application lager started on node rabbit@db02ef3ad502
taiga-async_1 | [2021-05-24 09:39:40,844: ERROR/MainProcess] consumer: Cannot connect to amqp://taiga:**@taiga-async-rabbitmq:5672/taiga: [Errno 111] Connection refused.
taiga-async_1 | Trying again in 2.00 seconds...
taiga-async_1 |
taiga-async-rabbitmq_1 | 2021-05-24 09:39:42.358 [info] <0.44.0> Application mnesia started on node rabbit@21543dd5f6f8
taiga-events-rabbitmq_1 | 2021-05-24 09:39:42.358 [info] <0.44.0> Application mnesia started on node rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | 2021-05-24 09:39:42.370 [info] <0.273.0>
taiga-events-rabbitmq_1 | Starting RabbitMQ 3.8.16 on Erlang 23.3.4.1
taiga-events-rabbitmq_1 | Copyright (c) 2007-2021 VMware, Inc. or its affiliates.
taiga-events-rabbitmq_1 | Licensed under the MPL 2.0. Website: https://rabbitmq.com
taiga-async-rabbitmq_1 | 2021-05-24 09:39:42.370 [info] <0.273.0>
taiga-async-rabbitmq_1 | Starting RabbitMQ 3.8.16 on Erlang 23.3.4.1
taiga-async-rabbitmq_1 | Copyright (c) 2007-2021 VMware, Inc. or its affiliates.
taiga-async-rabbitmq_1 | Licensed under the MPL 2.0. Website: https://rabbitmq.com
taiga-events-rabbitmq_1 |
taiga-events-rabbitmq_1 | ## ## RabbitMQ 3.8.16
taiga-events-rabbitmq_1 | ## ##
taiga-events-rabbitmq_1 | ########## Copyright (c) 2007-2021 VMware, Inc. or its affiliates.
taiga-events-rabbitmq_1 | ###### ##
taiga-events-rabbitmq_1 | ########## Licensed under the MPL 2.0. Website: https://rabbitmq.com
taiga-events-rabbitmq_1 |
taiga-events-rabbitmq_1 | Doc guides: https://rabbitmq.com/documentation.html
taiga-events-rabbitmq_1 | Support: https://rabbitmq.com/contact.html
taiga-events-rabbitmq_1 | Tutorials: https://rabbitmq.com/getstarted.html
taiga-events-rabbitmq_1 | Monitoring: https://rabbitmq.com/monitoring.html
taiga-events-rabbitmq_1 |
taiga-events-rabbitmq_1 | Logs: <stdout>
taiga-events-rabbitmq_1 |
taiga-events-rabbitmq_1 | Config file(s): /etc/rabbitmq/rabbitmq.conf
taiga-events-rabbitmq_1 |
taiga-async-rabbitmq_1 |
taiga-async-rabbitmq_1 | ## ## RabbitMQ 3.8.16
taiga-async-rabbitmq_1 | ## ##
taiga-async-rabbitmq_1 | ########## Copyright (c) 2007-2021 VMware, Inc. or its affiliates.
taiga-async-rabbitmq_1 | ###### ##
taiga-async-rabbitmq_1 | ########## Licensed under the MPL 2.0. Website: https://rabbitmq.com
taiga-async-rabbitmq_1 |
taiga-async-rabbitmq_1 | Doc guides: https://rabbitmq.com/documentation.html
taiga-async-rabbitmq_1 | Support: https://rabbitmq.com/contact.html
taiga-async-rabbitmq_1 | Tutorials: https://rabbitmq.com/getstarted.html
taiga-async-rabbitmq_1 | Monitoring: https://rabbitmq.com/monitoring.html
taiga-async-rabbitmq_1 |
taiga-async-rabbitmq_1 | Logs: <stdout>
taiga-async-rabbitmq_1 |
taiga-async-rabbitmq_1 | Config file(s): /etc/rabbitmq/rabbitmq.conf
taiga-async-rabbitmq_1 |
taiga-events-rabbitmq_1 | Starting broker...2021-05-24 09:39:42.390 [info] <0.273.0>
taiga-events-rabbitmq_1 | node : rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | home dir : /var/lib/rabbitmq
taiga-events-rabbitmq_1 | config file(s) : /etc/rabbitmq/rabbitmq.conf
taiga-events-rabbitmq_1 | cookie hash : JDwKdQ1+Opz6fGGTXnORXQ==
taiga-events-rabbitmq_1 | log(s) : <stdout>
taiga-events-rabbitmq_1 | database dir : /var/lib/rabbitmq/mnesia/rabbit@db02ef3ad502
taiga-async-rabbitmq_1 | Starting broker...2021-05-24 09:39:42.391 [info] <0.273.0>
taiga-async-rabbitmq_1 | node : rabbit@21543dd5f6f8
taiga-async-rabbitmq_1 | home dir : /var/lib/rabbitmq
taiga-async-rabbitmq_1 | config file(s) : /etc/rabbitmq/rabbitmq.conf
taiga-async-rabbitmq_1 | cookie hash : JDwKdQ1+Opz6fGGTXnORXQ==
taiga-async-rabbitmq_1 | log(s) : <stdout>
taiga-async-rabbitmq_1 | database dir : /var/lib/rabbitmq/mnesia/rabbit@21543dd5f6f8
taiga-async_1 | [2021-05-24 09:39:42,991: ERROR/MainProcess] consumer: Cannot connect to amqp://taiga:**@taiga-async-rabbitmq:5672/taiga: [Errno 111] Connection refused.
taiga-async_1 | Trying again in 4.00 seconds...
taiga-async_1 |
taiga-async_1 | [2021-05-24 09:39:47,096: ERROR/MainProcess] consumer: Cannot connect to amqp://taiga:**@taiga-async-rabbitmq:5672/taiga: [Errno 111] Connection refused.
taiga-async_1 | Trying again in 6.00 seconds...
taiga-async_1 |
taiga-events-rabbitmq_1 | 2021-05-24 09:39:47.703 [info] <0.273.0> Feature flags: list of feature flags found:
taiga-async-rabbitmq_1 | 2021-05-24 09:39:47.704 [info] <0.273.0> Feature flags: list of feature flags found:
taiga-events-rabbitmq_1 | 2021-05-24 09:39:47.705 [info] <0.273.0> Feature flags: [ ] drop_unroutable_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:39:47.709 [info] <0.273.0> Feature flags: [ ] empty_basic_get_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:39:47.711 [info] <0.273.0> Feature flags: [ ] implicit_default_bindings
taiga-async-rabbitmq_1 | 2021-05-24 09:39:47.706 [info] <0.273.0> Feature flags: [ ] drop_unroutable_metric
taiga-async-rabbitmq_1 | 2021-05-24 09:39:47.712 [info] <0.273.0> Feature flags: [ ] empty_basic_get_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:39:47.712 [info] <0.273.0> Feature flags: [ ] maintenance_mode_status
taiga-async-rabbitmq_1 | 2021-05-24 09:39:47.714 [info] <0.273.0> Feature flags: [ ] implicit_default_bindings
taiga-events-rabbitmq_1 | 2021-05-24 09:39:47.715 [info] <0.273.0> Feature flags: [ ] quorum_queue
taiga-async-rabbitmq_1 | 2021-05-24 09:39:47.716 [info] <0.273.0> Feature flags: [ ] maintenance_mode_status
taiga-events-rabbitmq_1 | 2021-05-24 09:39:47.717 [info] <0.273.0> Feature flags: [ ] user_limits
taiga-async-rabbitmq_1 | 2021-05-24 09:39:47.718 [info] <0.273.0> Feature flags: [ ] quorum_queue
taiga-async-rabbitmq_1 | 2021-05-24 09:39:47.720 [info] <0.273.0> Feature flags: [ ] user_limits
taiga-events-rabbitmq_1 | 2021-05-24 09:39:47.719 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata
taiga-events-rabbitmq_1 | 2021-05-24 09:39:47.721 [info] <0.273.0> Feature flags: feature flag states written to disk: yes
taiga-async-rabbitmq_1 | 2021-05-24 09:39:47.722 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata
taiga-async-rabbitmq_1 | 2021-05-24 09:39:47.724 [info] <0.273.0> Feature flags: feature flag states written to disk: yes
taiga-async_1 | [2021-05-24 09:39:52,513: INFO/Beat] beat: Starting...
taiga-async_1 | [2021-05-24 09:39:53,152: ERROR/MainProcess] consumer: Cannot connect to amqp://taiga:**@taiga-async-rabbitmq:5672/taiga: [Errno 111] Connection refused.
taiga-async_1 | Trying again in 8.00 seconds...
taiga-async_1 |
taiga-back_1 | Starting Taiga API...
taiga-async_1 | [2021-05-24 09:40:01,209: ERROR/MainProcess] consumer: Cannot connect to amqp://taiga:**@taiga-async-rabbitmq:5672/taiga: [Errno 111] Connection refused.
taiga-async_1 | Trying again in 10.00 seconds...
taiga-async_1 |
taiga-back_1 | [2021-05-24 09:40:09 +0000] [1] [INFO] Starting gunicorn 19.9.0
taiga-back_1 | [2021-05-24 09:40:09 +0000] [1] [INFO] Listening at: http://0.0.0.0:8000 (1)
taiga-back_1 | [2021-05-24 09:40:09 +0000] [1] [INFO] Using worker: sync
taiga-back_1 | [2021-05-24 09:40:09 +0000] [26] [INFO] Booting worker with pid: 26
taiga-back_1 | [2021-05-24 09:40:10 +0000] [27] [INFO] Booting worker with pid: 27
taiga-back_1 | [2021-05-24 09:40:10 +0000] [28] [INFO] Booting worker with pid: 28
taiga-async_1 | [2021-05-24 09:40:12,410: ERROR/MainProcess] consumer: Cannot connect to amqp://taiga:**@taiga-async-rabbitmq:5672/taiga: [Errno 111] Connection refused.
taiga-async_1 | Trying again in 12.00 seconds...
taiga-async_1 |
taiga-async-rabbitmq_1 | Killed
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.132 [info] <0.273.0> Running boot step pre_boot defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.132 [info] <0.273.0> Running boot step rabbit_core_metrics defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.137 [info] <0.273.0> Running boot step rabbit_alarm defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.197 [info] <0.364.0> Memory high watermark set to 392 MiB (411603763 bytes) of 981 MiB (1029009408 bytes) total
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.217 [info] <0.366.0> Enabling free disk space monitoring
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.218 [info] <0.366.0> Disk free limit set to 50MB
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.242 [info] <0.273.0> Running boot step code_server_cache defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.242 [info] <0.273.0> Running boot step file_handle_cache defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.252 [info] <0.369.0> Limiting to approx 1048479 file handles (943629 sockets)
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.252 [info] <0.370.0> FHC read buffering: OFF
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.253 [info] <0.370.0> FHC write buffering: ON
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.259 [info] <0.273.0> Running boot step worker_pool defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.261 [info] <0.348.0> Will use 1 processes for default worker pool
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.262 [info] <0.348.0> Starting worker pool 'worker_pool' with 1 processes in it
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.266 [info] <0.273.0> Running boot step database defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.271 [info] <0.273.0> Node database directory at /var/lib/rabbitmq/mnesia/rabbit@db02ef3ad502 is empty. Assuming we need to join an existing cluster or initialise from scratch...
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.271 [info] <0.273.0> Configured peer discovery backend: rabbit_peer_discovery_classic_config
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.274 [info] <0.273.0> Will try to lock with peer discovery backend rabbit_peer_discovery_classic_config
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.276 [info] <0.273.0> Peer discovery backend does not support locking, falling back to randomized delay
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.277 [info] <0.273.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping randomized startup delay.
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.277 [info] <0.273.0> All discovered existing cluster peers:
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.279 [info] <0.273.0> Discovered no peer nodes to cluster with. Some discovery backends can filter nodes out based on a readiness criteria. Enabling debug logging might help troubleshoot.
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.300 [info] <0.44.0> Application mnesia exited with reason: stopped
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.300 [info] <0.44.0> Application mnesia exited with reason: stopped
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.396 [info] <0.44.0> Application mnesia started on node rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.688 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.689 [info] <0.273.0> Successfully synced tables from a peer
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.849 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.849 [info] <0.273.0> Successfully synced tables from a peer
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.851 [info] <0.273.0> Feature flag `drop_unroutable_metric`: supported, attempt to enable...
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.851 [info] <0.273.0> Feature flag `drop_unroutable_metric`: mark as enabled=state_changing
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.893 [info] <0.273.0> Feature flags: list of feature flags found:
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.901 [info] <0.273.0> Feature flags: [~] drop_unroutable_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.901 [info] <0.273.0> Feature flags: [ ] empty_basic_get_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.901 [info] <0.273.0> Feature flags: [ ] implicit_default_bindings
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.901 [info] <0.273.0> Feature flags: [ ] maintenance_mode_status
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.901 [info] <0.273.0> Feature flags: [ ] quorum_queue
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.902 [info] <0.273.0> Feature flags: [ ] user_limits
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.902 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata
taiga-events-rabbitmq_1 | 2021-05-24 09:40:20.902 [info] <0.273.0> Feature flags: feature flag states written to disk: yes
taiga-docker_taiga-async-rabbitmq_1 exited with code 0
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.000 [info] <0.273.0> Feature flag `drop_unroutable_metric`: mark as enabled=true
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.085 [info] <0.273.0> Feature flags: list of feature flags found:
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.096 [info] <0.273.0> Feature flags: [x] drop_unroutable_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.096 [info] <0.273.0> Feature flags: [ ] empty_basic_get_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.097 [info] <0.273.0> Feature flags: [ ] implicit_default_bindings
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.097 [info] <0.273.0> Feature flags: [ ] maintenance_mode_status
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.097 [info] <0.273.0> Feature flags: [ ] quorum_queue
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.097 [info] <0.273.0> Feature flags: [ ] user_limits
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.097 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.097 [info] <0.273.0> Feature flags: feature flag states written to disk: yes
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.182 [info] <0.273.0> Feature flag `empty_basic_get_metric`: supported, attempt to enable...
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.198 [info] <0.273.0> Feature flag `empty_basic_get_metric`: mark as enabled=state_changing
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.247 [info] <0.273.0> Feature flags: list of feature flags found:
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.248 [info] <0.273.0> Feature flags: [x] drop_unroutable_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.248 [info] <0.273.0> Feature flags: [~] empty_basic_get_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.248 [info] <0.273.0> Feature flags: [ ] implicit_default_bindings
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.248 [info] <0.273.0> Feature flags: [ ] maintenance_mode_status
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.248 [info] <0.273.0> Feature flags: [ ] quorum_queue
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.248 [info] <0.273.0> Feature flags: [ ] user_limits
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.248 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.248 [info] <0.273.0> Feature flags: feature flag states written to disk: yes
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.328 [info] <0.273.0> Feature flag `empty_basic_get_metric`: mark as enabled=true
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.402 [info] <0.273.0> Feature flags: list of feature flags found:
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.406 [info] <0.273.0> Feature flags: [x] drop_unroutable_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.407 [info] <0.273.0> Feature flags: [x] empty_basic_get_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.407 [info] <0.273.0> Feature flags: [ ] implicit_default_bindings
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.407 [info] <0.273.0> Feature flags: [ ] maintenance_mode_status
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.407 [info] <0.273.0> Feature flags: [ ] quorum_queue
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.408 [info] <0.273.0> Feature flags: [ ] user_limits
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.408 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.415 [info] <0.273.0> Feature flags: feature flag states written to disk: yes
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.486 [info] <0.273.0> Feature flag `implicit_default_bindings`: supported, attempt to enable...
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.510 [info] <0.273.0> Feature flag `implicit_default_bindings`: mark as enabled=state_changing
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.541 [info] <0.273.0> Feature flags: list of feature flags found:
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.541 [info] <0.273.0> Feature flags: [x] drop_unroutable_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.545 [info] <0.273.0> Feature flags: [x] empty_basic_get_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.547 [info] <0.273.0> Feature flags: [~] implicit_default_bindings
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.549 [info] <0.273.0> Feature flags: [ ] maintenance_mode_status
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.549 [info] <0.273.0> Feature flags: [ ] quorum_queue
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.551 [info] <0.273.0> Feature flags: [ ] user_limits
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.552 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.553 [info] <0.273.0> Feature flags: feature flag states written to disk: yes
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.592 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 0 retries left
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.598 [info] <0.273.0> Successfully synced tables from a peer
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.598 [info] <0.273.0> Feature flag `implicit_default_bindings`: mark as enabled=true
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.627 [info] <0.273.0> Feature flags: list of feature flags found:
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.630 [info] <0.273.0> Feature flags: [x] drop_unroutable_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.631 [info] <0.273.0> Feature flags: [x] empty_basic_get_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.632 [info] <0.273.0> Feature flags: [x] implicit_default_bindings
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.633 [info] <0.273.0> Feature flags: [ ] maintenance_mode_status
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.633 [info] <0.273.0> Feature flags: [ ] quorum_queue
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.634 [info] <0.273.0> Feature flags: [ ] user_limits
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.635 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.636 [info] <0.273.0> Feature flags: feature flag states written to disk: yes
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.671 [info] <0.273.0> Feature flag `maintenance_mode_status`: supported, attempt to enable...
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.679 [info] <0.273.0> Feature flag `maintenance_mode_status`: mark as enabled=state_changing
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.710 [info] <0.273.0> Feature flags: list of feature flags found:
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.710 [info] <0.273.0> Feature flags: [x] drop_unroutable_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.713 [info] <0.273.0> Feature flags: [x] empty_basic_get_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.714 [info] <0.273.0> Feature flags: [x] implicit_default_bindings
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.718 [info] <0.273.0> Feature flags: [~] maintenance_mode_status
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.721 [info] <0.273.0> Feature flags: [ ] quorum_queue
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.722 [info] <0.273.0> Feature flags: [ ] user_limits
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.722 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.722 [info] <0.273.0> Feature flags: feature flag states written to disk: yes
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.765 [info] <0.273.0> Creating table rabbit_node_maintenance_states for feature flag `maintenance_mode_status`
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.785 [info] <0.273.0> Feature flag `maintenance_mode_status`: mark as enabled=true
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.810 [info] <0.273.0> Feature flags: list of feature flags found:
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.810 [info] <0.273.0> Feature flags: [x] drop_unroutable_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.811 [info] <0.273.0> Feature flags: [x] empty_basic_get_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.815 [info] <0.273.0> Feature flags: [x] implicit_default_bindings
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.817 [info] <0.273.0> Feature flags: [x] maintenance_mode_status
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.818 [info] <0.273.0> Feature flags: [ ] quorum_queue
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.820 [info] <0.273.0> Feature flags: [ ] user_limits
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.821 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.822 [info] <0.273.0> Feature flags: feature flag states written to disk: yes
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.872 [info] <0.273.0> Feature flag `quorum_queue`: supported, attempt to enable...
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.881 [info] <0.273.0> Feature flag `quorum_queue`: mark as enabled=state_changing
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.906 [info] <0.273.0> Feature flags: list of feature flags found:
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.906 [info] <0.273.0> Feature flags: [x] drop_unroutable_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.913 [info] <0.273.0> Feature flags: [x] empty_basic_get_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.914 [info] <0.273.0> Feature flags: [x] implicit_default_bindings
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.916 [info] <0.273.0> Feature flags: [x] maintenance_mode_status
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.917 [info] <0.273.0> Feature flags: [~] quorum_queue
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.919 [info] <0.273.0> Feature flags: [ ] user_limits
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.920 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.921 [info] <0.273.0> Feature flags: feature flag states written to disk: yes
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.963 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.973 [info] <0.273.0> Successfully synced tables from a peer
taiga-events-rabbitmq_1 | 2021-05-24 09:40:21.973 [info] <0.273.0> Feature flag `quorum_queue`: migrating Mnesia table rabbit_queue...
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.002 [info] <0.273.0> Feature flag `quorum_queue`: migrating Mnesia table rabbit_durable_queue...
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.022 [info] <0.273.0> Feature flag `quorum_queue`: Mnesia tables migration done
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.022 [info] <0.273.0> Feature flag `quorum_queue`: mark as enabled=true
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.051 [info] <0.273.0> Feature flags: list of feature flags found:
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.051 [info] <0.273.0> Feature flags: [x] drop_unroutable_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.052 [info] <0.273.0> Feature flags: [x] empty_basic_get_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.053 [info] <0.273.0> Feature flags: [x] implicit_default_bindings
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.054 [info] <0.273.0> Feature flags: [x] maintenance_mode_status
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.055 [info] <0.273.0> Feature flags: [x] quorum_queue
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.055 [info] <0.273.0> Feature flags: [ ] user_limits
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.056 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.057 [info] <0.273.0> Feature flags: feature flag states written to disk: yes
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.094 [info] <0.273.0> Feature flag `user_limits`: supported, attempt to enable...
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.101 [info] <0.273.0> Feature flag `user_limits`: mark as enabled=state_changing
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.121 [info] <0.273.0> Feature flags: list of feature flags found:
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.121 [info] <0.273.0> Feature flags: [x] drop_unroutable_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.127 [info] <0.273.0> Feature flags: [x] empty_basic_get_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.128 [info] <0.273.0> Feature flags: [x] implicit_default_bindings
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.129 [info] <0.273.0> Feature flags: [x] maintenance_mode_status
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.130 [info] <0.273.0> Feature flags: [x] quorum_queue
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.131 [info] <0.273.0> Feature flags: [~] user_limits
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.132 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.133 [info] <0.273.0> Feature flags: feature flag states written to disk: yes
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.168 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.174 [info] <0.273.0> Successfully synced tables from a peer
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.203 [info] <0.273.0> Feature flag `user_limits`: mark as enabled=true
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.229 [info] <0.273.0> Feature flags: list of feature flags found:
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.229 [info] <0.273.0> Feature flags: [x] drop_unroutable_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.230 [info] <0.273.0> Feature flags: [x] empty_basic_get_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.231 [info] <0.273.0> Feature flags: [x] implicit_default_bindings
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.235 [info] <0.273.0> Feature flags: [x] maintenance_mode_status
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.237 [info] <0.273.0> Feature flags: [x] quorum_queue
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.238 [info] <0.273.0> Feature flags: [x] user_limits
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.239 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.240 [info] <0.273.0> Feature flags: feature flag states written to disk: yes
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.271 [info] <0.273.0> Feature flag `virtual_host_metadata`: supported, attempt to enable...
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.280 [info] <0.273.0> Feature flag `virtual_host_metadata`: mark as enabled=state_changing
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.297 [info] <0.273.0> Feature flags: list of feature flags found:
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.297 [info] <0.273.0> Feature flags: [x] drop_unroutable_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.299 [info] <0.273.0> Feature flags: [x] empty_basic_get_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.300 [info] <0.273.0> Feature flags: [x] implicit_default_bindings
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.301 [info] <0.273.0> Feature flags: [x] maintenance_mode_status
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.301 [info] <0.273.0> Feature flags: [x] quorum_queue
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.302 [info] <0.273.0> Feature flags: [x] user_limits
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.303 [info] <0.273.0> Feature flags: [~] virtual_host_metadata
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.305 [info] <0.273.0> Feature flags: feature flag states written to disk: yes
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.346 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.355 [info] <0.273.0> Successfully synced tables from a peer
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.380 [info] <0.273.0> Feature flag `virtual_host_metadata`: mark as enabled=true
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.397 [info] <0.273.0> Feature flags: list of feature flags found:
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.399 [info] <0.273.0> Feature flags: [x] drop_unroutable_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.401 [info] <0.273.0> Feature flags: [x] empty_basic_get_metric
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.403 [info] <0.273.0> Feature flags: [x] implicit_default_bindings
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.405 [info] <0.273.0> Feature flags: [x] maintenance_mode_status
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.405 [info] <0.273.0> Feature flags: [x] quorum_queue
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.406 [info] <0.273.0> Feature flags: [x] user_limits
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.407 [info] <0.273.0> Feature flags: [x] virtual_host_metadata
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.407 [info] <0.273.0> Feature flags: feature flag states written to disk: yes
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.435 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.446 [info] <0.273.0> Successfully synced tables from a peer
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.511 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.515 [info] <0.273.0> Successfully synced tables from a peer
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.515 [info] <0.273.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping registration.
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.518 [info] <0.273.0> Running boot step database_sync defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.519 [info] <0.273.0> Running boot step feature_flags defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.520 [info] <0.273.0> Running boot step codec_correctness_check defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.520 [info] <0.273.0> Running boot step external_infrastructure defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.521 [info] <0.273.0> Running boot step rabbit_registry defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.523 [info] <0.273.0> Running boot step rabbit_auth_mechanism_cr_demo defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.524 [info] <0.273.0> Running boot step rabbit_queue_location_random defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.527 [info] <0.273.0> Running boot step rabbit_event defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.529 [info] <0.273.0> Running boot step rabbit_auth_mechanism_amqplain defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.530 [info] <0.273.0> Running boot step rabbit_auth_mechanism_plain defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.531 [info] <0.273.0> Running boot step rabbit_exchange_type_direct defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.531 [info] <0.273.0> Running boot step rabbit_exchange_type_fanout defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.532 [info] <0.273.0> Running boot step rabbit_exchange_type_headers defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.533 [info] <0.273.0> Running boot step rabbit_exchange_type_topic defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.533 [info] <0.273.0> Running boot step rabbit_mirror_queue_mode_all defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.534 [info] <0.273.0> Running boot step rabbit_mirror_queue_mode_exactly defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.535 [info] <0.273.0> Running boot step rabbit_mirror_queue_mode_nodes defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.536 [info] <0.273.0> Running boot step rabbit_priority_queue defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.536 [info] <0.273.0> Priority queues enabled, real BQ is rabbit_variable_queue
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.536 [info] <0.273.0> Running boot step rabbit_queue_location_client_local defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.539 [info] <0.273.0> Running boot step rabbit_queue_location_min_masters defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.541 [info] <0.273.0> Running boot step kernel_ready defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.541 [info] <0.273.0> Running boot step rabbit_sysmon_minder defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.545 [info] <0.273.0> Running boot step rabbit_epmd_monitor defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.552 [info] <0.625.0> epmd monitor knows us, inter-node communication (distribution) port: 25672
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.554 [info] <0.273.0> Running boot step guid_generator defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.558 [info] <0.273.0> Running boot step rabbit_node_monitor defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.560 [info] <0.629.0> Starting rabbit_node_monitor
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.561 [info] <0.273.0> Running boot step delegate_sup defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.564 [info] <0.273.0> Running boot step rabbit_memory_monitor defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.568 [info] <0.273.0> Running boot step core_initialized defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.568 [info] <0.273.0> Running boot step upgrade_queues defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.634 [info] <0.273.0> message_store upgrades: 1 to apply
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.635 [info] <0.273.0> message_store upgrades: Applying rabbit_variable_queue:move_messages_to_vhost_store
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.637 [info] <0.273.0> message_store upgrades: No durable queues found. Skipping message store migration
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.637 [info] <0.273.0> message_store upgrades: Removing the old message store data
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.643 [info] <0.273.0> message_store upgrades: All upgrades applied successfully
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.704 [info] <0.273.0> Running boot step channel_tracking defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.710 [info] <0.273.0> Setting up a table for channel tracking on this node: tracked_channel_on_node_rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.716 [info] <0.273.0> Setting up a table for channel tracking on this node: tracked_channel_table_per_user_on_node_rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.717 [info] <0.273.0> Running boot step rabbit_channel_tracking_handler defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.718 [info] <0.273.0> Running boot step connection_tracking defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.725 [info] <0.273.0> Setting up a table for connection tracking on this node: tracked_connection_on_node_rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.733 [info] <0.273.0> Setting up a table for per-vhost connection counting on this node: tracked_connection_per_vhost_on_node_rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.739 [info] <0.273.0> Setting up a table for per-user connection counting on this node: tracked_connection_table_per_user_on_node_rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.740 [info] <0.273.0> Running boot step rabbit_connection_tracking_handler defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.741 [info] <0.273.0> Running boot step rabbit_exchange_parameters defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.743 [info] <0.273.0> Running boot step rabbit_mirror_queue_misc defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.744 [info] <0.273.0> Running boot step rabbit_policies defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.746 [info] <0.273.0> Running boot step rabbit_policy defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.747 [info] <0.273.0> Running boot step rabbit_queue_location_validator defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.748 [info] <0.273.0> Running boot step rabbit_quorum_memory_manager defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.749 [info] <0.273.0> Running boot step rabbit_vhost_limit defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.749 [info] <0.273.0> Running boot step rabbit_mgmt_reset_handler defined by app rabbitmq_management
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.750 [info] <0.273.0> Running boot step rabbit_mgmt_db_handler defined by app rabbitmq_management_agent
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.750 [info] <0.273.0> Management plugin: using rates mode 'basic'
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.756 [info] <0.273.0> Running boot step recovery defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.758 [info] <0.273.0> Running boot step empty_db_check defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.758 [info] <0.273.0> Will seed default virtual host and user...
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.761 [info] <0.273.0> Adding vhost 'taiga' (description: 'Default virtual host', tags: [])
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.775 [info] <0.688.0> Making sure data directory '/var/lib/rabbitmq/mnesia/rabbit@db02ef3ad502/msg_stores/vhosts/DUUPSD51ILPPE6LUATO0IN63B' for vhost 'taiga' exists
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.780 [info] <0.688.0> Starting message stores for vhost 'taiga'
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.781 [info] <0.692.0> Message store "DUUPSD51ILPPE6LUATO0IN63B/msg_store_transient": using rabbit_msg_store_ets_index to provide index
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.784 [info] <0.688.0> Started message store of type transient for vhost 'taiga'
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.787 [info] <0.696.0> Message store "DUUPSD51ILPPE6LUATO0IN63B/msg_store_persistent": using rabbit_msg_store_ets_index to provide index
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.789 [warning] <0.696.0> Message store "DUUPSD51ILPPE6LUATO0IN63B/msg_store_persistent": rebuilding indices from scratch
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.793 [info] <0.688.0> Started message store of type persistent for vhost 'taiga'
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.804 [info] <0.273.0> Created user 'taiga'
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.806 [info] <0.273.0> Successfully set user tags for user 'taiga' to [administrator]
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.811 [info] <0.273.0> Successfully set permissions for 'taiga' in virtual host 'taiga' to '.*', '.*', '.*'
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.811 [info] <0.273.0> Running boot step rabbit_looking_glass defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.812 [info] <0.273.0> Running boot step rabbit_core_metrics_gc defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.815 [info] <0.273.0> Running boot step background_gc defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.816 [info] <0.273.0> Running boot step routing_ready defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.816 [info] <0.273.0> Running boot step pre_flight defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.817 [info] <0.273.0> Running boot step notify_cluster defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.818 [info] <0.273.0> Running boot step networking defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.819 [info] <0.273.0> Running boot step definition_import_worker_pool defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.823 [info] <0.348.0> Starting worker pool 'definition_import_pool' with 1 processes in it
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.824 [info] <0.273.0> Running boot step cluster_name defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.825 [info] <0.273.0> Initialising internal cluster ID to 'rabbitmq-cluster-id-I0dDgKBKRMxhFMTzXrQC_Q'
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.828 [info] <0.273.0> Running boot step direct_client defined by app rabbit
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.829 [info] <0.273.0> Running boot step rabbit_management_load_definitions defined by app rabbitmq_management
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.831 [info] <0.726.0> Resetting node maintenance status
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.832 [info] <0.44.0> Application rabbit started on node rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.843 [info] <0.44.0> Application rabbitmq_management_agent started on node rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.845 [info] <0.44.0> Application cowlib started on node rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.847 [info] <0.44.0> Application cowboy started on node rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.851 [info] <0.44.0> Application rabbitmq_web_dispatch started on node rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.853 [info] <0.44.0> Application amqp_client started on node rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.966 [info] <0.785.0> Management plugin: HTTP (non-TLS) listener started on port 15672
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.970 [info] <0.813.0> Statistics database started.
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.972 [info] <0.812.0> Starting worker pool 'management_worker_pool' with 3 processes in it
taiga-events-rabbitmq_1 | 2021-05-24 09:40:22.976 [info] <0.44.0> Application rabbitmq_management started on node rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | 2021-05-24 09:40:23.048 [info] <0.44.0> Application prometheus started on node rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | 2021-05-24 09:40:23.056 [info] <0.826.0> Prometheus metrics: HTTP (non-TLS) listener started on port 15692
taiga-events-rabbitmq_1 | 2021-05-24 09:40:23.057 [info] <0.44.0> Application rabbitmq_prometheus started on node rabbit@db02ef3ad502
taiga-events-rabbitmq_1 | 2021-05-24 09:40:23.057 [info] <0.726.0> Ready to start client connection listeners
taiga-events-rabbitmq_1 | 2021-05-24 09:40:23.066 [info] <0.870.0> started TCP listener on [::]:5672
taiga-events-rabbitmq_1 | 2021-05-24 09:40:24.204 [info] <0.726.0> Server startup complete; 4 plugins started.
taiga-events-rabbitmq_1 | * rabbitmq_prometheus
taiga-events-rabbitmq_1 | * rabbitmq_management
taiga-events-rabbitmq_1 | * rabbitmq_web_dispatch
taiga-events-rabbitmq_1 | * rabbitmq_management_agent
taiga-events-rabbitmq_1 | completed with 4 plugins.
taiga-events-rabbitmq_1 | 2021-05-24 09:40:24.209 [info] <0.726.0> Resetting node maintenance status
taiga-async_1 | [2021-05-24 09:40:24,626: ERROR/MainProcess] consumer: Cannot connect to amqp://taiga:**@taiga-async-rabbitmq:5672/taiga: failed to resolve broker hostname.
taiga-async_1 | Trying again in 14.00 seconds...
taiga-async_1 |
taiga-async_1 | [2021-05-24 09:40:38,829: ERROR/MainProcess] consumer: Cannot connect to amqp://taiga:**@taiga-async-rabbitmq:5672/taiga: failed to resolve broker hostname.
taiga-async_1 | Trying again in 16.00 seconds...
taiga-async_1 |
taiga-back_1 | [2021-05-24 09:40:40 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:26)
taiga-back_1 | [2021-05-24 09:40:40 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:27)
taiga-back_1 | [2021-05-24 09:40:40 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:28)
taiga-back_1 | [2021-05-24 09:40:41 +0000] [29] [INFO] Booting worker with pid: 29
taiga-back_1 | [2021-05-24 09:40:41 +0000] [30] [INFO] Booting worker with pid: 30
taiga-back_1 | [2021-05-24 09:40:41 +0000] [31] [INFO] Booting worker with pid: 31
taiga-async_1 | [2021-05-24 09:40:55,230: ERROR/MainProcess] consumer: Cannot connect to amqp://taiga:**@taiga-async-rabbitmq:5672/taiga: failed to resolve broker hostname.
taiga-async_1 | Trying again in 18.00 seconds...
taiga-async_1 |
taiga-events-rabbitmq_1 | Killed
taiga-docker_taiga-events-rabbitmq_1 exited with code 0
taiga-back_1 | [2021-05-24 09:41:12 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:29)
taiga-back_1 | [2021-05-24 09:41:12 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:30)
taiga-back_1 | [2021-05-24 09:41:12 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:31)
taiga-back_1 | [2021-05-24 09:41:13 +0000] [44] [INFO] Booting worker with pid: 44
taiga-back_1 | [2021-05-24 09:41:13 +0000] [45] [INFO] Booting worker with pid: 45
taiga-back_1 | [2021-05-24 09:41:13 +0000] [46] [INFO] Booting worker with pid: 46
taiga-async_1 | [2021-05-24 09:41:13,390: ERROR/MainProcess] consumer: Cannot connect to amqp://taiga:**@taiga-async-rabbitmq:5672/taiga: failed to resolve broker hostname.
taiga-async_1 | Trying again in 20.00 seconds...
taiga-async_1 |
taiga-async_1 | [2021-05-24 09:41:33,668: ERROR/MainProcess] consumer: Cannot connect to amqp://taiga:**@taiga-async-rabbitmq:5672/taiga: failed to resolve broker hostname.
taiga-async_1 | Trying again in 22.00 seconds...
taiga-async_1 |
taiga-docker_taiga-async_1 exited with code 137
I'm using latest taiga-docker on Ubuntu 20.04, followed the "Install Taiga in production" guide, "Advanced configuration and customisation" section.
I can't figure out what are the correct parameters for EVENTS_PUSH_BACKEND_OPTIONS and CELERY_BROKER_URL in the mapped config.py .
EVENTS_PUSH_BACKEND_OPTIONS = {
"url": "amqp://taiga:[email protected]:5672/taiga"
}
CELERY_BROKER_URL = "amqp://taiga:[email protected]:5672/taiga"
This is my current conf and the logs say:
ERROR/MainProcess] consumer: Cannot connect to amqp://taiga:**@myhostname.com:5672/taiga: [Errno 111] Connection refused
The guide says user and pwd should be the same for the Postgres DB. About the host I already tried localhost or keeping the default one, trying to guess it was a inner variable.
EDIT: I see now that this new repo has different base config files... should I install this taiga-docker instead?
Hello everyone, I've done a clean docker install but when I go to the IP:9000 I can't create new projects (keeps loading).
From the console I see this error:
angular.js:14195 WebSocket error: [object Event]
(anonymous) @ angular.js:14195
e.onError @ app.js:3565
t @ lodash.js:4949
value @ elements.js:1
value @ elements.js:1
value @ elements.js:1
o @ elements.js:1
v @ elements.js:1
error (async)
a @ elements.js:1
value @ elements.js:1
value @ elements.js:1
value @ elements.js:1
(anonymous) @ elements.js:1
e.setupConnection @ app.js:3322
t @ lodash.js:4949
value @ elements.js:1
value @ elements.js:1
value @ elements.js:1
invoke @ elements.js:1
t.args.<computed> @ elements.js:1
setTimeout (async)
l @ elements.js:1
value @ elements.js:1
value @ elements.js:1
value @ elements.js:1
w @ elements.js:1
(anonymous) @ elements.js:1
T.r.<computed> @ elements.js:1
e.onClose @ app.js:3574
t @ lodash.js:4949
value @ elements.js:1
value @ elements.js:1
value @ elements.js:1
o @ elements.js:1
v @ elements.js:1
app.js:3319 WebSocket connection to 'ws://10.146.115.135:9000/events' failed:
e.setupConnection @ app.js:3319
t @ lodash.js:4949
value @ elements.js:1
value @ elements.js:1
value @ elements.js:1
invoke @ elements.js:1
t.args.<computed> @ elements.js:1
This is my taiga.conf
server {
listen 80 default_server;
client_max_body_size 100M;
charset utf-8;
# Frontend
location / {
proxy_pass http://taiga-front/;
proxy_pass_header Server;
proxy_set_header Host $http_host;
proxy_redirect off;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Scheme $scheme;
}
# API
location /api/ {
proxy_pass http://taiga-back:8000/api/;
proxy_pass_header Server;
proxy_set_header Host $http_host;
proxy_redirect off;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Scheme $scheme;
}
# Admin
location /admin/ {
proxy_pass http://taiga-back:8000/admin/;
proxy_pass_header Server;
proxy_set_header Host $http_host;
proxy_redirect off;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Scheme $scheme;
}
# Static
location /static/ {
alias /taiga/static/;
}
# Media
location /_protected/ {
internal;
alias /taiga/media/;
add_header Content-disposition "attachment";
}
# Unprotected section
location /media/exports/ {
alias /taiga/media/exports/;
add_header Content-disposition "attachment";
}
location /media/ {
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_pass http://taiga-protected:8003/;
proxy_redirect off;
}
# Events
location /events/ {
proxy_pass http://10.146.115.135:8888/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;
}
}
And this is my docker-compose.yml
, I didn't really change much beside the IP instead of localhost
GNU nano 4.8 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_SCHEME: "http"
TAIGA_SITES_DOMAIN: "http://10.146.115.135:9000"
TAIGA_SUBPATH: "" # "" or "/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: "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.8-management-alpine
environment:
RABBITMQ_ERLANG_COOKIE: secret-erlang-cookie
RABBITMQ_DEFAULT_USER: taiga
RABBITMQ_DEFAULT_PASS: taiga
RABBITMQ_DEFAULT_VHOST: taiga
volumes:
- taiga-async-rabbitmq-data:/var/lib/rabbitmq
networks:
- taiga
taiga-front:
image: taigaio/taiga-front:latest
environment:
TAIGA_URL: "http://10.146.115.135:9000"
TAIGA_WEBSOCKETS_URL: "ws://10.146.115.135:9000"
TAIGA_SUBPATH: "" # "" or "/subpath"
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.8-management-alpine
environment:
RABBITMQ_ERLANG_COOKIE: secret-erlang-cookie
RABBITMQ_DEFAULT_USER: taiga
RABBITMQ_DEFAULT_PASS: taiga
RABBITMQ_DEFAULT_VHOST: taiga
volumes:
- taiga-events-rabbitmq-data:/var/lib/rabbitmq
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:
taiga-async-rabbitmq-data:
taiga-events-rabbitmq-data:
networks:
taiga:
I understand is a matter of events, but can't figure out how to fix it. I'm running on Ubuntu 20.04
thanks!
Good morning,
I have a Websocket problem, which I couldn't solve.
I performed the installation and configuration according to the documentation.
From what I've tested, the system is working normally but in the browser's developer tools it follows the websocket error.
WebSocket connection to 'ws://177.71.112.103:9000/events' failed: app.js:3359
e.setupConnection @app.js:3359
WebSocket error: [object Event] angular.js:14195
(anonymous) @angular.js:14195
WebSocket connection to 'ws:/events' failed: WebSocket is closed before the connection is established.
Describe the bug
I have followed the instructions for launching a new instance (https://resources.taiga.io/30min-setup/). I have a VM setup in Azure that I am doing this testing on. Due to firewall restrictions I need to run Nginx to proxy port 80 to localhost:9000. This seems to be a very common problem so I am not sure if it is just a simple config item I am missing. I will detail my steps further below.
How can we reproduce the behavior
./launch-all.sh
./taiga-manage.sh createsuperuser
You have 257 unapplied migration(s). Your project may not work properly until you apply the migrations for app(s): admin, attachments, auth, bitbucket, contact, contenttypes, custom_attributes, djmail, easy_thumbnails, epics, external_apps, feedback, github, gitlab, gogs, history, issues, likes, milestones, notifications, projects, references, sessions, settings, tasks, telemetry, timeline, users, userstorage, userstories, votes, webhooks, wiki.
Run 'python manage.py migrate' to apply them.
./taiga-manage.sh migrate
as per the message./taiga-manage.sh createsuperuser
and works as expectedI have deployed taiga but neither created an admin user nor the default admin user with username admin
and password 123123
is working, could anyone help me creating one.
Describe the bug
Nginx 502 Error with /api/v1 urls
How can we reproduce the behavior
Just try to login to the application it throws the 502 error.
Workarounds
NA
Screenshots
NA
Taiga environment
Self Hosted
Desktop (please complete the following information):
ubuntu 20.04 LTS
Additional context
taiga-events_1 container fails with error:
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start:production: NODE_ENV=production node ./src/index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start:production script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /taiga-events/.npm/_logs/2021-10-02T13_47_35_746Z-debug.log
Complete log file content:
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli '/usr/local/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'run',
1 verbose cli 'start:production'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose config Skipping project config: /taiga-events/.npmrc. (matches userconfig)
5 verbose run-script [ 'prestart:production', 'start:production', 'poststart:production' ]
6 info lifecycle [email protected]prestart:production: [email protected]start:production: [email protected]
7 info lifecycle [email protected]
8 verbose lifecycle [email protected]start:production: unsafe-perm in lifecycle truestart:production: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/taiga-events/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
9 verbose lifecycle [email protected]
10 verbose lifecycle [email protected]start:production: CWD: /taiga-eventsstart:production: Args: [ '-c', 'NODE_ENV=production node ./src/index.js' ]
11 silly lifecycle [email protected]
12 silly lifecycle [email protected]start:production: Returned: code: 1 signal: nullstart:production: Failed to exec start:production script
13 info lifecycle [email protected]
14 verbose stack Error: [email protected] start:production: NODE_ENV=production node ./src/index.js
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
14 verbose stack at EventEmitter.emit (events.js:314:20)
14 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
14 verbose stack at ChildProcess.emit (events.js:314:20)
14 verbose stack at maybeClose (internal/child_process.js:1022:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
15 verbose pkgid [email protected]
16 verbose cwd /taiga-events
17 verbose Linux 3.10.0-1160.31.1.el7.x86_64
18 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "start:production"
19 verbose node v12.22.1
20 verbose npm v6.14.12
21 error code ELIFECYCLE
22 error errno 1
23 error [email protected] start:production: NODE_ENV=production node ./src/index.js
23 error Exit status 1
24 error Failed at the [email protected] start:production script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]
Describe the bug
After deploying a self-hosted instance of Taiga 6, I observed that the project timeline in the web UI is always empty.
Instead of that, I would expect that timeline to gradually be filled, as user stories, tasks, etc are created and changed for that project.
How can we reproduce the behavior
Workarounds
After reading the details of issue https://github.com/taigaio/taiga-back/issues/709 I found that running the backend command python manage.py rebuild_timeline_iterating_per_projects
makes that previous entries appear, but new ones will not appear.
Taiga environment
Desktop (please complete the following information):
Questions
CELERY_ALWAYS_EAGER
setting no longer exists for the Taiga backend?Thanks in advance.
Hi, is there a way to set the default language for Taiga in this docker? Example, I want to set the default language to Spanish (without the need to set in every user creation).
I only see this variable in conf.json. So, I ask if this is the right place.
Thanks.
TLDR: Please add official LDAPS support to the Taiga 6 docker installation and/or provide some step by step guide explaining how to install and maintain the community addons to the docker installation. That would be great.
Okay so please excuse that I have to get some tears flowing regarding the missing (suported) LDAPS functionality in Taiga 6:
We're currently evaluating Taiga for a non profit hospital. We have absolutely zero budget to buy ourself project management software and using free cloud services or any cloud services at all is forbidden by german law. We also have close to zero time allocated to improving the status quo of working with excel files on network shares so we're currently struggling through getting Taiga 6 production ready in our free time in the middle of already pretty high workloads due to obvious reasons.
Taiga looks like a gift from heaven, enabling us to finally move away from excel files on network shares to something visually and functionally appealing (even for non-IT teams. Looking at you, free JIRA software license for nonprofits where the software focused terminology and workflow is forced upon everybody…) to coordinate tasks and ideas across teams from different departments.
Okay so now that I built up the appropriate amount of pity to get your attention :-P
Please please please take us on-premise folks that have to rely heavily on LDAPS into account when planning your next development sprints. I am pretty sure most of us on premise folks have tons of experience with virtualization solutions like VMWare but are total docker noobs.
I know that I am struggling through a lot of problems that are basically solved with basic docker knowledge and installing the community plugin in your docker installation is probably easy for a dev with a lot of Docker experience but for us old and gnarly sysadmins it's just super confusing and we have to make sure every deployment checks certain boxes like “can we test backups, updates, restores” and “can we plug it into our LDAP to manage our 300 users that constantly forget passwords”.
Thanks for the great work overall, this project really looks like it could shape up to become the gold standard in free and open source project management :-)
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"
Could anyone help me setting up apache2 reverse proxy my current config is:
ProxyPass "/" "http://localhost:9000/" connectiontimeout=5 timeout=30 keepalive=on
ProxyPassReverse "/" "http://localhost:9000/"
RewriteEngine on
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteCond %{HTTP:Connection} upgrade [NC]
RewriteRule ^/?(.*) "ws://localhost:9000//$1" [P,L]
ProxyPass "/events" "ws://localhost:9000/events" connectiontimeout=5 timeout=30 keepalive=on
ProxyPassReverse "/events" "ws://localhost:9000/events"
but It's giving an error while signing up.
angular.js:14195 WebSocket error: [object Event]
(anonymous) @ angular.js:14195
e.onError @ app.js:3565
t @ lodash.js:4949
value @ elements.js:1
value @ elements.js:1
value @ elements.js:1
o @ elements.js:1
v @ elements.js:1
error (async)
a @ elements.js:1
value @ elements.js:1
value @ elements.js:1
value @ elements.js:1
(anonymous) @ elements.js:1
e.setupConnection @ app.js:3322
t @ lodash.js:4949
value @ elements.js:1
value @ elements.js:1
value @ elements.js:1
invoke @ elements.js:1
t.args.<computed> @ elements.js:1
setTimeout (async)
l @ elements.js:1
value @ elements.js:1
value @ elements.js:1
value @ elements.js:1
w @ elements.js:1
(anonymous) @ elements.js:1
T.r.<computed> @ elements.js:1
e.onClose @ app.js:3574
t @ lodash.js:4949
value @ elements.js:1
value @ elements.js:1
value @ elements.js:1
o @ elements.js:1
v @ elements.js:1
May have had a messy docker-compose.yml
that originally did not override the TAIGA_SITES_DOMAIN
while setting up Taiga - it worked just fine with just TAIGA_URL
, though. Then I noticed that while attachments can be uploaded, the media links are still to localhost:9000
.
TAIGA_SITES_DOMAIN
to the domain used - did not workconfig.py
- did not workconfig.py
the value of MEDIA_URL
- shows the expected value, e.g.,[33mtaiga-async_1 |ESC[0m WARNING:root:MEDIA_URL = https://my.domain/media/
Yet I get attachment links like
http://localhost:9000/media/attachments/f/a/b/2/04ea6bb76aedc3f0b1071a24c17498014528c09f488ae1bce64fd8ebeb5d/mplayer-youtube.txt?token=YbQG-g%3AUiZG3CVEO6YVxX8uYAQWVYolNUu075WAd8ujLLG8eRXB6e0vTuuxEOQ_hwRNWC1YHsO8gHC1Qhu6dT19kXybQQ#_taiga-refresh=userstory:5
Is there some cache I should clear somewhere? It would be great if I didn't have to start from scratch. :-)
docker-compose.yml
- TAIGA_SITES_SCHEME: "http"
- TAIGA_SITES_DOMAIN: "localhost:9000"
+ TAIGA_SITES_SCHEME: "https"
+ TAIGA_SITES_DOMAIN: "my.domain"
[...]
- TAIGA_URL: "http://localhost:9000"
- TAIGA_WEBSOCKETS_URL: "ws://localhost:9000"
+ TAIGA_URL: "https://my.domain"
+ TAIGA_WEBSOCKETS_URL: "wss://my.domain"
(The first change came after already having used Taiga for a while.)
Please describe the problem / need you are trying to solve.
Trying to run taiga-docker (launch-taiga.sh) on Kubernetes.
Describe the feature or the improvement you'd like and what are you trying to achieve.
Baseline of manifests to allow easy deployment on Kubernetes clusters.
Describe alternatives you've considered
Bare yaml files or building a Helm chart.
Additional context
NA
Describe the bug
RabbitMQ deprecated in the 3.9
release a bunch of environment variables that were used by the taiga-docker
repository. Containers taiga-async-rabbitmq
and taiga-events-rabbitmq
fail to start because of this change. Both stable
and main
branches are affected.
How can we reproduce the behavior
Clone the repo from stable
or main
branch. Run ./launch-taiga.sh
. Both containers will exit with an error.
Workarounds
Specify a concrete RabbitMQ version in the image tag (e.g. rabbitmq:3-management-alpine
-> rabbitmq:3.8-management-alpine
).
Desktop (please complete the following information):
I've been trying to set up a taiga environment for testing using the 30min setup guide at taiga.io.
I've created a new VM running Ubuntu 20.04, Docker 20.10.7 and Docker-Compose 1.29.2.
This VM has the hostname "taiga" and is reachable under "http://taiga/".
I'm currently using the following 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"
TAIGA_SITES_SCHEME: "http"
# 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: "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
volumes:
- taiga-async-rabbitmq-data:/var/lib/rabbitmq
networks:
- taiga
taiga-front:
image: taigaio/taiga-front:latest
environment:
TAIGA_URL: "http://taiga"
TAIGA_WEBSOCKETS_URL: "ws://taiga"
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
volumes:
- taiga-events-rabbitmq-data:/var/lib/rabbitmq
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:
taiga-async-rabbitmq-data:
taiga-events-rabbitmq-data:
networks:
taiga:
and the following taiga.conf in /etc/nginx/conf.d/taiga.conf:
server {
server_name taiga;
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;
}
}
After running "launch-all.sh", I can connect to my Taiga instance at "http://taiga" and login as the superuser I created.
Whenever I try to create a project, I end up with a spinning wheel and the console reports
"elements.js:1 POST http://taiga/api/v1/projects 500 (Internal Server Error)".
The log of taiga-back contains:
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /api/v1/projects
From: root@localhost
To: [email protected]
Date: Sat, 31 Jul 2021 12:01:51 -0000
Message-ID: <162773291136.32.10133582904113318513@2fad224a4f25>
Internal Server Error: /api/v1/projects
Exception Value: failed to resolve broker hostname
Request information:
USER: AnonymousUser
-------------------------------------------------------------------------------
ERROR:2021-07-31 12:01:51,309: Internal Server Error: /api/v1/projects
Traceback (most recent call last):
File "/opt/venv/lib/python3.7/site-packages/amqp/transport.py", line 138, in _connect
host, port, family, socket.SOCK_STREAM, SOL_TCP)
File "/usr/local/lib/python3.7/socket.py", line 752, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Temporary failure in name resolution
and later (after a lot of python traceback):
OSError: failed to resolve broker hostname
The vm can ping itself using taiga, so the DNS is properly set up, pinging other (external) domains does work as well.
I'm a bit confused about the Django message from root@localhost to [email protected], is this just default behavior as I haven't set up smtp?
I first suspected this issue to be related to the local nature of my setup but I experienced the same when using "taiga.mydomain.com" as hostname (I changed the hostname in docker-compose.yml, of course).
I'm pretty sure I'm missing something obvious here, but I've tried setting this up four times now without any luck.
Thank you for your help :)
Describe the bug
We went through the installation guide and made changes to latest stable docker-compose.yml. We observed new folders rabbitmq@randomstring in /var/lib/docker/volumes/taiga-docker_taiga-async-rabbitmq-data
and /var/lib/docker/volumes/taiga-docker_taiga-events-rabbitmq-data
(>300 MB each) after every docker-compose up
. According docker-library/rabbitmq#391 rabbitmq uses the hostname as part of the folder name, like rabbitmq@[hostname]. I suspect, without giving a hostname, rabbitmq creates a new directory with a random string, but the older ones are no longer needed.
How can we reproduce the behavior
taiga-docker_taiga-async-rabbitmq-data
and taiga-docker_taiga-events-rabbitmq-data
Workarounds
After setting a hostname in taiga-async-rabbitmq and taiga-events-rabbitmq, rabbitmq uses always the same directory without creating new ones.
taiga-async:
image: taigaio/taiga-back:latest
hostname: "taiga-async-rabbitmq"
volumes:
- taiga-async-rabbitmq-data:/var/lib/rabbitmq
[..]
taiga-events-rabbitmq:
image: rabbitmq:3.8-management-alpine
hostname: "taiga-events-rabbitmq"
volumes:
- taiga-events-rabbitmq-data:/var/lib/rabbitmq
Taiga environment
Self-hosted latest stable taiga-docker
The documentation mentions:
IMPORTANT NOTICE: When you're configuring Taiga to run with HTTPS, you should configure TAIGA_URL with https and TAIGA_WEBSOCKETS_URL with wss.
What additional steps are necessary to get SSL working?
.
.
** troubleshooting **
I've set:
x-environment
TAIGA_SITES_DOMAIN: "host.[domain]"
TAIGA_SITES_SCHEME: "https"
taiga-front
TAIGA_URL: "https://host.[domain]"
TAIGA_WEBSOCKETS_URL: "wss://host.[domain]
then
docker-compose down; docker-compose up -d
Next, enter the container taiga-docker_taiga-front_1 and modify /etc/nginx/conf.d/default with:
listen 443 default_server;
server_name host.[domain];
ssl_certificate tls.crt;
ssl_certificate_key tls.key;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers HIGH:!aNULL:!MD5;
and I copied over tls.crt & tls.key to:
/etc/nginx/tls.crt
/etc/nginx/tls.key
then
docker restart taiga-docker_taiga-front_1
I'm not sure what else to try.
please show me there a way to use multiple domains for taiga?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.