bug: ollama pull fails

[erhant]

People are getting:

Error: could not pull model

Caused by:
    An error occurred with ollama-rs: {"error":"max retries exceeded: Get "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/ollama/docker/registry/v2/blobs/sha256/81/819c2adf5ce6df2b6bd2ae4ca90d2a69f060afeb438d0c171db57daa02e39c3d/data?X-Amz-Algorithm=AWS4-HMAC-SHA256\u0026X-Amz-Credential=66040c77ac1b787c3af820529859349a%2F20250321%2Fauto%2Fs3%2Faws4_request\u0026X-Amz-Date=20250321T140900Z\u0026X-Amz-Expires=86400\u0026X-Amz-SignedHeaders=host\u0026X-Amz-Signature=6c3c06f0c16cccf470f88fa03802663a9d51d6f9b669dcf7492ff498d7464d3f\": dial tcp: lookup dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com on 10.255.255.254:53: server misbehaving"}

I believe they are running in WSL (Windows)

[erhant]

see also: ollama/ollama#2680

[yagneshmb]

I changed DNS server to Google's public DNS and it solved the issue. I gave the issue to Gemini and it provided the below response. I was running WSL inside windows. See gemini's response below

Absolutely! Checking your DNS settings varies slightly depending on your operating system. Here's a detailed guide for common operating systems:

Windows:

1. Open Network Connections:
   • Press the Windows key + R, type ncpa.cpl, and press Enter. This will open the Network Connections window.
2. Select Your Network Adapter:
   • Right-click on the network adapter you're currently using (Wi-Fi or Ethernet) and select "Properties."
3. Open Internet Protocol Version 4 (TCP/IPv4) Properties:
   • In the Properties window, scroll down and select "Internet Protocol Version 4 (TCP/IPv4)." Then, click "Properties."
4. View DNS Settings:
   • In the TCP/IPv4 Properties window, you'll see two options:
     • "Obtain an IP address automatically" and "Obtain DNS server address automatically": If these are selected, your computer is getting its DNS settings from your router or ISP.
     • "Use the following DNS server addresses": If this is selected, you'll see the preferred and alternate DNS server addresses that are currently in use.
5. Change DNS Settings (Optional):
   • If you want to change your DNS servers, select "Use the following DNS server addresses" and enter the desired addresses. Common public DNS servers include:
     • Google Public DNS: Preferred DNS server: 8.8.8.8, Alternate DNS server: 8.8.4.4
     • Cloudflare DNS: Preferred DNS server: 1.1.1.1, Alternate DNS server: 1.0.0.1
   • Click "OK" to save your changes.
6. Clear DNS Cache (Recommended):
   • Open Command Prompt as administrator (search for "cmd," right-click, and select "Run as administrator").
   • Type ipconfig /flushdns and press Enter. This will clear your DNS cache, ensuring that your computer uses the new DNS settings.

macOS:

1. Open System Settings (or System Preferences):
   • Click the Apple menu in the top-left corner and select "System Settings" (or "System Preferences" on older macOS versions).
2. Open Network Settings:
   • Click on "Network."
3. Select Your Network Connection:
   • Select your active network connection (Wi-Fi or Ethernet) from the left-hand side.
4. Click "Details...":
   • Click the "Details..." button.
5. Go to the DNS Tab:
   • Click on the "DNS" tab.
6. View and Change DNS Settings:
   • You'll see a list of DNS server addresses. You can add or remove DNS servers using the "+" and "-" buttons.
   • Add the desired DNS server addresses.
7. Apply Changes:
   • Click "OK" and then "Apply" to save your changes.
8. Clear DNS Cache (Recommended):
   • Open Terminal (Applications > Utilities > Terminal).
   • The command varies depending on your macOS version:
     • For macOS Ventura and later: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
     • For macOS Monterey and earlier: sudo killall -HUP mDNSResponder
   • Enter your administrator password when prompted.

Linux (Ubuntu/Debian):

1. Check Network Settings (GUI):
   • Open your system settings and navigate to the network settings. The exact steps may vary depending on your desktop environment (GNOME, KDE, etc.).
   • Select your active network connection and look for DNS settings.
2. Check Network Settings (Terminal):
   • The way to check network settings through the terminal depends on your network configuration.
   • If using NetworkManager, you can use the command nmcli device show <interface> (replace <interface> with your network interface name, like wlan0 or eth0).
   • You can also check the /etc/resolv.conf file, but it is often automatically generated.
3. Change DNS Settings (GUI):
   • In the network settings, you should be able to manually specify DNS server addresses.
4. Change DNS Settings (Terminal):
   • Editing /etc/resolv.conf is not recommended for persistent changes with NetworkManager.
   • To make persistent changes using NetworkManager, you can use nmcli or edit the network connection configuration files.
5. Clear DNS Cache (Recommended):
   • The command to clear the DNS cache depends on the DNS service used:
     • sudo systemd-resolve --flush-caches (for systemd-resolved)
     • sudo /etc/init.d/dns-clean start (for dns-clean)
     • sudo service dnsmasq restart (for dnsmasq)
     • sudo service nscd restart (for nscd)

Important Notes:

• Changing your DNS settings can affect your internet browsing experience. If you encounter problems, revert to your original settings.
• Using public DNS servers like Google or Cloudflare can improve your browsing speed and security.
• When changing network configuration files, always create a backup before making any changes.
• When using the terminal, sudo will require your user password.

I hope this detailed explanation helps you check and manage your DNS settings.

[erhant]

Hi @yagneshmb thanks for the info 🙏🏻

I would still suggest that people use Windows as-is instead of WSL, it will have better native performance as well (e.g. with Ollama)

[erhant]

We would like to keep installation as simple as possible, and adding extra DNS configuration steps would make things a bit harder for everyone

[yagneshmb]

@erhant
Yeah. Makes sense. Although I was in a hurry I just tried. It just worked. :)

[erhant]

Closing this issue along with #32 as we prefer that the users use Windows cmd.exe instead.

[erhant]

Reopening because reports are coming that this still fails for Powershell, even outside WSL

[erhant]

 Downloading missing model hellord/mxbai-embed-large-v1:f16 (this may take a while)
Error: could not pull model

Caused by:
    An error occurred with ollama-rs: {"error":"max retries exceeded: Get "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/ollama/docker/registry/v2/blobs/sha256/81/819c2adf5ce6df2b6bd2ae4ca90d2a69f060afeb438d0c171db57daa02e39c3d/data?X-Amz-Algorithm=AWS4-HMAC-SHA256\u0026X-Amz-Credential=66040c77ac1b787c3af820529859349a%2F20250402%2Fauto%2Fs3%2Faws4_request\u0026X-Amz-Date=20250402T145834Z\u0026X-Amz-Expires=86400\u0026X-Amz-SignedHeaders=host\u0026X-Amz-Signature=a31b0196a7597489b5dbd4ea43e829b7be1117cd3948f59a569172e4c842e0db\": dial tcp: lookup dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com: no such host"}

[erhant]

In windows, the following commands fixes the issue.

# find interface name here
netsh interface show interface

# suppose your interface name is "Wi-Fi", then do:
netsh interface ip set dns "Wi-Fi" static 8.8.8.8
netsh interface ip add dns "Wi-Fi" 8.8.4.4 index=2

# finally flush DNS
ipconfig /flushdns

It is indeed about DNS, as #33 (comment) mentioned.