Skip to main content
← All guides

Share a local LLM privately

Why qURL here

Keep Ollama bound to localhost and invite the people you choose by email to your Open WebUI: each verifies their address and saves a passkey. Replies stream as the model writes them, and a one-time qURL™ link covers a quick try.

Steps

With qURL, keep Ollama and Open WebUI bound to localhost, publish the web interface with qurl publish, and send the link from qurl share. The model server never gets a public address, and each link works once and expires within 24 hours. Replies stream to their browser as the model writes them.

  1. Install the qURL CLI

    On macOS, install it with Homebrew. On Linux and Windows, download the package for your platform from the latest release; the CLI page lists each one. Nothing asks you to sign up.

    brew install layervai/tap/qurl
    qurl --version
  2. Keep the model server on localhost

    Ollama binds 127.0.0.1 port 11434 by default. Keep it that way: don’t set OLLAMA_HOST to 0.0.0.0 or turn on “Expose Ollama to the network” in the app’s settings. If Ollama runs in Docker, publish its port as -p 127.0.0.1:11434:11434; a bare -p 11434:11434 listens on every interface. Exposed Ollama servers are routinely found by internet scans.

  3. Run Open WebUI on localhost and create your admin account

    Bind the interface to localhost too. With pip, run open-webui serve --host 127.0.0.1 (port 8080). With Docker on macOS or Windows, use -p 127.0.0.1:3000:8080 in place of -p 3000:8080 (port 3000). On Linux, use --network=host -e HOST=127.0.0.1 -e OLLAMA_BASE_URL=http://127.0.0.1:11434 so the container reaches Ollama without exposing it (port 8080). Then open it yourself and create the first account: it becomes the admin, and whoever creates it first gets that role.

  4. Add an account for your recipient, then publish the interface

    Open WebUI turns off sign-up after the first account, so create your recipient’s account from the admin panel first, or turn new sign-ups back on and approve their pending account. Then publish the interface, not port 11434, using the port from the previous step. Give it a public name: recipients see it on the link page, and without one a terminal uses the folder you run the command in. Keep the name neutral.

    qurl publish http://127.0.0.1:8080 --name "Model playground"   # Docker on macOS or Windows: :3000

What the recipient sees

The recipient lands on Open WebUI’s login page, signs in with the account you created, and uses the models through it.

More

Replies stream as they do locally: Open WebUI sends them over a WebSocket, and WebSockets pass through a qURL link. A reply still streaming when the session ends (1 hour by default) stops; send a new link.

Troubleshooting

Troubleshooting
If you seeDo this
The page loads but replies never appearIf you set CORS_ALLOW_ORIGIN for Open WebUI, its WebSocket accepts only the origins listed there, and the link’s origin is https://r_….qurl.site. Add it or unset the variable while sharing.
Open WebUI in Docker on Linux can’t reach OllamaUse --network=host with -e HOST=127.0.0.1 -e OLLAMA_BASE_URL=http://127.0.0.1:11434 rather than setting OLLAMA_HOST=0.0.0.0. Without OLLAMA_BASE_URL the container looks for host.docker.internal, which host networking doesn’t provide.
Show 6 more fixes
More troubleshooting
If you seeDo this
qurl publish says the local app is not accepting TCP connectionsStart the app first and check that curl works on the same address. qurl publish connects to localhost as 127.0.0.1, so if your app listens only on IPv6 (on macOS or Linux, lsof -iTCP -sTCP:LISTEN -nP shows [::1]), publish 'http://[::1]:PORT' instead, or start the dev server with --host 127.0.0.1 and publish that address. Neither requires listening on your LAN. Keep the quotes: zsh treats the brackets as a pattern.
The recipient sees “Access link invalid”The link was already used or has expired. Run qurl share again and send the new link.
The recipient sees “Resource not found”The resource was deleted after the link was made. Publish the app again, then run qurl share and send the new link.
publish rejects http://127.0.0.1 with “only HTTPS URLs are allowed”, asks you to log in, or prints no Access: lineYour qURL CLI is out of date. On macOS run brew update, then brew upgrade qurl; elsewhere install the latest release. After updating, qurl --version prints 3.4.1 or later, and every publish is private by default.
publish says this Linux session “can’t reach a systemd user manager”You are in a container or sandbox without a user service manager. Run qurl publish with --foreground; sharing lasts as long as that process runs. Container and CI setup →
publish says “Quota Exceeded” with “protected resource limit reached”, or “Your qURL account has reached a plan limit”You can see this without an account: a device with no account can keep up to 3 active resources, with links that last up to 24 hours. Run qurl list --status active, then qurl delete <CRID> for any you no longer need (it asks you to confirm; --yes skips that). qurl stop keeps the resource, so it does not free a slot.

Frequently Asked Questions

Why not open port 11434?

Ollama has no login of its own, and exposed servers are easy to find. In 2025 Cisco Talos used Shodan to find over 1,100 Ollama servers exposed to the internet, about 20 percent of them hosting models open to unauthorized access.

Can I share the Ollama API itself?

Share the web interface: people chat with your models through it, and Ollama itself stays bound to localhost. Bound there, Ollama accepts only requests addressed to a local name, so publish Open WebUI with qURL rather than port 11434.

Who else can reach my app while the link is open?

Opening the link starts a session for that browser, which lasts 1 hour by default. After a browser opens it, another browser on the same public IP cannot use its access. A script or agent that opens the link without a browser is admitted by its network address instead, which other devices on that public IP share until the session ends. A link admits whoever opens it: the API’s IP and country rules do not apply to the signed links qurl share issues. Keep your app’s own sign-in for anything sensitive.

How do I stop sharing?

Run qurl stop <CRID> to pause serving the app, and qurl start <CRID> to resume it; a stopped app still counts toward your resource limit. qurl delete <CRID> removes the resource for good after asking you to confirm; its CRID can never be shared again.

Publish your app now

Install the CLI, then run one command. No sign-up, no API key.

Install the CLI →

Book a pilot

Tell us what to hide. We’ll scope a pilot.

Enterprise starts with a paid pilot on one application, typically 60 to 90 days, credited in full toward year one if you convert within 60 days. After that, an annual package sized to what you protect, not per seat.