Web Asset House Guides
Local AI

Use Ollama from Other Devices: OLLAMA_HOST, OLLAMA_ORIGINS and Safety

By Web Asset House Studio ·

Note: Some future links on this site may be affiliate links. We never claim hands-on testing; guides are researched from the public sources listed in each article.

How we wrote this: A plain-English summary of Ollama's official documentation (FAQ), checked October 29, 2026. Exposing a service changes your security picture; only do it on networks you trust.

The default: this computer only

Ollama's FAQ says the server binds 127.0.0.1, port 11434 by default. Only apps on the same computer can reach it.

Listen on your network: OLLAMA_HOST

Set OLLAMA_HOST to change the bind address. The FAQ's example is 0.0.0.0:11434, which listens on all network interfaces. Then restart Ollama.

Other devices can then use http://<that computer's IP>:11434.

Allow web origins: OLLAMA_ORIGINS

By default, Ollama allows cross-origin requests only from 127.0.0.1 and 0.0.0.0. To let web apps or browser extensions call it, add their origins to OLLAMA_ORIGINS. The FAQ's example allows all Chrome, Firefox and Safari extensions:

OLLAMA_ORIGINS=chrome-extension://*,moz-extension://*,safari-web-extension://* ollama serve

Allowing only the specific extensions you use is the narrower choice.

Be careful

Ollama's local API has no login of its own, so anyone who can reach port 11434 can use your models. Before you change the default:

Related: Open WebUI, Ollama in Docker, the local API, proxy and startup settings.

Sources

← All Local AI guides · All guides