Self host Taiga 30 mins setup: How to install on a server and use IP address:port number

Troubleshooting Self hosted Taiga
1

I am following all the steps of Taiga 30min Setup
Where do i mention server IP address (instead of creating a domain name) and port number 9000.

Summary: I am not able to launch Taiga using IP address.

2

Hello @ranjankv

You don’t have to make any changes to use the public IP. By default it should already be accessible through the interfaces of the PC where you are installed it, through port 9000.

Best regards

3

Thank you David.

Please respond to below mentioned queries.

  1. DO i need to change this to IP address of the interface or leave it as it is? Also i am not planning to use domain name.
    TAIGA_DOMAIN=192.168.10.21:9000
    TAIGA_SITES_SCHEME = “https”
    TAIGA_SITES_DOMAIN = “192.168.10.21”
    “api”: “https://192.168.10.21/api/v1/”,
    “eventsUrl”: “wss://192.168.10.21/events”,

  2. In which file we do this setting?
    server {
    server_name taiga.mycompany.com;

    location / {
    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Scheme $scheme;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_redirect off;

    }

    Events

    location /events {
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection “upgrade”;
    proxy_set_header Host $host;
    proxy_connect_timeout 7d;
    proxy_send_timeout 7d;
    proxy_read_timeout 7d;
    }

    TLS: Configure your TLS following the best practices inside your company

    Logs and other configurations

}

4

Let’s imagine that the external IP of your machine is 192.168.10.21 (note, this is a private IP that will only be accessible from your internal network and not from the internet).

You have to replace localhost to 192.168.10.21. For example:

# Defaulr values in .env
TAIGA_SCHEME=http                                                                       
TAIGA_DOMAIN=192.168.10.21:9000                                                  
SUBPATH=""                                              
WEBSOCKETS_SCHEME=ws

You can access to http://192.168.10.21:9000/ with your browser and you see taiga homepage running.

5

For the second questions, if you want to serve taiga over https, you need to create a cert (with Let’s Encryp, OpenSSL or whatever) and use a local proxy pass server (like nginx) to set the cert and create the proxy pass to the taiga-gateway container.

The code in the guide is just an example of this, using a local nginx.

6

Thank you David, i was using https without creating certificate.
As of now i am able to login.
I have some more questions.

  1. How to add new users in Taiga.
  2. Making private will allow user i am adding to access this project, but not anyone from outside this group.
7

David, please ignore question-2.
For question-1; even after sending invite to team member, they have not received email. May be EMAIL settings are not correct in .env

8

Yes, you have to set the EMAIL settings properly to use your smtp server. You can check the logs of taiga-back, taiga-async and taiga-async-rabbitmq (with docker compose logs) to find if there is any error.

Sometime a mistake with the values for EMAIL_USE_SSL and EMAIL_USE_TSL are usually the problem.

9

David,

I want to enable public registeration so that user can sign up. ?

In tutorial it says to do this setting
-----> Add to &default-back-environment environments

PUBLIC_REGISTER_ENABLED: "True"

My .yml file

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

PUBLIC_REGISTER_ENABLED: “True”
SESSION_COOKIE_SECURE: “False”
CSRF_COOKIE_SECURE: “False”

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

10

The documentatio say:

Public registration

Public registration is disabled by default. If you want to allow a public register, you have to enable public registration on both, frontend and backend.

Note
Be careful with the upper and lower case in these settiings. We will use ‘True’ for the backend and ‘true’ for the frontend (this is not a typo, otherwise it won’t work).

Add to &default-back-environment environments

PUBLIC_REGISTER_ENABLED: "True"

Add to taiga-front service environments

PUBLIC_REGISTER_ENABLED: "true"

So you have to modify &default-back-environment and the taiga-front service too. Pay special attention to upper and lower case letters (True for the first one and true for the second one, it is not a typo).

11

David, Thank you for all your support.