Ollama: 'blocked redirect to a different host'

Site Feedback
1

while trying:

ollama pull hf-co /empero-ai/Qwen3.8-35B-A3B-Distill-GGUF:Q8_0

got error:

blocked redirect to a different host

edit: resolved after some time

2

Glad to hear it eventually resolved — that redirect error usually comes from a temporary CDN switch on the HF side, and Ollama blocks cross‑host redirects for safety.

If you have a moment, could you leave a quick feedback about whether the pull speed and model loading behaved normally after the issue cleared? It helps track whether the redirect glitch had any side effects on the client.

3

I am constantly seeing the same error, it does not resolve after waiting some time. It happens only for hugging face models e.g. ollama run hf.co/unsloth/Qwen3.8-27B-GGUF:UD-IQ4_XS

However, it works fine with models hosted on Ollama.com e.g. https://ollama.com/batiai/gemma4-e2b

4

I have the same issue. After how much time is the issue supposed to “resolve itself”?

Is there no workaround to be still able to run hf models in ollama?

5

Same here. I can no longer download models from Hugging Face, only those hosted on Ollama.com. I’ve also tried several times, but it doesn’t resolve on its own after a while. Any solutions?

Edit: I was able to complete the installation using the command ollama pull --insecure ``hf.co/unsloth/Qwen3.8-27B-GGUF:UD-IQ3_S

6

yep, now again getting this error with ollama pull hf.co/TokenRhythm/NeoHorse-1-4B-GGUF:BF16
but thanks to @mattks92 --insecure option it now pulls

7

That redirect error usually comes from a temporary CDN host switch on HuggingFace.
Ollama blocks the cross‑host redirect for security reasons, so the pull fails until the endpoint stabilizes.

Using --insecure bypasses the certificate/host check and lets the pull continue normally.
Nothing wrong with the model or the repo — just a transient network condition.

8

I know this has been marked as solution, and the --insecure is working for me. but I think there should be a more robust way of saying: If I ask you hf.co is ok that you get us.aws.cdn.hf.co

for me the --insecure opens an insecure can of worms :slight_smile: