{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiactuwhgffporrdubh4n5zzv63stqdpyqwx2k7ujuzofc7dyumibu",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mowktkkigey2"
  },
  "path": "/t/gradio-web-components-failing-to-load/177067#post_4",
  "publishedAt": "2026-06-23T04:21:05.000Z",
  "site": "https://discuss.huggingface.co",
  "tags": [
    "something beyond just Gradio itself",
    "(click for more details)"
  ],
  "textContent": "Thanks. I see. If it happens with that method too, this may connect to something beyond just Gradio itself:\n\n* * *\n\nThe `https://.hf.space/config` part changes the picture quite a bit.\n\nMy previous guess was narrower:\n\n\n    src=\"https://<space-subdomain>.hf.space\"\n      → possibly failing through the by-subdomain lookup path\n\n\nBut if this also happens with:\n\n\n    <gradio-app space=\"<owner>/<space_name>\"></gradio-app>\n\n\nand the component repeatedly tries to fetch:\n\n\n    https://.hf.space/config\n\n\nthen this looks broader than only a `by-subdomain` reverse-lookup problem.\n\nA literal empty-host URL like this:\n\n\n    https://.hf.space/config\n\n\nsuggests that the web component, or the Hugging Face Space metadata/config resolution path behind it, failed to resolve a valid `.hf.space` host at all.\n\nSo I would update the working hypothesis to something like this:\n\n\n    src=\"https://<space-subdomain>.hf.space\"\n      → may fail through by-subdomain lookup\n\n    space=\"<owner>/<space_name>\"\n      → may fail through owner/name → resolved Space host/config lookup\n\n    common layer:\n      browser-facing Space identity/config resolution path\n\n\nThat is hard to explain as a bug inside the user Space runtime itself.\n\nIf the generated URL is literally:\n\n\n    https://.hf.space/config\n\n\nthen the missing value is probably the resolved Space subdomain / host, not something inside the Gradio app running in the Space.\n\nWhy this seems broader than the original repo-name hypothesis (click for more details) Why this may connect to the Spaces proxy / CORS thread (click for more details) Checks that may narrow it down (click for more details)\n\nShort version: your `space=\"<owner>/<space_name>\"` result makes this look less like only a repo-name-specific `by-subdomain` issue and more like a broader browser-facing Spaces integration problem.\n\nEspecially if the web component literally requests:\n\n\n    https://.hf.space/config\n\n\nthen something upstream failed to resolve the Space host before the request even reached the user app.",
  "title": "Gradio web components failing to load"
}