# 502 Bad Gateway when accessing Hugging Face Chat

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2F502-bad-gateway-when-accessing-hugging-face-chat%2F160411%3E%5C
**Category:** Beginners\
**Created:** [June 23, 2025, 5:29pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2F502-bad-gateway-when-accessing-hugging-face-chat%2F160411 "2025-06-23T17:29:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andragel](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/andragel/32/32928_2.png) [@Andragel](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FAndragel)%5C
**Post date:** [June 23, 2025, 5:29pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2F502-bad-gateway-when-accessing-hugging-face-chat%2F160411%2F1 "2025-06-23T17:29:43Z")

</div>

I’ve been having this for a couple of weeks and can’t access the chat at all

---

<div class="post-metadata">

**Author:** ![meganariley](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/meganariley/32/56966_2.png) [@meganariley](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fmeganariley)%5C
**Post date:** [June 23, 2025, 5:54pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2F502-bad-gateway-when-accessing-hugging-face-chat%2F160411%2F2 "2025-06-23T17:54:52Z")

</div>

Hi @Andragel Can you please provide the name of the model you’re seeing this with?

---

<div class="post-metadata">

**Author:** ![meganariley](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/meganariley/32/56966_2.png) [@meganariley](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fmeganariley)%5C
**Post date:** [June 24, 2025, 4:01pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2F502-bad-gateway-when-accessing-hugging-face-chat%2F160411%2F3 "2025-06-24T16:01:00Z")

</div>

Hi! I wanted to provide a quick update that we’ve identified the issue and it’s now fixed. If you continue seeing any issues please be sure to let us know which model you’re seeing this with. Thanks again for reporting!