Page locked

This page is currently locked for editing by another user. You have to wait until this user finishes editing or the lock expires.

Currently locked by: 216.73.217.89
Lock expires at: 2026/06/12 01:49 (12 min)

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== Taiga ======
Taiga is an project management tool.
[[https://taiga.io/|Website]]
[[https://docs.taiga.io/|Documentation]]

===== Relevant Information =====

==== Taiga Location ====
You can find the Taiga relevant files in:
  /var/www/vhosts/ct-lab.info/taiga.ct-lab.info/taiga-docker/

==== Accessing the API ====
[[https://taiga.ct-lab.info/api/v1/|https://taiga.ct-lab.info/api/v1/]]
[[https://docs.taiga.io/#api|API documentation]]

==== Backups ====
Taiga is getting backupped every Monday at 04:00 AM via cron jobs.
It will execute the script in:
  /var/www/vhosts/ct-lab.info/taiga.ct-lab.info/taiga-docker/taiga-backup.sh
The backup files are located under the following folder:
  /var/www/vhosts/ct-lab.info/taiga.ct-lab.info/taiga-docker/taiga-backup/
[[https://docs.taiga.io/#_backup_and_restore_taiga|Documentation for backing up / restoring]]

===== Troubleshooting =====

==== Taiga is unreachable ====
Start Taiga manually by entering the following in the SSH terminal:
<code>
cd ~/docker/taiga-docker/
// taiga only
./launch-taiga
// taiga + penpot
./launch-all.sh
</code>

==== Taiga only displays old stories ====
The server was probably restarted and docker.socket didn't restart correctly.

To fix this, enter the following in the SSH terminal:
<code>
cd ~/docker/taiga-docker/
docker compose stop
sudo systemctl stop docker
// you will probably get the warning: Warning: Stopping docker.service, but it can still be activated by: docker.socket
sudo systemctl stop docker.socket
sudo systemctl start docker
</code>
If you get the following error:
{{:intern:error_gateway_failed.png |}}
<code>
cd ~/docker/taiga-docker/
docker compose stop
sudo systemctl stop docker
// you will probably get the warning: Warning: Stopping docker.service, but it can still be activated by: docker.socket
sudo systemctl stop docker.socket
sudo lsof -i:9000
// example output:
// COMMAND       PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
// docker-pr 2030447 root    4u  IPv4 9450363      0t0  TCP *:9000 (LISTEN)
// docker-pr 2030464 root    4u  IPv6 9450370      0t0  TCP *:9000 (LISTEN)
kill {pid}
// in this case: kill 2030447
// in this case: kill 2030464
sudo systemctl start docker
</code>