Expired60% confidenceDecision RuleExact time
When configuring Ollama in Dify, if both are deployed on the same machine the Docker internal network address http://host.docker.internal:11434 must be used; if deployed on separate machines, enter the Ollama server's public IP and port.
2
Sources
60%
Confidence
Medium-term (~90 days)
Relevance
7/22/2026
First Seen
This claim has expired. It is kept for the record and no longer describes the current state.
Valid until: 10/20/2026(expired)
Sources
Ollama+Dify+DeepSeek本地企业级知识库搭建全指南
Related Claims
UnverifiedIn Docker's default bridge network, localhost inside the container points to the container itself rather than the host machine; if Ollama runs on the host machine, the FastAPI container accessing it usually needs host.docker.internal (Docker Desktop), or on Linux via --network=host, a custom bridge network with the host gateway IP specified.77% similarUnverifiedThe way Dify interfaces with Ollama is by filling in the Ollama local service address in the model provider settings, which defaults to http://localhost:11434.71% similarUnverified127.0.0.1 is the local loopback address that only accepts connections from the same host; after changing to 0.0.0.0, Ollama listens for requests on all network interfaces, including Docker containers and local area network access.68% similarVerifiedOllama listens on local port 11434 by default, and AnythingLLM communicates with it via HTTP API.66% similarUnverifiedOllama requires no authentication by default because it assumes it will only run on the local loopback address (127.0.0.1), serving only applications on the same machine.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/590863API
curl https://kongchang.com/api/v1/knowledge/claims/590863MCP
get_claim(id=590863)