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

[GH-ISSUE #2070] SSL_ERROR_RX_RECORD_TOO_LONG #47711

New Issue
Closed
opened 2026-04-28 05:00:56 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-28 05:00:56 -05:00
Owner
Copy Link

Originally created by @d1nuc0m on GitHub (Jan 19, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/2070

System: ollama 0.1.20 on AlmaLinux 9.3, installed with sudo su && curl https://ollama.ai/install.sh | sh. SELinux does not influence the issue, enabled or not the problem is the same.

  1. I'm using a wildcard certificate (*.example.com) to run ollama on a dedicated VM (ollama.example.com).
  2. Placed cert.pem and key.pem in /usr/share/ollama/.ollama/ssl/ (also tried with ~/.ollama/ssl/)
  3. Certificate has been verified against the key (link), CA has been installed and the certificate has been verified again (link)
  4. Ollama has been bind to all interfaces, service has been reloaded as per FAQ
  5. http://ollama.example.com:11434 returns Ollama is running, while https://ollama.example.com:11434 returns error SSL_ERROR_RX_RECORD_TOO_LONG
  6. I've tried both with certificate only and certificate with intermediates, same result. Note that the same certificate/key pair is in use on other *.example.com subdomains and it works
Originally created by @d1nuc0m on GitHub (Jan 19, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/2070 System: ollama 0.1.20 on AlmaLinux 9.3, installed with `sudo su && curl https://ollama.ai/install.sh | sh`. SELinux does not influence the issue, enabled or not the problem is the same. 1. I'm using a wildcard certificate (*.example.com) to run ollama on a dedicated VM (ollama.example.com). 2. Placed `cert.pem` and `key.pem` in `/usr/share/ollama/.ollama/ssl/` (also tried with `~/.ollama/ssl/`) 3. Certificate has been verified against the key ([link](https://www.ssl247.com/knowledge-base/detail/how-do-i-verify-that-a-private-key-matches-a-certificate-openssl-1527076112539/ka03l0000015hscaay/)), CA has been installed and the certificate has been verified again ([link](https://jermsmit.com/install-a-ca-certificate-on-red-hat-enterprise-linux/)) 4. Ollama has been bind to all interfaces, service has been reloaded as per [FAQ](https://github.com/jmorganca/ollama/blob/main/docs/faq.md#how-do-i-use-ollama-server-environment-variables-on-linux) 5. http://ollama.example.com:11434 returns _Ollama is running_, while https://ollama.example.com:11434 returns error _SSL_ERROR_RX_RECORD_TOO_LONG_ 6. I've tried both with certificate only and certificate with intermediates, same result. Note that the same certificate/key pair is in use on other *.example.com subdomains and it works
GiteaMirror commented 2026-04-28 05:01:00 -05:00
Author
Owner
Copy Link

@mxyng commented on GitHub (Jan 19, 2024):

There is currently no HTTPS support built into Ollama. If you want to use HTTPS, the suggestion is to put Ollama behind a reverse proxy like nginx

<!-- gh-comment-id:1900849612 --> @mxyng commented on GitHub (Jan 19, 2024): There is currently no HTTPS support built into Ollama. If you want to use HTTPS, the suggestion is to put Ollama behind a reverse proxy like nginx
GiteaMirror commented 2026-04-28 05:01:01 -05:00
Author
Owner
Copy Link

@d1nuc0m commented on GitHub (Jan 21, 2024):

There is currently no HTTPS support built into Ollama

Thank you, just seen #1310 , any plans on merging it?

<!-- gh-comment-id:1902663374 --> @d1nuc0m commented on GitHub (Jan 21, 2024): > There is currently no HTTPS support built into Ollama Thank you, just seen #1310 , any plans on merging it?
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
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#47711
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?