- Hugging Face Spaces' system DNS sinkholes these domains by returning a fake IP address instead of throwing ENOTFOUND.
- Because it returns a fake IP, the standard fallback logic in dns-fix.js was bypassed, causing n8n to connect to the sinkholed IP resulting in an ECONNRESET timeout after 60s.
- dns-fix.js now forces direct IP resolution via 1.1.1.1 DoH for these specific blocked hostnames before falling back to system DNS.
- HF Spaces blocks standard UDP DNS for some domains (like Telegram) by returning ENOTFOUND.
- The previous attempt forced DoH first via cloudflare-dns.com, but standard DNS resolution for cloudflare-dns.com itself failed inside HF Spaces, causing the entire DoH fallback to crash with ECONNRESET.
- Restored the original HuggingClaw logic: try system DNS first, and if it fails (ENOTFOUND), fallback to DoH using the direct IP '1.1.1.1' which bypasses system DNS entirely.
- Reverted README and DISCORD_PROXY_GUIDE.md since Telegram is NOT blocked by HF TLS/SNI and works natively once DNS is fixed.
fix: Telegram+Discord TLS/SNI bypass via Cloudflare Worker proxy
- Confirmed HF blocks Telegram via TLS/SNI inspection (60s timeout, ECONNRESET)
- Moved NODE_OPTIONS to Dockerfile ENV (after COPY) so dns-fix.js loads in n8n
- Added keep-alive=false patch to prevent stale socket ECONNRESET on Node 22
- Removed diagnostic code from dns-fix.js
- Updated README and guide to cover both Discord and Telegram proxy workaround
- Guide now includes Telegram Base URL field instructions for n8n credential
fix: resolve dns resolution issues by updating configuration in dns-fix.js