Taiga shows error after installation

Troubleshooting Self hosted Taiga
1

Hello

I am trying to install Taiga on my Synology NAS with ARM64 architecture and need help.
Whole installation went smooth but I can’t create superuser and Taiga is stuck on this error page. I am also using Tailscale, maybe it is relevant here.

image
image1848×992 195 KB

I was using this page as guidance. Everything is as default. Changed some Taiga images to work with arm. With default ones I had errors.

sudo ./taiga-manage.sh createsuperuser

exec docker compose -f docker-compose.yml -f docker-compose-inits.yml run --rm taiga-manage createsuperuser
[+] Creating 1/0
✔ Container taiga-docker-taiga-db-1  Running                                                                                                                       0.0s
exec /opt/venv/bin/python: exec format error
failed to resize tty, using default size

Log from docker-compose up

sudo docker-compose up
Password:
[+] Running 9/0
✔ Container taiga-docker-taiga-front-1 Running 0.0s
✔ Container taiga-docker-taiga-async-rabbitmq-1 Running 0.0s
✔ Container taiga-docker-taiga-protected-1 Running 0.0s
✔ Container taiga-docker-taiga-events-rabbitmq-1 Running 0.0s
✔ Container taiga-docker-taiga-db-1 Running 0.0s
✔ Container taiga-docker-taiga-events-1 Running 0.0s
✔ Container taiga-docker-taiga-back-1 Running 0.0s
✔ Container taiga-docker-taiga-async-1 Running 0.0s
✔ Container taiga-docker-taiga-gateway-1 Running 0.0s
Attaching to taiga-docker-taiga-async-1, taiga-docker-taiga-async-rabbitmq-1, taiga-docker-taiga-back-1, taiga-docker-taiga-db-1, taiga-docker-taiga-events-1, taiga-docker-taiga-events-rabbitmq-1, taiga-docker-taiga-front-1, taiga-docker-taiga-gateway-1, taiga-docker-taiga-protected-1
taiga-docker-taiga-async-1 | [2026-03-11 17:08:46,280: INFO/Beat] Scheduler: Sending due task send-bulk-emails (taiga.projects.notifications.tasks.send_bulk_email)
taiga-docker-taiga-async-1 | [2026-03-11 17:08:46,286: INFO/MainProcess] Task taiga.projects.notifications.tasks.send_bulk_email[91320fa7-6005-4da2-aab4-7737b30dd723] received
taiga-docker-taiga-front-1 | 172.19.0.10 - - [11/Mar/2026:17:10:11 +0000] “GET / HTTP/1.0” 304 0 “``http://100.91.148.1:9000/discover”`` “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36 OPR/128.0.0.0” “-”
taiga-docker-taiga-gateway-1 | 172.19.0.1 - - [11/Mar/2026:17:10:11 +0000] “GET / HTTP/1.1” 304 0 “``http://100.91.148.1:9000/discover”`` “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36 OPR/128.0.0.0” “-”
taiga-docker-taiga-async-1 | [2026-03-11 17:10:46,283: INFO/Beat] Scheduler: Sending due task send-bulk-emails (taiga.projects.notifications.tasks.send_bulk_email)
taiga-docker-taiga-async-1 | [2026-03-11 17:10:46,301: INFO/MainProcess] Task taiga.projects.notifications.tasks.send_bulk_email[078e05f6-ef3f-485d-970d-6ded1b82df27] received
taiga-docker-taiga-front-1 | 172.19.0.10 - - [11/Mar/2026:17:11:24 +0000] “GET /discover HTTP/1.0” 304 0 “-” “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36 OPR/128.0.0.0” “-”
taiga-docker-taiga-gateway-1 | 172.19.0.1 - - [11/Mar/2026:17:11:24 +0000] “GET /discover HTTP/1.1” 304 0 “-” “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36 OPR/128.0.0.0” “-”
taiga-docker-taiga-front-1 | 172.19.0.10 - - [11/Mar/2026:17:11:24 +0000] “GET /conf.json HTTP/1.0” 304 0 “``http://100.91.148.1:9000/discover”`` “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36 OPR/128.0.0.0” “-”
taiga-docker-taiga-gateway-1 | 172.19.0.1 - - [11/Mar/2026:17:11:24 +0000] “GET /conf.json HTTP/1.1” 304 0 “``http://100.91.148.1:9000/discover”`` “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36 OPR/128.0.0.0” “-”

My docker-compose.yml

version: “3.5”

x-environment:
&default-back-environment

These environment variables will be used by taiga-back and taiga-async.

Database settings

POSTGRES_DB: “taiga”
POSTGRES_USER: “${POSTGRES_USER}”
POSTGRES_PASSWORD: “${POSTGRES_PASSWORD}”
POSTGRES_HOST: “taiga-db”

Taiga settings

TAIGA_SECRET_KEY: “${SECRET_KEY}”
TAIGA_SITES_SCHEME: “${TAIGA_SCHEME}”
TAIGA_SITES_DOMAIN: “${TAIGA_DOMAIN}”
TAIGA_SUBPATH: “${SUBPATH}”

Email settings.

EMAIL_BACKEND: “django.core.mail.backends.${EMAIL_BACKEND}.EmailBackend”
DEFAULT_FROM_EMAIL: “${EMAIL_DEFAULT_FROM}”
EMAIL_USE_TLS: “${EMAIL_USE_TLS}”
EMAIL_USE_SSL: “${EMAIL_USE_SSL}”
EMAIL_HOST: “${EMAIL_HOST}”
EMAIL_PORT: “${EMAIL_PORT}”
EMAIL_HOST_USER: “${EMAIL_HOST_USER}”
EMAIL_HOST_PASSWORD: “${EMAIL_HOST_PASSWORD}”

