Skip to content

docs: explain InvokeAI HuggingFace downloads behind fake-IP DNS - #1789

Open
wesd6r wants to merge 1 commit into
LykosAI:mainfrom
wesd6r:docs/invokeai-fake-ip-downloads
Open

wesd6r wants to merge 1 commit into
LykosAI:mainfrom
wesd6r:docs/invokeai-fake-ip-downloads

Conversation

@wesd6r

@wesd6r wesd6r commented Oct 25, 2026

Copy link
Copy Markdown

Adds a troubleshooting entry for the case reported in #1788: InvokeAI's downloader rejects huggingface.co when a fake-IP DNS proxy (Clash Verge / mihomo TUN, Surge, etc.) resolves it into the 198.18.0.0/15 range. The page now documents both workarounds:

  • keep InvokeAI's SSRF protection by adding huggingface.co, +.huggingface.co and +.hf.co to the proxy's fake-ip-filter, or
  • set allow_private_download_urls: true in the package's invokeai-root/invokeai.yaml and restart the package.

It also notes that this affects downloads made by InvokeAI itself, not the Stability Matrix Model Browser.

Docs only; no code changes. Refs #1788.

🤖 Generated with Claude Code

InvokeAI's downloader rejects hosts that resolve into a proxy's fake-IP range. Document both workarounds: add HuggingFace domains to the proxy's fake-ip-filter, or set allow_private_download_urls in the package's invokeai.yaml. Refs LykosAI#1788.

Co-Authored-By: Claude Code <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant