Ollama / Ollama

Ollama 'pulling manifest' i/o timeout error fetching models from registry

Fix Ollama model download failures caused by network timeouts when connecting to the Ollama registry Includes evidence for Ollama troubleshooting demand.

Source-backed Last updated May 29, 2026 4 sources Needs local verification

Category: Ollama
Error signature: Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/...": dial tcp <IP>:443: i/o timeout
Quick fix: Verify the model name, local service connectivity, and network access before retrying the model pull.
Updated: May 29, 2026
Verification status: Source-backed
Evidence: 4 public source URLs

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Ollama, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/...": dial tcp <IP>:443: i/o timeout is a Ollama failure pattern reported for developers trying to fix ollama model download failures caused by network timeouts when connecting to the ollama registry. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue #16330 (created 2026-05-27, updated 2026-05-28): Raspberry Pi 5 and general Linux setups fail to pull any models with explicit i/o timeout when resolving registry.ollama.ai. Error matches real developer scenario — building local LLM environments. High commercial intent from developers running local inference services.

Common causes

GitHub issue #16330 (created 2026-05-27, updated 2026-05-28): Raspberry Pi 5 and general Linux setups fail to pull any models with explicit i/o timeout when resolving registry.ollama.ai. Error matches real developer scenario — building local LLM environments. High commercial intent from developers running local inference services.

Quick fixes

Confirm the exact error signature matches Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/...": dial tcp <IP>:443: i/o timeout.
Check the Ollama account, local tool state, and provider configuration involved in the failing workflow.
Verify the model name, local service connectivity, and network access before retrying the model pull.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/...": dial tcp <IP>:443: i/o timeout exactly before applying the quick fix.
Compare the failing environment with Ollama versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/...": dial tcp <IP>:443: i/o timeout mean in Ollama?

Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/...": dial tcp <IP>:443: i/o timeout indicates the workflow described by "Ollama 'pulling manifest' i/o timeout error fetching models from registry" failed in a Ollama context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/...": dial tcp <IP>:443: i/o timeout?

Check whether this cause matches your environment: GitHub issue #16330 (created 2026-05-27, updated 2026-05-28): Raspberry Pi 5 and general Linux setups fail to pull any models with explicit i/o timeout when resolving registry.ollama.ai. Error matches real developer scenario — building local LLM environments. High commercial intent from developers running local inference services.

Is the Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/...": dial tcp <IP>:443: i/o timeout guidance source-backed?

The "Ollama 'pulling manifest' i/o timeout error fetching models from registry" page is labeled source-backed. It has 4 public source URLs from registry.ollama.ai, github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/...": dial tcp <IP>:443: i/o timeout?

For "Ollama 'pulling manifest' i/o timeout error fetching models from registry", avoid applying "Verify the model name, local service connectivity, and network access before retrying the model pull." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/...": dial tcp <IP>:443: i/o timeout?

For "Ollama 'pulling manifest' i/o timeout error fetching models from registry", collect the failing Ollama command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.