github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 00:51:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #12033] Feature Request: Improved HTTPS/TLS Configuration for macOS App #33750

New Issue
Open
opened 2026-04-22 16:43:54 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-22 16:43:54 -05:00
Owner
Copy Link

Originally created by @bijant92 on GitHub (Aug 22, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/12033

The current process for configuring HTTPS/TLS on the Ollama macOS application is highly unreliable and difficult to implement. The standard macOS method of using a launchd .plist file to set environment variables is not functioning as expected. The .plist file is loaded by the system, but the OLLAMA_SSL_CERT and OLLAMA_SSL_KEY variables are not being passed to the Ollama process, causing the server to continue running on HTTP.

Manually exporting the variables and then launching the application from the Terminal works, but this is not a persistent solution and must be repeated after every system restart. This manual process undermines a key functionality of the macOS application bundle.

Proposed Solution
Please add a reliable and user-friendly method for persistent HTTPS/TLS configuration for the macOS application. Here are a few options for consideration:

  • GUI Configuration (my preference):
    Add an Advanced Settings section to the Settings Panel where users can input the paths to their certificate and key files, the default location being ~/.ollama/certificates . The application would then manage these variables internally.

  • config.yml File:
    Introduce a config.yml file in a standard location (e.g., ~/.ollama/config.yml) that the application automatically reads at startup. This is a robust, common, and well-documented solution for many command-line tools. The configuration could look something like this:

YAML
host: "https://0.0.0.0:11434"
ssl_cert: "/Users/{user}/.ollama/https_certificaten/cert.pem"
ssl_key: "/Users/{user}/.ollama/https_certificaten/key.pem"
  • Improved launchd Implementation: Ensure the application correctly reads and implements environment variables specified in the .plist file. This would make the launchd method a reliable option.
Originally created by @bijant92 on GitHub (Aug 22, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/12033 The current process for configuring HTTPS/TLS on the Ollama macOS application is highly unreliable and difficult to implement. The standard macOS method of using a launchd .plist file to set environment variables is not functioning as expected. The .plist file is loaded by the system, but the OLLAMA_SSL_CERT and OLLAMA_SSL_KEY variables are not being passed to the Ollama process, causing the server to continue running on HTTP. Manually exporting the variables and then launching the application from the Terminal works, but this is not a persistent solution and must be repeated after every system restart. This manual process undermines a key functionality of the macOS application bundle. **Proposed Solution** Please add a reliable and user-friendly method for persistent HTTPS/TLS configuration for the macOS application. Here are a few options for consideration: - **GUI Configuration (my preference):** Add an Advanced Settings section to the Settings Panel where users can input the paths to their certificate and key files, the default location being `~/.ollama/certificates` . The application would then manage these variables internally. - `config.yml` **File**: Introduce a `config.yml` file in a standard location (e.g., `~/.ollama/config.yml`) that the application automatically reads at startup. This is a robust, common, and well-documented solution for many command-line tools. The configuration could look something like this: ``` YAML host: "https://0.0.0.0:11434" ssl_cert: "/Users/{user}/.ollama/https_certificaten/cert.pem" ssl_key: "/Users/{user}/.ollama/https_certificaten/key.pem" ``` - **Improved** `launchd` **Implementation**: Ensure the application correctly reads and implements environment variables specified in the .plist file. This would make the launchd method a reliable option.
GiteaMirror added the feature request label 2026-04-22 16:43:54 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#33750
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?