# Cannot view, edit or delete kanban cards: 400 Bad Request

**URL:** <https://community.taiga.io/t/cannot-view-edit-or-delete-kanban-cards-400-bad-request/2150>\
**Category:** Self hosted Taiga\
**Tags:** kanban, docker\
**Created:** [November 15, 2023, 1:47pm UTC](https://community.taiga.io/t/cannot-view-edit-or-delete-kanban-cards-400-bad-request/2150 "2023-11-15T13:47:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daerendor](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/daerendor/32/1383_2.png) [@Daerendor](https://community.taiga.io/u/Daerendor)\
**Post date:** [November 15, 2023, 1:47pm UTC](https://community.taiga.io/t/cannot-view-edit-or-delete-kanban-cards-400-bad-request/2150/1 "2023-11-15T13:47:18Z")

</div>

Hey,

I am trying to use Taiga Selfhosted (CE) Kanban feature.  
I get errors when I try to view, edit or delete cards in custom columns/tasks.

The issue I get is the following:

```auto
GET https://me.tld/api/v1/userstories/by_ref?project=1&status__is_archived=false
400 Bad Request

ref param is needed

```

I also get a second error:

```auto
GET https://me.tld/api/v1/userstories/by_ref?project=1&ref=2&status__is_archived=false
400 Internal Redirect

```

I suspect it might be related to a dual proxy situation (since I’m running Taiga with its default gateway behind nginx proxy).

Thank you for any explaination 🙂

Edit: running on taigaio/any:latest with default configuration apart from secrets and stuff.

---

<div class="post-metadata">

**Author:** ![yami](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/yami/32/289_2.png) [@yami](https://community.taiga.io/u/yami)\
**Post date:** [November 16, 2023, 9:24am UTC](https://community.taiga.io/t/cannot-view-edit-or-delete-kanban-cards-400-bad-request/2150/2 "2023-11-16T09:24:49Z")

</div>

Hi @Daerendor

I’m not sure what it happening in your environment:

- the first request is made using directly the API? or you have a way to reproduce the error using the UI?
- the second error, is made using the API? or you did change something to make the request have the `ref` param?
- do you have some docker logs that may help to understand the error?

The dual proxy situation is expected; it’s not the only way to serve Taiga and you may want your own configurations, but you should know about nginx, exposing ports in docker, etc.

Cheers!

---

<div class="post-metadata">

**Author:** ![Felipe\_Vera](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/felipe_vera/32/3237_2.png) [@Felipe\_Vera](https://community.taiga.io/u/Felipe_Vera)\
**Post date:** [October 25, 2024, 6:44pm UTC](https://community.taiga.io/t/cannot-view-edit-or-delete-kanban-cards-400-bad-request/2150/3 "2024-10-25T18:44:50Z")

</div>

Hi!

I had the same problem and I found the culprit. It was the addon ClearURLs that deleted the ref parameter. After disabling the addon (it doesn’t have whitelist ): ) I was able to use Taiga normally.

If anyone face the same problem and has the addon, disable it!

---

<div class="post-metadata">

**Author:** ![Toni](https://avatars.discourse-cdn.com/v4/letter/t/8797f3/32.png) [@Toni](https://community.taiga.io/u/Toni)\
**Post date:** [August 4, 2025, 1:36pm UTC](https://community.taiga.io/t/cannot-view-edit-or-delete-kanban-cards-400-bad-request/2150/4 "2025-08-04T13:36:21Z")

</div>

This should imho be part of the docs. I just found that I had the same problem, Taiga itself was all working fine.
