Ollama / Ollama

Ollama Model Pull Terminated When Chat GUI Closed — Download Progress Lost

Fix Ollama model pull being killed when Chat GUI is closed, and download not resuming from last checkpoint Includes evidence for Ollama troubleshooting demand.

Source-backed Last updated May 14, 2026 1 source Needs local verification

Category: Ollama
Error signature: Error: Post "http://127.0.0.1:11434/api/show": dial tcp 127.0.0.1:11434: connectex: No connection could be made because the target machine actively refused it.
Quick fix: Verify the model name, local service connectivity, and network access before retrying the model pull.
Updated: May 14, 2026
Verification status: Source-backed
Evidence: 1 public source URL

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: Post "http://127.0.0.1:11434/api/show": dial tcp 127.0.0.1:11434: connectex: No connection could be made because the target machine actively refused it. is a Ollama failure pattern reported for developers trying to fix ollama model pull being killed when chat gui is closed, and download not resuming from last checkpoint. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Issue #11742 on ollama/ollama: user pulling qwen3-coder (18GB), closed Chat GUI at 33%, download terminated and restarted from 0%. Error: connection refused to localhost:11434. Ollama v0.11.2 on Windows.

Common causes

Closing the Ollama Chat GUI during an active model pull terminates the entire download process. The error shows 'connection refused' because the server shuts down. Download progress is completely lost — re-running starts from 0%. This is a data loss issue for users pulling large models (18GB+).
Issue #11742 on ollama/ollama: user pulling qwen3-coder (18GB), closed Chat GUI at 33%, download terminated and restarted from 0%. Error: connection refused to localhost:11434. Ollama v0.11.2 on Windows.

Quick fixes

Confirm the exact error signature matches Error: Post "http://127.0.0.1:11434/api/show": dial tcp 127.0.0.1:11434: connectex: No connection could be made because the target machine actively refused it..
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: Post "http://127.0.0.1:11434/api/show": dial tcp 127.0.0.1:11434: connectex: No connection could be made because the target machine actively refused it. 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: Post "http://127.0.0.1:11434/api/show": dial tcp 127.0.0.1:11434: connectex: No connection could be made because the target machine actively refused it. mean in Ollama?

Error: Post "http://127.0.0.1:11434/api/show": dial tcp 127.0.0.1:11434: connectex: No connection could be made because the target machine actively refused it. indicates the workflow described by "Ollama Model Pull Terminated When Chat GUI Closed — Download Progress Lost" failed in a Ollama context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Error: Post "http://127.0.0.1:11434/api/show": dial tcp 127.0.0.1:11434: connectex: No connection could be made because the target machine actively refused it.?

Check whether this cause matches your environment: Closing the Ollama Chat GUI during an active model pull terminates the entire download process. The error shows 'connection refused' because the server shuts down. Download progress is completely lost — re-running starts from 0%. This is a data loss issue for users pulling large models (18GB+).

Is the Error: Post "http://127.0.0.1:11434/api/show": dial tcp 127.0.0.1:11434: connectex: No connection could be made because the target machine actively refused it. guidance source-backed?

The "Ollama Model Pull Terminated When Chat GUI Closed — Download Progress Lost" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Error: Post "http://127.0.0.1:11434/api/show": dial tcp 127.0.0.1:11434: connectex: No connection could be made because the target machine actively refused it.?

For "Ollama Model Pull Terminated When Chat GUI Closed — Download Progress Lost", 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: Post "http://127.0.0.1:11434/api/show": dial tcp 127.0.0.1:11434: connectex: No connection could be made because the target machine actively refused it.?

For "Ollama Model Pull Terminated When Chat GUI Closed — Download Progress Lost", 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.