{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicwipa56eogl2lajtxko2wacu46iuoffl2xwkgcqah65iihsyv3pa",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3miw2x27iofu2"
  },
  "path": "/t/outbound-connection-dns-error-n8n-space-failing-to-reach-external-apis-facebook-telegram/175045#post_1",
  "publishedAt": "2026-04-07T11:33:20.000Z",
  "site": "https://discuss.huggingface.co",
  "tags": [
    "N8n - a Hugging Face Space by yking21"
  ],
  "textContent": "Hi everyone,\n\nI am running an automated workflow instance (n8n) using a Docker container inside a Hugging Face Space. The deployment itself works perfectly, but I am facing a persistent issue when the workflow tries to make outbound HTTP requests to specific external APIs, namely the **Facebook Graph API** (`graph.facebook.com`) and the **Telegram API** (`api.telegram.org`).\n\nWhenever the workflow triggers these nodes, I receive the following error:\n\n> _“Couldn’t connect with these settings. The connection cannot be established, this usually occurs due to an incorrect host (domain) value.”_\n\n**What I suspect:** This behavior strongly points to either a DNS resolution failure inside the Space container or a firewall/network policy blocking outbound traffic to these specific domains.\n\n**My questions to the community/staff:**\n\n  1. Are there known outbound network restrictions or blocked domains on Hugging Face Spaces (specifically for social media APIs)?\n\n  2. If this is a DNS issue, is there a recommended way to force custom DNS settings (e.g., `8.8.8.8`) within the Space’s configuration or Dockerfile?\n\n\n\n\n**Space URL:** N8n - a Hugging Face Space by yking21\n\nHas anyone experienced this while running n8n or similar automation tools on Spaces? Any insights or workarounds would be highly appreciated!\n\nThanks in advance.",
  "title": "[Outbound Connection/DNS Error] n8n Space failing to reach external APIs (Facebook/Telegram)"
}