# Docker Spaces returning {"data":\[\]} – proxy not forwarding requests to container (all spaces affected)

**URL:** <https://discuss.huggingface.co/t/docker-spaces-returning-data-proxy-not-forwarding-requests-to-container-all-spaces-affected/175500>\
**Category:** Spaces\
**Created:** [April 23, 2026, 8:04pm UTC](https://discuss.huggingface.co/t/docker-spaces-returning-data-proxy-not-forwarding-requests-to-container-all-spaces-affected/175500 "2026-04-23T20:04:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rajvivan](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/rajvivan/32/59755_2.png) [@rajvivan](https://discuss.huggingface.co/u/rajvivan)\
**Post date:** [April 23, 2026, 8:04pm UTC](https://discuss.huggingface.co/t/docker-spaces-returning-data-proxy-not-forwarding-requests-to-container-all-spaces-affected/175500/1 "2026-04-23T20:04:00Z")

</div>

## Issue

All of my Docker Spaces are returning `{"data":[]}` with the “Pretty-print” viewer instead of rendering the actual app. This affects all 3 of my spaces:

- [ML Sentiment Analysis Social Media - a Hugging Face Space by rajvivan](https://huggingface.co/spaces/rajvivan/ML-Sentiment-Analysis-Social-Media)
- [CUD Traffic AI - a Hugging Face Space by rajvivan](https://huggingface.co/spaces/rajvivan/CUD-Traffic-AI)

## Symptoms

- All spaces show `{"data":[]}` with “Pretty-print” checkbox at the top
- This happens on both the HF Space viewer AND the direct `.hf.space` subdomain URLs
- Container logs confirm the app starts successfully: `Application startup complete. Uvicorn running on http://0.0.0.0:7860`
- **CRITICAL: The container logs show ZERO incoming HTTP requests** — the HF proxy is not forwarding any traffic to the container
- All spaces use `sdk: docker` with `app_port: 7860`

## What I’ve tried

- Logged out and back in
- Restarted all 3 spaces
- Checked from different browser sessions

## Expected behavior

The React + FastAPI apps should be served normally. The containers are running fine but HF’s reverse proxy is not routing requests to them.

Please investigate the proxy routing for user `rajvivan`. This appears to be an account-level infrastructure issue.

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [April 24, 2026, 1:39am UTC](https://discuss.huggingface.co/t/docker-spaces-returning-data-proxy-not-forwarding-requests-to-container-all-spaces-affected/175500/2 "2026-04-24T01:39:35Z")

</div>

Seems resolved by themselves now…?

---

<div class="post-metadata">

**Author:** ![rajvivan](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/rajvivan/32/59755_2.png) [@rajvivan](https://discuss.huggingface.co/u/rajvivan)\
**Post date:** [April 24, 2026, 5:47am UTC](https://discuss.huggingface.co/t/docker-spaces-returning-data-proxy-not-forwarding-requests-to-container-all-spaces-affected/175500/3 "2026-04-24T05:47:28Z")

</div>

Unfortunately it is not working. I am still seeing the the issue. None of the spaces are working .  
I am seeing issues for other spaces as well

> **[ML Intern - a Hugging Face Space by smolagents](https://huggingface.co/spaces/smolagents/ml-intern)**
>
> This web app lets you type questions or requests about machine‑learning topics and receive helpful, plain‑language replies. Just enter your query in the chat box and the assistant will respond with...

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [April 24, 2026, 10:11am UTC](https://discuss.huggingface.co/t/docker-spaces-returning-data-proxy-not-forwarding-requests-to-container-all-spaces-affected/175500/4 "2026-04-24T10:11:06Z")

</div>

Hmm… If the issue is related to your Hugging Face account, your only option is to contact them via email… [website@huggingface.co](mailto:website@huggingface.co)

If you want to determine whether it’s purely an account issue, the best way is to compare how it behaves with a different account…  
For example, [if you duplicate this, does it not work in your namespace?](https://huggingface.co/spaces/John6666/docker_routing_test)