[SOLVED] Help with the 30min setup

[collex100]

I did everything according to this manual. No installation errors. Specified only external domains for two applications. How to remove errors?
How to remove a port from a domain?

[collex100]

Friends, I’ve been sitting in the evenings for a whole week trying to launch Taiga according to the Taiga 30 min Setup manual and my brain explodes))

The installation is done on the VPS. Directed the domain. I go through all the commands on OK.

On the domain taiga.mydomen.ltd:9000

I get a message that:

Something happened and the Taiga has captured the error to be able to work on it.

In the browser, the message p.js:3319 WebSocket connection to ‘ws://localhost:9000/events’ failed:

On the domain penpot.mydomen.ltd:9001
Bad Gateway

In the browser, the message:
Failed to load resource: the server responded with a status of 502 (Bad Gateway)
Eror in handleResponse UNK/SW_UNREACHABLE contextMenu createContextMenu
Eror: Could not establish connection. Receiving end does not exist.

I’m sitting on the forum, I see similar errors, but it’s as if the paths all lead nowhere.

In the installation itself, there is already an nginx container, everywhere on the forum it is said about nginx, so it is not clear where it should be inside the container or from the outside on the machine.

Yes, I’m not friends with docker, but if you pack everything into a container, why don’t you write how to work with this good.

In general, I am now a little at a loss what to do. The installation instructions are very crude. There is almost nothing about installing on a real machine, as an example, do one do two.

I sit and think what to do. should I try installing from the source code?

[collex100]

After installing Taiga according to this instruction, I get a white screen.
OS Ubuntu 20.04

Tell me please, what am I doing wrong?

Here’s what I’m doing:

Installation Docker

sudo apt update

sudo apt install apt-transport-https ca-certificates curl software-properties-common

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -

sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu focal stable"

sudo apt update

apt-cache policy docker-ce

docker-ce:
  Installed: (none)
  Candidate: 5:19.03.9~3-0~ubuntu-focal
  Version table:
     5:19.03.9~3-0~ubuntu-focal 500
        500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages

sudo apt install docker-ce

sudo systemctl status docker

Output● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2020-05-19 17:00:41 UTC; 17s ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 24321 (dockerd)
      Tasks: 8
     Memory: 46.4M
     CGroup: /system.slice/docker.service
             └─24321 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

apt install docker-compose

Installation Nginx

apt install nginx python3-certbot-nginx

unlink /etc/nginx/sites-enabled/default

nano /etc/nginx/sites-available/taiga.conf

Added settings with your domain taiga.mydomen.com:
Everywhere changed the address to 127.0.0.1.

server {
    server_name  taiga.mydomen.com;
    large_client_header_buffers 4 32k;
    client_max_body_size 50M;
    charset utf-8;
    access_log /var/log/nginx/reverse-access.log;
    error_log /var/log/nginx/reverse-error.log;
   
 # Frontend
    location / {
        proxy_pass http://127.0.0.1:9000/;
        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_pass http://127.0.0.1:9000/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;
    }

ln -s /etc/nginx/sites-available/taiga.conf /etc/nginx/sites-enabled/taiga.conf

service nginx reload

Preparation Taiga

sudo apt install git

sudo git clone https://github.com/kaleidos-ventures/taiga-docker.git

cd taiga-docker/
git checkout stable

.env

Added my domain

Installing the certificate SSL

certbot --nginx

Launch Taiga

cd taiga-docker/

./launch-taiga.sh

./taiga-manage.sh createsuperuser

Final NGINX

server {
    server_name  taiga.mydomen.com;
    large_client_header_buffers 4 32k;
    client_max_body_size 50M;
    charset utf-8;
    access_log /var/log/nginx/reverse-access.log;
    error_log /var/log/nginx/reverse-error.log;
    # Frontend
    location / {
        proxy_pass http://127.0.0.1:9000/;
        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_pass http://127.0.0.1:9000/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;
    }
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/taiga.mydomen.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/taiga.mydomen.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
            if ($host = taiga.mydomen.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot
   
    listen 80 default_server;
    server_name  taiga.mydomen.com;
    return 404; # managed by Certbot
}

[yami]

Hi @collex100

Everything seems mostly ok, there are not obvious errors, so we have to go through the configuration very carefully.

1. I assume that in your .env the domain the same as the domain in the nginx, is that correct?

2. with the last screenshot we can know several things:
   a) the API is working properly: https://taiga.6ministers.com/api/v1/
   b) the events URL should be wss://taiga.6ministers.com/events instead of ws://taiga.6ministers.com/events ( check the extra “s”)

3. One thing you can try is to configure the .env to http://localhost:9000, run everything and try it. If it works, we can know that the containers are working ok and the problem is in the nginx configuration.

Cheers!

[collex100]

Solved the issue point number 2. Thanks!!!

Your default manual is not effective enough. I spent a week in the evenings gathering installation methods from all over the Internet and experimenting myself. Ultimately, I used the Penpot installation from another location.

The current installation of Taiga I have been thinking for a long time how to use the settings. The installation instructions are very general and not practical.

[collex100]

Now this manual is working, which can be fully launched and everything is there.

Need to check Penpot with your instructions. Because it didn’t work with your instructions.

Used another source. From another manual, everything started the first time.

I don’t know why you didn’t make a complete instruction with a working example. Everything is somehow not finished to the end.

I will then publish here the full instructions on how to run your application with all the commands.

[collex100]

I have a lot of questions about your wonderful product. In my assortment, your application occupies the number 1 position.

Because in our human civilization, the first was task management. Tasks are water. Tasks originate from water. And water is life on earth.
This is an introduction and good words about your product.

As for the forum. The forum is good, but I always don’t like the initial conditions on such forums.

It is impossible to write a topic for a beginner, and there are few open topics at the start and, frankly, everyone is far from pressing topics.Now about the pressing topics.

1. Why do the containers in this manual lift themselves automatically:
   Deploying a self-hosted Penpot Instance using the Docker InstantApp

and your installation,

Taiga 30min Setup

This is the easiest and **recommended** way to run Taiga in production. This document explains how to deploy a full Taiga service for a production environment with **docker**. If you’re already using taiga-docker, follow this migration guide to use the new .env based deployment. Note: You can access the older docker installation guide for documentation purposes, intended just for earlier versions of Taiga (prior to ver. 6.6.0) Requirements Prior to start the installation, ensure you hav…

all containers need to be understood one by one. How do I make the containers automatically start themselves?

2. How to update the configuration? If, for example, SMTP has changed?

3. How to make everything run through compose, not a script, and what is the difference?

4. Is there an example of saving backups on a third-party server in Minio?

These are not all questions. To get an answer for something.
Thanks!

[collex100]

A strange answer, everything about installing Taiga is packaged in Docker, and you honestly have a manual for installing Docker Taiga is not very good.
It is difficult and long to fully install according to your information, and this issue is not disclosed to you in principle.
Although this is a VERY IMPORTANT point! And for some reason you are avoiding this issue! It’s strange!

чт, 1 июн. 2023 г. в 08:48, Yamila Moreno via Taiga Community <notifications@taiga.discoursemail.com>: