Ollama Not Connecting from Your Phone? 6 Checks

Quick answer: If Ollama works on your computer but your phone cannot connect, replace localhost with the computer's LAN IP, confirm Ollama is listening beyond 127.0.0.1, and open http://YOUR_COMPUTER_IP:11434/api/tags from the phone or another device on the same network. If that request fails, fix the host binding, firewall, or Wi-Fi network before changing the client app.

The fastest way to fix an Ollama phone connection is to test one layer at a time. The phone cannot repair a server that is listening only on itself, and a client cannot discover a model behind a blocked port. Work through this checklist in order and stop as soon as a check fails.

1. Use the computer's LAN address, not localhost

localhost and 127.0.0.1 mean “this device.” In a phone app, they point to the phone, not the Mac or PC running Ollama. Find the computer's private network address, such as 192.168.1.42, and use:

http://192.168.1.42:11434

In Ollama Connect, save the server address without /api/tags; the app adds Ollama's API paths itself. Use the full /api/tags URL only for the connectivity test below.

2. Check the Ollama bind address

Ollama binds to 127.0.0.1:11434 by default. The official FAQ documents OLLAMA_HOST as the setting that changes this. For a temporary test, start the server with:

OLLAMA_HOST=0.0.0.0:11434 ollama serve

If Ollama runs as a macOS app, set the environment variable through launchctl, then restart the app:

launchctl setenv OLLAMA_HOST "0.0.0.0:11434"

The restart matters. The server reads this setting when it starts; changing the variable while an old Ollama process is still running does not change the listener.

3. Prove the endpoint from another device

From a second computer on the same network, run:

curl --max-time 5 http://192.168.1.42:11434/api/tags

A JSON response with a models array means the server answered the request. You can also open the same URL in the phone's browser. If you get “connection refused,” Ollama is not listening on that address or port. If the request times out, check the firewall and whether both devices are really on the same network.

Run this test before opening the phone app. It separates server and network problems from client configuration problems.

4. Check the firewall and Wi-Fi network

Binding to 0.0.0.0 makes Ollama listen on network interfaces, but the operating-system firewall can still reject inbound TCP connections on port 11434. Allow Ollama or the port on the computer's private network, then retry /api/tags.

Also check for guest Wi-Fi, client isolation, a VPN that changes routing, or a phone using cellular data instead of the same home network. A phone may show full Wi-Fi signal and still be prevented from reaching another device by the access point.

5. Match the app settings to the server

Once /api/tags works from another device, add the host to Ollama Connect using the computer's IP, port 11434, and any path prefix used by your reverse proxy. The app tests the Ollama tags endpoint and reports whether the host is connected, unreachable, timed out, unauthorized, or responding with an incompatible payload.

If the server is behind HTTPS or a proxy that requires a bearer token, enter the proxy URL and token instead of bypassing the proxy. Ollama Connect stores host details locally and protects bearer tokens with iOS Keychain or Android Keystore storage. The app does not provide a hosted model or relay a request through Pocket Grove; it is a client for the Ollama host you configure.

Do not change OLLAMA_ORIGINS just because a native phone app cannot connect. Ollama documents that setting for additional web origins and browser extensions; it does not make an unreachable server, blocked port, or incorrect address reachable.

6. Read the error instead of guessing

• Invalid host: check that the address includes a valid IP or URL and that the port is a number.
• Timed out: check the computer's reachability, firewall, VPN, and Wi-Fi isolation.
• Unauthorized: check the bearer token and reverse-proxy authentication rules.
• Unsupported endpoint: check that the address really points to Ollama and that the path prefix is correct.
• Server error: inspect the proxy path and Ollama logs; an HTTP error is different from a network outage.
• Connected, no models: the network works, but the selected Ollama host is not reporting an installed model yet.

The complete Ollama network setup guide covers persistent binding and platform-specific firewall steps. For a broader privacy and hardware overview, see how to run a private LLM at home.

Keep the endpoint private

The Ollama authentication documentation says local access through http://localhost:11434 does not require authentication. Do not expose an unauthenticated Ollama port directly to the public internet. Keep it on a trusted LAN or put a properly secured VPN or reverse proxy in front of it. If you only need a phone on the same home network, the private LAN setup is the smaller and safer surface.

When the endpoint passes the second-device test, add the same host address in Ollama Connect for iPhone or Android. Use the tracked App Store download or Google Play download for your device. The full app details explain what the client does before you install it.