github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 00:51:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #12236] [Macos Tahoe]: Ollama settings block internet connection activity #70199

New Issue
Open
opened 2026-05-04 20:38:33 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-04 20:38:33 -05:00
Owner
Copy Link

Originally created by @Quadriphobs1 on GitHub (Sep 10, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/12236

What is the issue?

I just installed the latest macOS Tahoe and I notice I wasn't able to connect via other apps but using curl or dig or nslookup seems to work just fine.

When I restart I noticed the same thing however, Ollama was the only other app running so I close it and I was able to connect via my browser(safari) got me curious as to why Ollama might be cause.

After several chats with ChatGPT debugging it pointed out that Ollama might be binding to a local interface like lo0 and it might have changed the default route or dns resolver and the traffic get misdirected.

So when I run this command networksetup -getsecurewebproxy Wi-Fi and networksetup -getsecurewebproxy Wi-Fi off it shows

Enabled: Yes
Server: 127.0.0.1
Port: 9090
Authenticated Proxy Enabled: 0

In order for me to get other apps to connect to the internet I had to run networksetup -setwebproxystate Wi-Fi off and networksetup -setsecurewebproxystate Wi-Fi off which will sets them to off.

I also run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder and sudo route -n flush to clear any dns and routing tables

And now whenever I do launchctl list | grep ollama it shows nothing.

I am not sure if this is something specifically wrong from ollama or from the macOS update, I thought I'd create a ticket here in case anyone else have this issue and wants a possible solution and if anyone have a likely solution for this that doesn't require flushing my dns routing table

Relevant log output

OS

Macos Tahoe

Ollama version

v0.11.10

Originally created by @Quadriphobs1 on GitHub (Sep 10, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/12236 ### What is the issue? I just installed the latest macOS Tahoe and I notice I wasn't able to connect via other apps but using `curl` or `dig` or `nslookup` seems to work just fine. When I restart I noticed the same thing however, Ollama was the only other app running so I close it and I was able to connect via my browser(safari) got me curious as to why Ollama might be cause. After several chats with ChatGPT debugging it pointed out that Ollama might be binding to a local interface like lo0 and it might have changed the default route or dns resolver and the traffic get misdirected. So when I run this command `networksetup -getsecurewebproxy Wi-Fi` and `networksetup -getsecurewebproxy Wi-Fi off` it shows ``` Enabled: Yes Server: 127.0.0.1 Port: 9090 Authenticated Proxy Enabled: 0 ``` In order for me to get other apps to connect to the internet I had to run `networksetup -setwebproxystate Wi-Fi off` and `networksetup -setsecurewebproxystate Wi-Fi off` which will sets them to `off`. I also run `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder` and `sudo route -n flush` to clear any dns and routing tables And now whenever I do `launchctl list | grep ollama` it shows nothing. I am not sure if this is something specifically wrong from ollama or from the macOS update, I thought I'd create a ticket here in case anyone else have this issue and wants a possible solution and if anyone have a likely solution for this that doesn't require flushing my dns routing table ### Relevant log output ```shell ``` ### OS Macos Tahoe ### Ollama version v0.11.10
GiteaMirror added the bug label 2026-05-04 20:38:33 -05:00
GiteaMirror commented 2026-05-04 20:38:36 -05:00
Author
Owner
Copy Link

@Quadriphobs1 commented on GitHub (Sep 10, 2025):

I made this gist for a possible solution

https://gist.github.com/Quadriphobs1/6b70b2b9395b3f1135f9a92e23bc132f

<!-- gh-comment-id:3272876932 --> @Quadriphobs1 commented on GitHub (Sep 10, 2025): I made this gist for a possible solution https://gist.github.com/Quadriphobs1/6b70b2b9395b3f1135f9a92e23bc132f
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#70199
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?