[GH-ISSUE #8565] Error when trying to download deepseek-r1:7b #31291

Closed
opened 2026-04-22 11:36:25 -05:00 by GiteaMirror · 16 comments
Owner

Originally created by @makhlwf on GitHub (Jan 24, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/8565

What is the issue?

I tried using ollama run deepseek-r1:7b
It started to download for a minute then this error appeared
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.

OS

Windows

GPU

Nvidia

CPU

AMD

Ollama version

0.5.7

Originally created by @makhlwf on GitHub (Jan 24, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/8565 ### What is the issue? I tried using ollama run deepseek-r1:7b It started to download for a minute then this error appeared 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. ### OS Windows ### GPU Nvidia ### CPU AMD ### Ollama version 0.5.7
GiteaMirror added the needs more infobug labels 2026-04-22 11:36:26 -05:00
Author
Owner

@Shiven-saini commented on GitHub (Jan 24, 2025):

Try different port:
export OLLAMA_HOST=http://localhost:8080

Then restart the ollama service :-
ollama serve
or if you are following a service based approach.
sudo systemctl daemon-reload
sudo systemctl restart ollama

<!-- gh-comment-id:2612347860 --> @Shiven-saini commented on GitHub (Jan 24, 2025): Try different port: `export OLLAMA_HOST=http://localhost:8080` Then restart the ollama service :- `ollama serve` or if you are following a service based approach. `sudo systemctl daemon-reload` `sudo systemctl restart ollama`
Author
Owner

@makhlwf commented on GitHub (Jan 24, 2025):

Try different port:
export OLLAMA_HOST=http://localhost:8080

Then restart the ollama service :-
ollama serve
or if you are following a service based approach.
sudo systemctl daemon-reload
sudo systemctl restart ollama

Same thing happening after using the commands**

setx OLLAMA_HOST http://localhost:8080

ollama serve

<!-- gh-comment-id:2612381998 --> @makhlwf commented on GitHub (Jan 24, 2025): > Try different port: > `export OLLAMA_HOST=http://localhost:8080` > > Then restart the ollama service :- > `ollama serve` > or if you are following a service based approach. > `sudo systemctl daemon-reload` > `sudo systemctl restart ollama` Same thing happening after using the commands** * setx OLLAMA_HOST http://localhost:8080 ollama serve
Author
Owner

@rick-github commented on GitHub (Jan 24, 2025):

Server logs may aid in debugging.

Run this in an Administrator PowerShell terminal and post the result:

netstat -bano | Select-String -Pattern 11434 -Context 0,1
netsh interface ipv4 show excludedportrange protocol=tcp
<!-- gh-comment-id:2612420521 --> @rick-github commented on GitHub (Jan 24, 2025): [Server logs](https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md#how-to-troubleshoot-issues) may aid in debugging. Run this in an Administrator PowerShell terminal and post the result: ``` netstat -bano | Select-String -Pattern 11434 -Context 0,1 netsh interface ipv4 show excludedportrange protocol=tcp ```
Author
Owner

@makhlwf commented on GitHub (Jan 24, 2025):

PS C:> netstat -bano | Select-String -Pattern 11434 -Context 0,1

TCP 127.0.0.1:11434 0.0.0.0:0 LISTENING 8656
[ollama.exe]

PS C:> netsh interface ipv4 show excludedportrange protocol=tcp

Protocol tcp Port Exclusion Ranges

Start Port End Port


  5357        5357
 49714       49813
 49814       49913
 50000       50059     *
 50160       50259
 50260       50359
 50360       50459
 50460       50559
 50560       50659
 50884       50983
 56344       56443
    • Administered port exclusions.

PS C:>

<!-- gh-comment-id:2612451529 --> @makhlwf commented on GitHub (Jan 24, 2025): PS C:\> netstat -bano | Select-String -Pattern 11434 -Context 0,1 > TCP 127.0.0.1:11434 0.0.0.0:0 LISTENING 8656 [ollama.exe] PS C:\> netsh interface ipv4 show excludedportrange protocol=tcp Protocol tcp Port Exclusion Ranges Start Port End Port ---------- -------- 5357 5357 49714 49813 49814 49913 50000 50059 * 50160 50259 50260 50359 50360 50459 50460 50559 50560 50659 50884 50983 56344 56443 * - Administered port exclusions. PS C:\>
Author
Owner

@rick-github commented on GitHub (Jan 24, 2025):

Output of:

curl http://localhost:11434/api/version
curl http://127.0.0.1:11434/api/version

And server logs.

<!-- gh-comment-id:2612497006 --> @rick-github commented on GitHub (Jan 24, 2025): Output of: ``` curl http://localhost:11434/api/version curl http://127.0.0.1:11434/api/version ``` And server logs.
Author
Owner

@makhlwf commented on GitHub (Jan 26, 2025):

Output of:

curl http://localhost:11434/api/version
curl http://127.0.0.1:11434/api/version

And server logs.

PS C:> curl http://localhost:11434/api/version
curl : Unable to connect to the remote server
At line:1 char:1

  • curl http://localhost:11434/api/version
  •   + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
     eption
      + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
    
    

PS C:> curl http://127.0.0.1:11434/api/versio
curl : Unable to connect to the remote server
At line:1 char:1

  • curl http://127.0.0.1:11434/api/versio
  •   + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
     eption
      + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
    
    

PS C:>

<!-- gh-comment-id:2614260012 --> @makhlwf commented on GitHub (Jan 26, 2025): > Output of: > ``` > curl http://localhost:11434/api/version > curl http://127.0.0.1:11434/api/version > ``` > And server logs. PS C:\> curl http://localhost:11434/api/version curl : Unable to connect to the remote server At line:1 char:1 + curl http://localhost:11434/api/version + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc eption + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand PS C:\> curl http://127.0.0.1:11434/api/versio curl : Unable to connect to the remote server At line:1 char:1 + curl http://127.0.0.1:11434/api/versio + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc eption + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand PS C:\>
Author
Owner

@rick-github commented on GitHub (Jan 26, 2025):

Something is preventing connections to port 11434. Do you have a proxy, firewall or anti virus software? Try turning it off.

<!-- gh-comment-id:2614261458 --> @rick-github commented on GitHub (Jan 26, 2025): Something is preventing connections to port 11434. Do you have a proxy, firewall or anti virus software? Try turning it off.
Author
Owner

@makhlwf commented on GitHub (Jan 26, 2025):

Something is preventing connections to port 11434. Do you have a proxy, firewall or anti virus software? Try turning it off.

I don't know actually my antivirus and my fire wall both are turned off and I don't use any VPN at all

<!-- gh-comment-id:2614272338 --> @makhlwf commented on GitHub (Jan 26, 2025): > Something is preventing connections to port 11434. Do you have a proxy, firewall or anti virus software? Try turning it off. I don't know actually my antivirus and my fire wall both are turned off and I don't use any VPN at all
Author
Owner

@rohanrlobo commented on GitHub (Jan 27, 2025):

The error you encountered when trying to run ollama run deepseek-r1:7b may be due to the Ollama application not running properly in the background. Here are the steps to troubleshoot the issue:

Check if Ollama is Running: Ensure that the Ollama application is running in the background. You can check the system tray for the Ollama icon.

Quit and Relaunch: If Ollama is already running, quit the tray application and relaunch it from the Start menu. After relaunching, try running the command again.

Firewall Settings: If the issue persists, check your firewall settings to ensure that they are not blocking the connection to 127.0.0.1:11434.

<!-- gh-comment-id:2614957491 --> @rohanrlobo commented on GitHub (Jan 27, 2025): The error you encountered when trying to run ollama run deepseek-r1:7b may be due to the Ollama application not running properly in the background. Here are the steps to troubleshoot the issue: Check if Ollama is Running: Ensure that the Ollama application is running in the background. You can check the system tray for the Ollama icon. Quit and Relaunch: If Ollama is already running, quit the tray application and relaunch it from the Start menu. After relaunching, try running the command again. Firewall Settings: If the issue persists, check your firewall settings to ensure that they are not blocking the connection to 127.0.0.1:11434.
Author
Owner

@blastewe commented on GitHub (Jan 29, 2025):

Having the same problem with the 1.5B one

<!-- gh-comment-id:2621868460 --> @blastewe commented on GitHub (Jan 29, 2025): Having the same problem with the 1.5B one
Author
Owner

@rick-github commented on GitHub (Jan 29, 2025):

Is it the same ("connectex: No connection could be made because the target machine actively refused it.") or is it different: https://github.com/ollama/ollama/issues/8657

<!-- gh-comment-id:2621878055 --> @rick-github commented on GitHub (Jan 29, 2025): Is it the same ("connectex: No connection could be made because the target machine actively refused it.") or is it different: https://github.com/ollama/ollama/issues/8657
Author
Owner

@aole commented on GitHub (Mar 13, 2025):

Image

<!-- gh-comment-id:2719760186 --> @aole commented on GitHub (Mar 13, 2025): ![Image](https://github.com/user-attachments/assets/973b190c-1a9c-4652-89b5-442b5371b4ea)
Author
Owner

@rick-github commented on GitHub (Mar 13, 2025):

Server logs may aid in debugging.

Run this in an Administrator PowerShell terminal and post the result:

netstat -bano | Select-String -Pattern 11434 -Context 0,1
netsh interface ipv4 show excludedportrange protocol=tcp
<!-- gh-comment-id:2720393836 --> @rick-github commented on GitHub (Mar 13, 2025): [Server logs](https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md#how-to-troubleshoot-issues) may aid in debugging. Run this in an Administrator PowerShell terminal and post the result: ``` netstat -bano | Select-String -Pattern 11434 -Context 0,1 netsh interface ipv4 show excludedportrange protocol=tcp ```
Author
Owner

@STPv22 commented on GitHub (May 16, 2025):

Hello, sorry for the bump, but I'm trying to run deepseekv3 on my device, but i haven't been successful. i get a similar error when i use run, and pull has no success message, unlike with a smaller model I tested. I had no problems with a 1.7 GB model, and I'm trying a 50 GB model at the moment to see if its just deepseek, or the file size.

I also have the same hardware setup as the original poster. RTX 4060, Ryzen 5 5600 g, 16 GB ddr4 ram, win 11. I'm trying to install the model on an old 500 GB RPM drive that has a 10 mb/s speed on average.

<!-- gh-comment-id:2887396077 --> @STPv22 commented on GitHub (May 16, 2025): Hello, sorry for the bump, but I'm trying to run deepseekv3 on my device, but i haven't been successful. i get a similar error when i use `run`, and `pull` has no success message, unlike with a smaller model I tested. I had no problems with a 1.7 GB model, and I'm trying a 50 GB model at the moment to see if its just deepseek, or the file size. I also have the same hardware setup as the original poster. RTX 4060, Ryzen 5 5600 g, 16 GB ddr4 ram, win 11. I'm trying to install the model on an old 500 GB RPM drive that has a 10 mb/s speed on average.
Author
Owner

@rick-github commented on GitHub (May 16, 2025):

Server logs may aid in debugging.

<!-- gh-comment-id:2887400836 --> @rick-github commented on GitHub (May 16, 2025): [Server logs](https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md#how-to-troubleshoot-issues) may aid in debugging.
Author
Owner

@STPv22 commented on GitHub (May 16, 2025):

ok, thank you

<!-- gh-comment-id:2887528081 --> @STPv22 commented on GitHub (May 16, 2025): ok, thank you
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#31291