Ollama / Ollama

Ollama Docker Pull Model Manifest TLS Handshake Timeout on Restricted Networks

Running Ollama inside Docker container behind restricted network/firewall/proxy cannot pull models from registry due to TLS handshake timeout; needs proxy configuration or DNS fix workaround Includes evidence for Ollama troubleshooting demand.

Source-backed Last updated June 2, 2026 3 sources Needs local verification

Category: Ollama
Error signature: Error: pull model manifest: Get https://registry.ollama.ai/v2/library/<model>/manifests/latest: net/http: TLS handshake timeout
Quick fix: Verify the model name, local service connectivity, and network access before retrying the model pull.
Updated: June 2, 2026
Verification status: Source-backed
Evidence: 3 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/<model>/manifests/latest: net/http: TLS handshake timeout is a Ollama failure pattern reported for developers trying to running ollama inside docker container behind restricted network/firewall/proxy cannot pull models from registry due to tls handshake timeout; needs proxy configuration or dns fix workaround. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

forums.docker.com thread confirms TLS handshake timeout during ollama pull from Docker container. Root causes include DNS resolution failure (lookup registry.ollama.ai times out), corporate firewall blocking outbound HTTPS, or missing HTTPS_PROXY env var. Hugging Face community thread shows 429 quota errors during model pulls too. Proxy config workaround involves systemd Environment=HTTPS_PROXY setup. Category: Ollama per mapping.

Common causes

forums.docker.com thread confirms TLS handshake timeout during ollama pull from Docker container. Root causes include DNS resolution failure (lookup registry.ollama.ai times out), corporate firewall blocking outbound HTTPS, or missing HTTPS_PROXY env var. Hugging Face community thread shows 429 quota errors during model pulls too. Proxy config workaround involves systemd Environment=HTTPS_PROXY setup. Category: Ollama per mapping.

Quick fixes

Confirm the exact error signature matches Error: pull model manifest: Get https://registry.ollama.ai/v2/library/<model>/manifests/latest: net/http: TLS handshake 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/<model>/manifests/latest: net/http: TLS handshake 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/<model>/manifests/latest: net/http: TLS handshake timeout mean in Ollama?

Error: pull model manifest: Get https://registry.ollama.ai/v2/library/<model>/manifests/latest: net/http: TLS handshake timeout indicates the workflow described by "Ollama Docker Pull Model Manifest TLS Handshake Timeout on Restricted Networks" 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/<model>/manifests/latest: net/http: TLS handshake timeout?

Check whether this cause matches your environment: forums.docker.com thread confirms TLS handshake timeout during ollama pull from Docker container. Root causes include DNS resolution failure (lookup registry.ollama.ai times out), corporate firewall blocking outbound HTTPS, or missing HTTPS_PROXY env var. Hugging Face community thread shows 429 quota errors during model pulls too. Proxy config workaround involves systemd Environment=HTTPS_PROXY setup. Category: Ollama per mapping.

Is the Error: pull model manifest: Get https://registry.ollama.ai/v2/library/<model>/manifests/latest: net/http: TLS handshake timeout guidance source-backed?

The "Ollama Docker Pull Model Manifest TLS Handshake Timeout on Restricted Networks" page is labeled source-backed. It has 3 public source URLs from registry.ollama.ai, forums.docker.com, discuss.huggingface.co, 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/<model>/manifests/latest: net/http: TLS handshake timeout?

For "Ollama Docker Pull Model Manifest TLS Handshake Timeout on Restricted Networks", 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/<model>/manifests/latest: net/http: TLS handshake timeout?

For "Ollama Docker Pull Model Manifest TLS Handshake Timeout on Restricted Networks", 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.