{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicrfc5gs4qjt5tt3y6t6oryyyresg4udl422fijwo56akq52gs2ky",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mowe4uw2jfv2"
  },
  "path": "/t/gradio-web-components-failing-to-load/177067#post_2",
  "publishedAt": "2026-06-23T00:42:40.000Z",
  "site": "https://discuss.huggingface.co",
  "tags": [
    "gradio-app/gradio#12570 — 404 Bad Request using Hugging Face Spaces API",
    "(click for more details)"
  ],
  "textContent": "Hmm… this could still be a transient glitch, but I wonder if the repository name itself may be part of the trigger:\n\n* * *\n\nThis looks less like a problem inside the Space app itself and more like a failure in the Gradio web component’s **Space lookup/status path**.\n\nThe main clue is that the failing request is:\n\n\n    https://huggingface.co/api/spaces/by-subdomain/<space-subdomain>\n\n\nand the error is:\n\n\n    {\"error\":\"Invalid repo name: name/of_app - repo name includes an url-encoded slash\"}\n\n\nSo, as a quick workaround / diagnostic, I would try the explicit Space repo-id form instead of the `.hf.space` URL form:\n\n\n    <gradio-app space=\"<owner>/<space_name>\"></gradio-app>\n\n\ninstead of:\n\n\n    <gradio-app src=\"https://<space-subdomain>.hf.space\"></gradio-app>\n\n\nIf `space=\"<owner>/<space_name>\"` works while `src=\"https://<space-subdomain>.hf.space\"` fails, that would strongly suggest that the app itself is fine and the failure is specifically in the `.hf.space` subdomain → Space repo lookup path.\n\nA very similar issue is here:\n\n  * gradio-app/gradio#12570 — 404 Bad Request using Hugging Face Spaces API\n\n\n\nIn that issue, the failing request is:\n\n\n    GET https://huggingface.co/api/spaces/by-subdomain/jglowa-ai-gov-pl\n\n\nand the response is:\n\n\n    {\"error\":\"Invalid repo name: jglowa/ai-gov.pl - repo name includes an url-encoded slash\"}\n\n\nThat looks very close to the error pattern here.\n\nWhy the repository name may matter (click for more details) Why `space=` is a useful test (click for more details) Suggested tests (click for more details) Related background issues (click for more details) Useful report format (click for more details)\n\nShort version: this may still be a transient platform-side issue, but the specific console error points to the Gradio web component’s `by-subdomain` metadata/status lookup. Testing `space=\"<owner>/<space_name>\"` instead of `src=\"https://<space-subdomain>.hf.space\"` should help separate an app/runtime problem from a subdomain lookup problem.",
  "title": "Gradio web components failing to load"
}