Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #3996] [DOCS]: SSL/HTTPS Support #2540

New Issue
Closed
opened 2026-02-22 18:30:08 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:30:08 -05:00
Owner
Copy Link
Copy Source

Originally created by @AndreC10002 on GitHub (Jun 13, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3996

Description

The documentation mentions NGINX as the way to enable SSL/HTTPS. But this can also be configured via the following environment variables:

ENABLE_HTTPS='true'
HTTPS_KEY_PATH=''
HTTPS_CERT_PATH=''

The SSL certificate needs to be generate (auto-signed or otherwise), but this method seems to work well and removes an unnecessary moving part (NGINX).
Unless, there are plans to retire this mechanism I'd suggest documenting it.

Originally created by @AndreC10002 on GitHub (Jun 13, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3996 ### Description The documentation mentions NGINX as the way to enable SSL/HTTPS. But this can also be configured via the following environment variables: ENABLE_HTTPS='true' HTTPS_KEY_PATH='' HTTPS_CERT_PATH='' The SSL certificate needs to be generate (auto-signed or otherwise), but this method seems to work well and removes an unnecessary moving part (NGINX). Unless, there are plans to retire this mechanism I'd suggest documenting it.
yindo added the documentation label 2026-02-22 18:30:08 -05:00
yindo closed this issue 2026-02-22 18:30:08 -05:00
yindo commented 2026-02-22 18:30:08 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jun 13, 2025):

but this method seems to work well and removes an unnecessary moving part (NGINX).

This method does work, but running a reverse proxy is the more "supported" way here since NGINX gives further controls on exposing the instance to the web (caching, routing, rate limiting) and a bunch of other web server admin features we will not build into the actual software.

You can absolutely of course use those ENVs
We have "docs" in the codebase for this here and here - which understandably are not real docs, but more technical people would be able to find and use those ENVs and understand the implications of doing so (like you did)

The option should exist for either crowd depending on their skill and knowledge level, since this is a deployment choice, which is why it exists. That being said, we NGINX and deploying via reverse proxy is generally preferred for most services.

We won't kill this feature ever, mostly because we need it for local SSL testing. Generating the SSL certs and hosting the container using those via the ENV is somewhat more technical (arguably), so "if you know, you know" people can use it. Otherwise, reverse proxy.

@timothycarambat commented on GitHub (Jun 13, 2025): > but this method seems to work well and removes an unnecessary moving part (NGINX). This method does work, but running a reverse proxy is the more "supported" way here since NGINX gives further controls on exposing the instance to the web (caching, routing, rate limiting) and a bunch of other web server admin features we will not build into the actual software. You can absolutely of course use those ENVs We have "docs" in the codebase for this [here](https://github.com/Mintplex-Labs/anything-llm/blob/1752bc261ea1287be3393352b9111599985ac217/server/.env.example#L280-L287) and [here](https://github.com/Mintplex-Labs/anything-llm/blob/1752bc261ea1287be3393352b9111599985ac217/server/utils/boot/index.js#L7-L15) - which understandably are not real docs, but more technical people would be able to find and use those ENVs and understand the implications of doing so (like you did) The option should exist for either crowd depending on their skill and knowledge level, since this is a deployment choice, which is why it exists. That being said, we NGINX and deploying via reverse proxy is _generally preferred_ for most services. We won't kill this feature ever, mostly because we need it for local SSL testing. Generating the SSL certs and hosting the container using those via the ENV is _somewhat_ more technical (arguably), so "if you know, you know" people can use it. Otherwise, reverse proxy.
yindo changed title from [DOCS]: SSL/HTTPS Support to [GH-ISSUE #3996] [DOCS]: SSL/HTTPS Support 2026-06-05 14:47:09 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label documentation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2540
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?