# WebSocket error: \[object Event\]

**URL:** <https://community.taiga.io/t/websocket-error-object-event/5317>\
**Category:** Self hosted Taiga\
**Tags:** issues, docker\
**Created:** [February 14, 2025, 11:59am UTC](https://community.taiga.io/t/websocket-error-object-event/5317 "2025-02-14T11:59:27Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![csmu](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/csmu/32/2289_2.png) [@csmu](https://community.taiga.io/u/csmu)\
**Post date:** [March 8, 2025, 4:01am UTC](https://community.taiga.io/t/websocket-error-object-event/5317/2 "2025-03-08T04:01:05Z")

</div>

I had pretty much the same issue. The websockets could not communicate with nginx. It was trying to communicate with localhost.

This is what I did to resolve the issue on my server.

> [@New Taiga, reverse proxying with HTTPS using Caddy](https://community.taiga.io/t/new-taiga-reverse-proxying-with-https-using-caddy/5615/3):
>
> Sorry for the delay in responding. I don’t use Caddy but it looks to me like your setup is wrong.A proxy is supposed to sit in front of a server. I can’t see any external public facing directive to point to an internal service in your post. However, I had similar issues getting web sockets to work. The front end was try to access an internal service - it never reached the proxy. I added a volumes directive in taiga-front to make conf.json file accessible in the taiga-docker directory. In doc…

---

_[View the full topic](https://community.taiga.io/t/websocket-error-object-event/5317)._