Rabbitmq settings

RABBITMQ_USER: “${RABBITMQ_USER}”
RABBITMQ_PASS: “${RABBITMQ_PASS}”

Telemetry settings

ENABLE_TELEMETRY: “${ENABLE_TELEMETRY}”

…your customizations go here

x-volumes:
&default-back-volumes

These volumens will be used by taiga-back and taiga-async.

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: “${POSTGRES_USER}”
POSTGRES_PASSWORD: “${POSTGRES_PASSWORD}”
healthcheck:
test: [“CMD-SHELL”, “pg_isready -U ${POSTGRES_USER}”]
interval: 2s
timeout: 15s
retries: 5
start_period: 3s
volumes:
- taiga-db-data:/var/lib/postgresql/data
networks:
- taiga

taiga-back:
image: elestio/taiga-backend:latest
environment: *default-back-environment
volumes: *default-back-volumes
networks:
- taiga
depends_on:
taiga-db:
condition: service_healthy
taiga-events-rabbitmq:
condition: service_started
taiga-async-rabbitmq:
condition: service_started

taiga-async:
image: elestio/taiga-backend:latest
entrypoint: [“/taiga-back/docker/async_entrypoint.sh”]
environment: *default-back-environment
volumes: *default-back-volumes
networks:
- taiga
depends_on:
taiga-db:
condition: service_healthy
taiga-events-rabbitmq:
condition: service_started
taiga-async-rabbitmq:
condition: service_started

taiga-async-rabbitmq:
image: rabbitmq:3.8-management-alpine
environment:
RABBITMQ_ERLANG_COOKIE: “${RABBITMQ_ERLANG_COOKIE}”
RABBITMQ_DEFAULT_USER: “${RABBITMQ_USER}”
RABBITMQ_DEFAULT_PASS: “${RABBITMQ_PASS}”
RABBITMQ_DEFAULT_VHOST: “${RABBITMQ_VHOST}”
hostname: “taiga-async-rabbitmq”
volumes:
- taiga-async-rabbitmq-data:/var/lib/rabbitmq
networks:
- taiga

taiga-front:
image: elestio/taiga-frontend:latest
environment:
TAIGA_URL: “${TAIGA_SCHEME}://${TAIGA_DOMAIN}”
TAIGA_WEBSOCKETS_URL: “${WEBSOCKETS_SCHEME}://${TAIGA_DOMAIN}”
TAIGA_SUBPATH: “${SUBPATH}”
# …your customizations go here
networks:
- taiga
# volumes:
#   - ./conf.json:/usr/share/nginx/html/conf.json

taiga-events:
image: elestio/taiga-event:latest
environment:
RABBITMQ_USER: “${RABBITMQ_USER}”
RABBITMQ_PASS: “${RABBITMQ_PASS}”
TAIGA_SECRET_KEY: “${SECRET_KEY}”
networks:
- taiga
depends_on:
taiga-events-rabbitmq:
condition: service_started

taiga-events-rabbitmq:
image: rabbitmq:3.8-management-alpine
environment:
RABBITMQ_ERLANG_COOKIE: “${RABBITMQ_ERLANG_COOKIE}”
RABBITMQ_DEFAULT_USER: “${RABBITMQ_USER}”
RABBITMQ_DEFAULT_PASS: “${RABBITMQ_PASS}”
RABBITMQ_DEFAULT_VHOST: “${RABBITMQ_VHOST}”
hostname: “taiga-events-rabbitmq”
volumes:
- taiga-events-rabbitmq-data:/var/lib/rabbitmq
networks:
- taiga

taiga-protected:
image: elestio/taiga-protected:latest
environment:
MAX_AGE: “${ATTACHMENTS_MAX_AGE}”
SECRET_KEY: “${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:

Browser Console errors

app.js:3322 WebSocket connection to ‘ws://localhost:9000/events’ failed:
(anonymous) @ app.js:3322
angular.js:14195 WebSocket error: [object Event]
(anonymous) @ angular.js:14195
localhost:9000/api/v1/stats/discover:1 Failed to load resource: net::ERR_CONNECTION_REFUSED
localhost:9000/api/v1/projects?discover_mode=true&is_featured=true:1 Failed to load resource: net::ERR_CONNECTION_REFUSED
localhost:9000/api/v1/projects?discover_mode=true&order_by=-total_fans_last_year:1 Failed to load resource: net::ERR_CONNECTION_REFUSED
localhost:9000/api/v1/projects?discover_mode=true&order_by=-total_activity_last_year:1 Failed to load resource: net::ERR_CONNECTION_REFUSED
app.js:3322 WebSocket connection to ‘ws://localhost:9000/events’ failed:
(anonymous) @ app.js:3322
angular.js:14195 WebSocket error: [object Event]
(anonymous) @ angular.js:14195
app.js:3322 WebSocket connection to ‘ws://localhost:9000/events’ failed:
(anonymous) @ app.js:3322
angular.js:14195 WebSocket error: [object Event]
(anonymous) @ angular.js:14195
app.js:3322 WebSocket connection to ‘ws://localhost:9000/events’ failed:
(anonymous) @ app.js:3322
angular.js:14195 WebSocket error: [object Event]
(anonymous) @ angular.js:14195
app.js:3322 WebSocket connection to ‘ws://localhost:9000/events’ failed:
(anonymous) @ app.js:3322
angular.js:14195 WebSocket error: [object Event]
(anonymous) @ angular.js:14195
angular.js:14195 Events are disabled: the maximum number of connection errors has been reached.
(anonymous) @ angular.js:14195