Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] : Taiga installation with docker shows error screen, penpot working #119

Closed
Akshaychdev opened this issue Oct 20, 2023 · 2 comments
Closed
Labels
bug Something isn't working

Comments

@Akshaychdev
Copy link

Issue

Tried taiga installation as per the documentation.
But after containers spawned up and superuser created, getting this error startup screen.
No containers failed status/ none showing any visible ERRORs at docker log <container>.

image

Used the default .env settings (as it is for testing), used the ./launch-all.sh script, penpot seems working fine.

image

Environment.

Docker version: 24.0.6
Os version: Ubuntu 22.04.3 LTS
Project branch: Stable

Spawned containers

image

Logs

DB container - taiga-docker-taiga-db-1

2023-10-20 10:24:52.281 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-10-20 10:24:52.337 UTC [86] LOG:  database system was shut down at 2023-10-20 10:24:52 UTC
2023-10-20 10:24:52.352 UTC [1] LOG:  database system is ready to accept connections

There are no errors showing in other container logs

./taiga-manage.sh migrate shows no migrations.

What I've tried so far

  • Removed the containers and volumes docker compose down && docker container prune && docker volume prune -a and relaunched multiple times with default .env configuration with both launch-all.sh and launch-taiga.sh but with no sucess.

Mention if anything missing using default http -> with public Ip for testing.

@Akshaychdev Akshaychdev added the bug Something isn't working label Oct 20, 2023
@stamenminkov
Copy link

@Akshaychdev did you manage to solve that?

@Akshaychdev
Copy link
Author

@Akshaychdev did you manage to solve that?

Yes it was due to the .env settings, the web socket will try to connect to ws:localhost:9000 - by default,
from your browser it is not accessible - you can just see the error in browser js console,
it is the default value given in the .env file, change that to your real web url,

Default

TAIGA_SCHEME=http  # serve Taiga using "http" or "https" (secured) connection
TAIGA_DOMAIN=localhost:9000  # Taiga's base URL
SUBPATH=""  # it'll be appended to the TAIGA_DOMAIN (use either "" or a "/subpath")
WEBSOCKETS_SCHEME=ws  # events connection protocol (use either "ws" or "wss")

Change this if you are using http://<YOUR PUB IP>:9000 to test taiga
Remember to allow the inbound connections to port 9000 in your network/firewall settings.

TAIGA_SCHEME=http
TAIGA_DOMAIN=<YOUR IP>
SUBPATH=""
WEBSOCKETS_SCHEME=ws

If you are using your subdomain with nginx reverse proxy

TAIGA_SCHEME=https
TAIGA_DOMAIN=taiga.mycompany.com
SUBPATH=""
WEBSOCKETS_SCHEME=wss

docker container will expose the port 9000.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants