> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/integrations/builtin/credentials/ollama.md).

# Set up Ollama credentials in Duaer

Store Ollama connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.
## Connect to Ollama <a href="#connect-to-ollama" id="connect-to-ollama"></a>

The Duaer Ollama credential needs an Ollama address the Duaer server can reach:

- Base URL defaults to http://localhost:11434. That works only when Ollama and Duaer run on the same machine and Duaer is not in a container.
- When Duaer runs in Docker and Ollama runs on the host, use http://host.docker.internal:11434 (on Linux, add a host-gateway mapping to the container), or the Ollama service name on the same Docker network.
- Ollama listens on 127.0.0.1 by default. To reach it from another machine, set OLLAMA_HOST=0.0.0.0 for Ollama and restart it.
- Fill in API Key only when Ollama sits behind a proxy with authentication, such as Open WebUI.

For refused connections or missing models, refer to [Ollama Chat Model common issues](/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.lmchatollama/common-issues.md).

## Ollama fields in Duaer <a href="#ollama" id="ollama"></a>

In Duaer, choose Ollama when you create a credential, then fill in these fields:

- Base URL (required): Default: http://localhost:11434.
- API Key (secret): When using Ollama behind a proxy with authentication (such as Open WebUI), provide the Bearer token/API key here. This is not required for the default Ollama installation.

When you save, Duaer tests the connection with these values.

Duaer nodes that use it: [Ollama](/integrations/builtin/app-nodes/n8n-nodes-langchain.ollama.md), [Embeddings Ollama](/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.embeddingsollama.md), [Ollama Chat Model](/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.lmchatollama.md), [Ollama Model](/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.lmollama.md).

## Save the connection in Duaer

Open Credentials and create Ollama. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.

Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. The matching node is under [the related node](/integrations/builtin/app-nodes/n8n-nodes-langchain.ollama.md).

## Who can use this credential

Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.
## Questions

### Do Ollama secret values appear in Duaer node parameters?

No. In Duaer, Ollama secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

### What usually stops a Ollama credential from saving in Duaer?

Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields Ollama expects, then confirm you can create credentials in that project.

