# Problems upgrading to 6.6.0

**URL:** <https://community.taiga.io/t/problems-upgrading-to-6-6-0/1299>\
**Category:** Self hosted Taiga\
**Tags:** docker\
**Created:** [May 30, 2023, 2:28pm UTC](https://community.taiga.io/t/problems-upgrading-to-6-6-0/1299 "2023-05-30T14:28:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![viamonster](https://avatars.discourse-cdn.com/v4/letter/v/7993a0/32.png) [@viamonster](https://community.taiga.io/u/viamonster)\
**Post date:** [May 30, 2023, 2:28pm UTC](https://community.taiga.io/t/problems-upgrading-to-6-6-0/1299/1 "2023-05-30T14:28:09Z")

</div>

I tried to upgrade to the new 6.6.0 from the previous version following themigration article ([Migrate to new docker settings (v 6.6.0+)](https://docs.taiga.io/upgrades-docker-migrate.html)) but ran into several problems.

Once I put all the info in the .env and ran docker-compose, I got this error message:

```auto
ERROR: The Compose file './docker-compose.yml' is invalid because:
services.taiga-back.depends_on contains an invalid type, it should be an array

```

Which is kind of astonishing as this is the file I got from git.  
So I just tried and put all the `depends on` things in comments. The containers go up then, but the frontend looks … a bit minimal:

![taiga_front](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/2X/3/34f275f28618e7714353fa8fc22b8f16a68e7d2a.png)

The browser console show me two errors:

1. … /styles/theme-taiga.css couldn’t be loaded because the MIME-Typ is “text/html” and not “text/css”
2. Uncaught SyntaxError: expected expression, got ‘\<’ on app-loader.js line 1

Furthermore, if I run docker-compose up without the -d, I get a wall of fast scrolling errors from rabbitmq:

```auto
taiga-async-rabbitmq_1 | 2023-05-26 04:16:39.336 [error] <0.5808.8> **Connection attempt from node 'rabbitmqcli-217-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply.**
taiga-async-rabbitmq_1 | 2023-05-26 04:16:43.987 [error] <0.5818.8> **Connection attempt from node 'rabbitmqcli-66-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply.**
taiga-async-rabbitmq_1 | 2023-05-26 04:16:48.694 [error] <0.5829.8> **Connection attempt from node 'rabbitmqcli-985-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply.**
taiga-async-rabbitmq_1 | 2023-05-26 04:16:53.499 [error] <0.5839.8> **Connection attempt from node 'rabbitmqcli-203-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply.**
taiga-async-rabbitmq_1 | 2023-05-26 04:16:58.219 [error] <0.5849.8> **Connection attempt from node 'rabbitmqcli-159-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply.**
taiga-async-rabbitmq_1 | 2023-05-26 04:17:02.899 [error] <0.5860.8> **Connection attempt from node 'rabbitmqcli-7-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply.**
taiga-async-rabbitmq_1 | 2023-05-26 04:17:07.454 [error] <0.5870.8> **Connection attempt from node 'rabbitmqcli-128-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply.**
taiga-async-rabbitmq_1 | 2023-05-26 04:17:12.226 [error] <0.5882.8> **Connection attempt from node 'rabbitmqcli-736-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply.**
taiga-async-rabbitmq_1 | 2023-05-26 04:17:16.973 [error] <0.5892.8> **Connection attempt from node 'rabbitmqcli-151-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply.**
taiga-async-rabbitmq_1 | 2023-05-26 04:17:21.550 [error] <0.5903.8> **Connection attempt from node 'rabbitmqcli-829-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply.**
taiga-async-rabbitmq_1 | 2023-05-26 04:17:26.191 [error] <0.5913.8> **Connection attempt from node 'rabbitmqcli-550-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply.**
taiga-async-rabbitmq_1 | 2023-05-26 04:17:30.885 [error] <0.5923.8> **Connection attempt from node 'rabbitmqcli-757-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply.**
taiga-async-rabbitmq_1 | 2023-05-26 04:17:35.632 [error] <0.5934.8> **Connection attempt from node 'rabbitmqcli-294-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply.**
taiga-async-rabbitmq_1 | 2023-05-26 04:17:40.287 [error] <0.5944.8> **Connection attempt from node 'rabbitmqcli-603-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply.**
taiga-async-rabbitmq_1 | 2023-05-26 04:17:44.864 [error] <0.5955.8> **Connection attempt from node 'rabbitmqcli-713-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply.**
taiga-events-rabbitmq_1 | 2023-05-26 04:27:19.929 [error] <0.7244.8> **Connection attempt from node 'rabbitmqcli-615-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply.**
taiga-events-rabbitmq_1 | 2023-05-26 04:27:24.398 [error] <0.7254.8> **Connection attempt from node 'rabbitmqcli-556-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply.**
taiga-events-rabbitmq_1 | 2023-05-26 04:27:29.391 [error] <0.7265.8> **Connection attempt from node 'rabbitmqcli-809-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply.**
taiga-events-rabbitmq_1 | 2023-05-26 04:27:34.476 [error] <0.7276.8> **Connection attempt from node 'rabbitmqcli-109-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply.**
taiga-events-rabbitmq_1 | 2023-05-26 04:27:39.085 [error] <0.7287.8> **Connection attempt from node 'rabbitmqcli-6-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply.**
taiga-events-rabbitmq_1 | 2023-05-26 04:27:43.454 [error] <0.7297.8> **Connection attempt from node 'rabbitmqcli-869-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply.**
taiga-events-rabbitmq_1 | 2023-05-26 04:27:48.176 [error] <0.7307.8> **Connection attempt from node 'rabbitmqcli-699-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply.**

```

Anyone got any idea how to solve all of this?

Team and management just warmed up to Taiga, so this is very unfortunate. Especially management is not very patient and will likely force us to go back to our previous, inferior tool if this situation goes on too long :-/

Context: I downloaded the new version via `git fetch && git reset --hard origin/main`, filled in my configuration information and ran `docker-compose up -d` as per the guide. My docker version is 20.10.5+dfsg1, build 55c4c88, this is on debian.

---

<div class="post-metadata">

**Author:** ![tdelatorre](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/tdelatorre/32/519_2.png) [@tdelatorre](https://community.taiga.io/u/tdelatorre)\
**Post date:** [June 1, 2023, 10:33am UTC](https://community.taiga.io/t/problems-upgrading-to-6-6-0/1299/2 "2023-06-01T10:33:38Z")

</div>

Hi @viamonster. Welcome to our community!

If you have followed the steps in [the migration article](https://docs.taiga.io/upgrades-docker-migrate.html) in detail, let’s start from the error:

```auto
ERROR: The Compose file './docker-compose.yml' is invalid because:
services.taiga-back.depends_on contains an invalid type, it should be an array

```

In order to help you, we need:

- check the logs `docker logs -f` to see if there is more information.
- your docker-compose.yml and docker-compose-inits.yml (redacted without sensitive data)

Regards.
