# Cannot open the Content bank Tile

**URL:** <https://forum.community.taotesting.com/t/cannot-open-the-content-bank-tile/104>\
**Category:** Support\
**Created:** [March 13, 2026, 11:36am UTC](https://forum.community.taotesting.com/t/cannot-open-the-content-bank-tile/104 "2026-03-13T11:36:06Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![frank\_jon](https://avatars.discourse-cdn.com/v4/letter/f/c89c15/32.png) [@frank\_jon](https://forum.community.taotesting.com/u/frank_jon)\
**Post date:** [March 13, 2026, 11:36am UTC](https://forum.community.taotesting.com/t/cannot-open-the-content-bank-tile/104/1 "2026-03-13T11:36:06Z")

</div>

Have setup a fresh installation of the TAO CE by following the installation guide and everything else works fine. When i click on the Content bank to create an assessment, it starts with a URL of [https://community.tao.internal/portal/content-bank](https://community.tao.internal/portal/content-bank) and then redirects automatically to [https://community.tao.internal/backoffice/taoLti/AuthoringTool/launch](https://community.tao.internal/backoffice/taoLti/AuthoringTool/launch) with a blank page. Any help with this issue would be highly appreciated.

---

<div class="post-metadata">

**Author:** ![frank\_jon](https://avatars.discourse-cdn.com/v4/letter/f/c89c15/32.png) [@frank\_jon](https://forum.community.taotesting.com/u/frank_jon)\
**Post date:** [March 16, 2026, 2:17am UTC](https://forum.community.taotesting.com/t/cannot-open-the-content-bank-tile/104/2 "2026-03-16T02:17:56Z")

</div>

I couldn’t check the URL over the weekend, I tried recreating the containers and now this time on clicking upon the Content Bank tile, I get a HTTP Error 502

---

<div class="post-metadata">

**Author:** ![Dave\_Leach](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.community.taotesting.com/dave_leach/32/108_2.png) [@Dave\_Leach](https://forum.community.taotesting.com/u/Dave_Leach)\
**Post date:** [March 16, 2026, 12:06pm UTC](https://forum.community.taotesting.com/t/cannot-open-the-content-bank-tile/104/3 "2026-03-16T12:06:48Z")

</div>

Getting the same problem here. I am on Ubuntu 24.04.3. Is the redirect to ‘backoffice’ correct?

---

<div class="post-metadata">

**Author:** ![Cicatrice](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.community.taotesting.com/cicatrice/32/31_2.png) [@Cicatrice](https://forum.community.taotesting.com/u/Cicatrice)\
**Post date:** [March 16, 2026, 1:36pm UTC](https://forum.community.taotesting.com/t/cannot-open-the-content-bank-tile/104/4 "2026-03-16T13:36:17Z")

</div>

Hi ! thanks for contacting us.

It may be due to a race condition during installation (we are already investigating it).

Can you try to wipe all volumes and containers related to `tao-ce`, then try to reinstall it?

> **[Reinstallation - Using Docker Compose - TAO Community Edition](https://tao-ce.github.io/tao-ce/start/install/container/docker-compose/#reinstallation)**
>
> About this guide

Many thanks!

---

<div class="post-metadata">

**Author:** ![Dave\_Leach](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.community.taotesting.com/dave_leach/32/108_2.png) [@Dave\_Leach](https://forum.community.taotesting.com/u/Dave_Leach)\
**Post date:** [March 16, 2026, 2:55pm UTC](https://forum.community.taotesting.com/t/cannot-open-the-content-bank-tile/104/5 "2026-03-16T14:55:54Z")

</div>

I ran `docker compose -f docker-compose.tao-ce.yaml down -v` and then `docker compose -f docker-compose.tao-ce.yaml up -d`. Sadly, the same issue is there when clicking the Content bank tile: Error code: 502 Bad Gateway.

Is there a debug log that I can provide to help?

---

<div class="post-metadata">

**Author:** ![frank\_jon](https://avatars.discourse-cdn.com/v4/letter/f/c89c15/32.png) [@frank\_jon](https://forum.community.taotesting.com/u/frank_jon)\
**Post date:** [March 17, 2026, 3:57am UTC](https://forum.community.taotesting.com/t/cannot-open-the-content-bank-tile/104/6 "2026-03-17T03:57:14Z")

</div>

I concur with Dave. Facing the same issue across multiple fresh deployments and also when I try the re-installation.

---

<div class="post-metadata">

**Author:** ![mindaugasNSA](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@mindaugasNSA](https://forum.community.taotesting.com/u/mindaugasNSA)\
**Post date:** [March 17, 2026, 2:19pm UTC](https://forum.community.taotesting.com/t/cannot-open-the-content-bank-tile/104/7 "2026-03-17T14:19:32Z")

</div>

The same issue. Problems with URL generation using environment file parameters.

---

<div class="post-metadata">

**Author:** ![Dave\_Leach](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.community.taotesting.com/dave_leach/32/108_2.png) [@Dave\_Leach](https://forum.community.taotesting.com/u/Dave_Leach)\
**Post date:** [March 18, 2026, 8:47am UTC](https://forum.community.taotesting.com/t/cannot-open-the-content-bank-tile/104/8 "2026-03-18T08:47:24Z")

</div>

Is there another way to open the item writing function without going through the portal and using the Content Tile?

---

<div class="post-metadata">

**Author:** ![jtaylor](https://avatars.discourse-cdn.com/v4/letter/j/e79b87/32.png) [@jtaylor](https://forum.community.taotesting.com/u/jtaylor)\
**Post date:** [April 9, 2026, 12:13pm UTC](https://forum.community.taotesting.com/t/cannot-open-the-content-bank-tile/104/9 "2026-04-09T12:13:32Z")

</div>

I am having the same issue. Agree with mindaugasNSA. It seems the backend variables are not present resulting in a 502. I followed the steps and have tried completely removing and reloading the containers and volumes.

---

<div class="post-metadata">

**Author:** ![Patrick](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.community.taotesting.com/patrick/32/60_2.png) [@Patrick](https://forum.community.taotesting.com/u/Patrick)\
**Post date:** [April 22, 2026, 8:25am UTC](https://forum.community.taotesting.com/t/cannot-open-the-content-bank-tile/104/10 "2026-04-22T08:25:25Z")

</div>

Hi, thank you for your feedbacks, we do have a race condition to launch the authoring tool depending a bit on the hardware, the good news is that Geoffrey already implemented a fix into the new release we intend to launch in August
