github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-07-15 20:54:54 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #8311] OpenSSL/3.0.13: error:0A00010B:SSL routines::wrong version number #31082

New Issue
Closed
opened 2026-04-22 11:14:24 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-22 11:14:24 -05:00
Owner
Copy Link

Originally created by @crspdavid on GitHub (Jan 5, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/8311

What is the issue?

I've set up SSL for Ollama following these steps:

Configuring SSL

  1. Obtain an SSL certificate and a private key. You can acquire these from a Certificate Authority (CA) or generate a self-signed certificate (not recommended for production use).

  2. Place the certificate and key files in the ~/.ollama/ssl/ directory on your server.

  3. Ensure the files are named cert.pem and key.pem, respectively.

  4. Restart the Ollama server. It will automatically detect the presence of these files and enable HTTPS.

I've generated them using openssl and I also tried a cloudflare cert but it still wouldn't work. Nothing pops up after serving (OLLAMA_HOST=https://0.0.0.0:11434 ollama serve) and http still works the same.

openssl s_client -connect 192.168.1.220:11434 returns:

CONNECTED(00000003)`
40970FDC4E730000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:354:

no peer certificate available

No client certificate CA names sent

SSL handshake has read 5 bytes and written 293 bytes
Verification: OK

New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)

Some people suggested a reverse proxy but I'm reallllllly hoping this would work
Tried it on both Windows Server and Ubuntu Server - same outcome

OS

Linux

GPU

No response

CPU

Intel

Ollama version

0.5.4

Originally created by @crspdavid on GitHub (Jan 5, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/8311 ### What is the issue? I've set up SSL for Ollama following these steps: ### Configuring SSL 1. Obtain an SSL certificate and a private key. You can acquire these from a Certificate Authority (CA) or generate a self-signed certificate (not recommended for production use). 2. Place the certificate and key files in the `~/.ollama/ssl/` directory on your server. 3. Ensure the files are named `cert.pem` and `key.pem`, respectively. 4. Restart the Ollama server. It will automatically detect the presence of these files and enable HTTPS. I've generated them using openssl and I also tried a cloudflare cert but it still wouldn't work. Nothing pops up after serving (OLLAMA_HOST=https://0.0.0.0:11434 ollama serve) and http still works the same. openssl s_client -connect 192.168.1.220:11434 returns: CONNECTED(00000003)` 40970FDC4E730000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:354: no peer certificate available No client certificate CA names sent SSL handshake has read 5 bytes and written 293 bytes Verification: OK New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated Early data was not sent Verify return code: 0 (ok) Some people suggested a reverse proxy but I'm reallllllly hoping this would work Tried it on both Windows Server and Ubuntu Server - same outcome ### OS Linux ### GPU _No response_ ### CPU Intel ### Ollama version 0.5.4
GiteaMirror added the bug label 2026-04-22 11:14:24 -05:00
GiteaMirror commented 2026-04-22 11:14:26 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Jan 5, 2025):

The ollama server doesn't do SSL, a reverse proxy is the way to go.

<!-- gh-comment-id:2571755226 --> @rick-github commented on GitHub (Jan 5, 2025): The ollama server doesn't do SSL, a reverse proxy is the way to go.
GiteaMirror commented 2026-04-22 11:14:26 -05:00
Author
Owner
Copy Link

@crspdavid commented on GitHub (Jan 5, 2025):

The ollama server doesn't do SSL, a reverse proxy is the way to go.

Damn. Thanks.

<!-- gh-comment-id:2571790550 --> @crspdavid commented on GitHub (Jan 5, 2025): > The ollama server doesn't do SSL, a reverse proxy is the way to go. Damn. Thanks.
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 bug
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#31082
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?