# Taiga it's not work **URL:** \ **Category:** Self hosted Taiga\ **Tags:** docker\ **Created:** [April 26, 2023, 4:18am UTC](https://community.taiga.io/t/taiga-its-not-work/1096 "2023-04-26T04:18:12Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![zavgleb](https://avatars.discourse-cdn.com/v4/letter/z/d26b3c/32.png) [@zavgleb](https://community.taiga.io/u/zavgleb)\ **Post date:** [April 26, 2023, 4:18am UTC](https://community.taiga.io/t/taiga-its-not-work/1096/1 "2023-04-26T04:18:12Z")
i download git clone [GitHub - taigaio/taiga-docker](https://github.com/kaleidos-ventures/taiga-docker) End start all instruction. ./launch-all.sh # Taiga Something happened and the Taiga has captured the error to be able to work on it. [Take me home](http://10.0.2.73:9000/) use taiga-docker i dont whera logs ☹ help plz ---
**Author:** ![daniel.herrero](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/daniel.herrero/32/301_2.png) [@daniel.herrero](https://community.taiga.io/u/daniel.herrero)\ **Post date:** [April 26, 2023, 9:14am UTC](https://community.taiga.io/t/taiga-its-not-work/1096/2 "2023-04-26T09:14:24Z")
> [@zavgleb](#): > > the Taiga has captured the error to be able to work on it. Hi @zavgleb, and welcome to the community! According to the link you provide in your “Take me home”, you’re serving Taiga in the 10.0.2.73 address. What is your exact infrastructure?. Apart from this, we would need more details to give a proper answer. For example: - What are your `.env` file settings? - What’s the status of the containers after running the `./launch-taiga.sh` command. You can get this info executing `docker ps `. - What are the service logs?. You can have this data starting Taiga with `docker compose up` directly, or with `docker compose logs`. - Do you have a proxy? What’s your configuration? If it’s nginx, it should be under `/etc/nginx/conf.d/default.conf` - Any interesting logs or error in the browser’s console or network requests? You can open Chrome DevTools by pressing F12 and checking the Console and Network tabs Thanks in advance ---
**Author:** ![zavgleb](https://avatars.discourse-cdn.com/v4/letter/z/d26b3c/32.png) [@zavgleb](https://community.taiga.io/u/zavgleb)\ **Post date:** [April 26, 2023, 7:24pm UTC](https://community.taiga.io/t/taiga-its-not-work/1096/3 "2023-04-26T19:24:36Z")
okay i done, thx. But now next problem ☹ \>( i used lan link [taiga.mycompany.com](http://taiga.mycompany.com) end show me #### Oops, something went wrong… According to the Taiga, your username/email or password are incorrect. What used login end password? ---
**Author:** ![daniel.herrero](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/daniel.herrero/32/301_2.png) [@daniel.herrero](https://community.taiga.io/u/daniel.herrero)\ **Post date:** [April 27, 2023, 9:13am UTC](https://community.taiga.io/t/taiga-its-not-work/1096/4 "2023-04-27T09:13:38Z")
Hi @zavgleb If you have follow the guide “Taiga 30 min setup”, one of the steps is the super user creation, with the command ```shell ./taiga-manage.sh createsuperuser ``` In that step you define her username/password, and it’s by all means a valid user log in into Taiga. By default it’s not enabled the public registration, but could also allow users to create their own accounts by following what’s described [in the guide](https://community.taiga.io/t/taiga-30min-setup/170#public-registration-16) You should introduce the following in the docker-compose.yml: ```yaml version: "3.5" x-environment: &default-back-environment PUBLIC_REGISTER_ENABLED: "True" ... ... taiga-front: image: taigaio/taiga-front:latest environment: PUBLIC_REGISTER_ENABLED: "true" ``` Just by restarting Taiga you should be able to create new user clicking on the “create your free account here” link. ![image](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/1X/2701c2dfea87c1f8001cfc9ee78b54d1f6b78b91.png) ---
**Author:** ![daniel.herrero](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/daniel.herrero/32/301_2.png) [@daniel.herrero](https://community.taiga.io/u/daniel.herrero)\ **Post date:** [April 28, 2023, 7:11am UTC](https://community.taiga.io/t/taiga-its-not-work/1096/6 "2023-04-28T07:11:28Z")
Hi @zavgleb, Don’t worry for your hidden messages, I have a copy. To avoid this in the future, please try not to share your passwords publicly (although it were fake or testing ones). And regarding to your problem, with your console logs it seems there’s a communication problem between taiga-front and taiga-back, according to the 404 responses when requesting the api/v1 urls: `GET http:///api/v1/stats` `GET http:///api/v1/discover/...` … and also the login request… `POST http:///api/v1/auth` As you mentioned you where running a source-code installation, could you please post here your configuration for taiga-back and taiga-front, specially for these variables?: `~/taiga-back/settings/config.py` ```auto TAIGA_SITES_SCHEME = "http" TAIGA_SITES_DOMAIN = "taiga.mycompany.com" FORCE_SCRIPT_NAME = "" ``` ` ~/taiga-front-dist/dist/conf.json` ```auto { "api": "http://taiga.mycompany.com/api/v1/", "eventsUrl": "wss://taiga.mycompany.com/events", "baseHref": "/", ``` The front-end api variable should match the URL where taiga-back is listening. Other thing to discard a back-end problem and verify its url, it’s to start it with `~/taiga-back [stable] $ DJANGO_SETTINGS_MODULE=settings.config python manage.py runserver` and try to access [http://taiga.mycompany.com/api/v1/](http://taiga.mycompany.com/api/v1/) You should see something like the json shown in the image ![image](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/1X/adf4284d4c2e1fc6cffbab487a33a5768cfea361.png) ---
**Author:** ![zavglebz](https://avatars.discourse-cdn.com/v4/letter/z/4bbf92/32.png) [@zavglebz](https://community.taiga.io/u/zavglebz)\ **Post date:** [April 28, 2023, 9:19am UTC](https://community.taiga.io/t/taiga-its-not-work/1096/7 "2023-04-28T09:19:23Z")
As you mentioned you where running a source-code installation, could you please post here your configuration for taiga-back and taiga-front, specially for these variables?: `~/taiga-back/settings/config.py` my code > TAIGA\_SITES\_SCHEME = “http” > TAIGA\_SITES\_DOMAIN = “[taiga.link.com](http://taiga.link.com)” > FORCE\_SCRIPT\_NAME = “/taiga” ~/taiga-front-dist/dist/conf.json my code “api”: “[http://taiga.link.com/api/v1/](http://taiga.link.com/api/v1/)”, “eventsUrl”: “wss://taiga.link.com/events”, “baseHref”: “/taiga/”, DJANGO\_SETTINGS\_MODULE=settings.config python manage.py runserver ![1](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/1X/4f9da6449254e48e3b5bbea3f7441da255b2392b.jpeg) ---
**Author:** ![zavglebz](https://avatars.discourse-cdn.com/v4/letter/z/4bbf92/32.png) [@zavglebz](https://community.taiga.io/u/zavglebz)\ **Post date:** [April 28, 2023, 9:19am UTC](https://community.taiga.io/t/taiga-its-not-work/1096/8 "2023-04-28T09:19:54Z")
![2](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/1X/2bf7b865da72cb0588bb18da5009f621b361349f.jpeg) ---
**Author:** ![zavglebz](https://avatars.discourse-cdn.com/v4/letter/z/4bbf92/32.png) [@zavglebz](https://community.taiga.io/u/zavglebz)\ **Post date:** [April 28, 2023, 9:20am UTC](https://community.taiga.io/t/taiga-its-not-work/1096/9 "2023-04-28T09:20:47Z")
![3](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/1X/6cf7d29da6ca6c1a277c479905817016bcf2937a.jpeg) ---
**Author:** ![daniel.herrero](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/daniel.herrero/32/301_2.png) [@daniel.herrero](https://community.taiga.io/u/daniel.herrero)\ **Post date:** [May 3, 2023, 10:22am UTC](https://community.taiga.io/t/taiga-its-not-work/1096/10 "2023-05-03T10:22:54Z")
Hi @zavglebz, With the configuration you provided, Taiga is being served following a subpath approach in the following URLs : - **taiga-back** : [http://taiga.link.com/taiga/api/v1/](http://taiga.link.com/taiga/api/v1/) (API) - **taiga-front** [http://taiga.link.com/taiga](http://taiga.link.com/taiga) (Taiga’s main page) It seems that your taiga-front configuration may be wong, as it’s missing the “ **/taiga** ” subpath to form the url where taiga-back (the API) is listening. Try to change your `~/taiga-front-dist/dist/conf.json` to this: > “api”: “[http://taiga.link.com/taiga/api/v1/”](http://taiga.link.com/taiga/api/v1/%E2%80%9D), > “eventsUrl”: “wss://taiga.link.com/taiga/events”, > “baseHref”: “/taiga/”, > } You can have more details about “subdomain” vs “subpaths” settings in the [documentation](https://docs.taiga.io/setup-production.html#taiga-front).