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 #3608] [BUG]: Issue Installing SSL Certificate with AnythingLLM Docker Setup #2331

New Issue
Closed
opened 2026-02-22 18:29:12 -05:00 by yindo · 2 comments
yindo commented 2026-02-22 18:29:12 -05:00
Owner
Copy Link
Copy Source

Originally created by @spyroskotsakis on GitHub (Apr 7, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3608

How are you running AnythingLLM?

Docker (remote machine)

What happened?

Hello
I'm trying to install a certificate I've already generated, it's stored on the server at the path below. I'm running AnythingLLM using Docker, but I'm having trouble getting it to work with the setup.
cert path: /etc/letsencrypt/live/domain.com/

ENABLE_HTTPS="true"
HTTPS_CERT_PATH="sslcert/fullchain.pem"
HTTPS_KEY_PATH="sslcert/privkey.pem"

Is there a specific way to include the certificate that I might be missing? I've also mounted the certificate folder in the Docker Compose file like this:

  • /etc/letsencrypt/live/domain.com:/app/server/sslcert:ro

Would really appreciate your help on this!
Thanks a lot
Spyros

Are there known steps to reproduce?

No response

Originally created by @spyroskotsakis on GitHub (Apr 7, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3608 ### How are you running AnythingLLM? Docker (remote machine) ### What happened? Hello I'm trying to install a certificate I've already generated, it's stored on the server at the path below. I'm running AnythingLLM using Docker, but I'm having trouble getting it to work with the setup. cert path: /etc/letsencrypt/live/domain.com/ ENABLE_HTTPS="true" HTTPS_CERT_PATH="sslcert/fullchain.pem" HTTPS_KEY_PATH="sslcert/privkey.pem" Is there a specific way to include the certificate that I might be missing? I've also mounted the certificate folder in the Docker Compose file like this: - /etc/letsencrypt/live/domain.com:/app/server/sslcert:ro Would really appreciate your help on this! Thanks a lot Spyros ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:29:12 -05:00
yindo closed this issue 2026-02-22 18:29:12 -05:00
yindo commented 2026-02-22 18:29:12 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Apr 7, 2025):

This is a configuration issue, not a bug with AnythingLLM. That being said, you should check that while the container is running that you can even ls /app/server/sslcert from within the container. If not then you know your bind is not working.

It is also worth noting that with certbot you typically run this as root and the /etc/letsencrypt/* folder is not accessible by non-root, which is what your container is likely running as - so the bind silently fails or cannot read from that directory once mounted.

This can be fixed by chmod -R /etc/letsencrypt/live/domain.com but that might not be recommended to do, however it is up to you. The bind likely is not the issue and instead is the file permissions

@timothycarambat commented on GitHub (Apr 7, 2025): This is a configuration issue, not a bug with AnythingLLM. That being said, you should check that while the container is running that you can even `ls /app/server/sslcert` from within the container. If not then you know your bind is not working. It is also worth noting that with `certbot` you typically run this as root and the `/etc/letsencrypt/*` folder is **not accessible** by non-root, which is what your container is likely running as - so the bind silently fails or cannot read from that directory once mounted. This can be fixed by `chmod -R /etc/letsencrypt/live/domain.com` but that might not be recommended to do, however it is up to you. The bind likely is not the issue and instead is the file permissions
yindo commented 2026-02-22 18:29:12 -05:00
Author
Owner
Copy Link
Copy Source

@spyroskotsakis commented on GitHub (Apr 7, 2025):

Thanks a lot for the clarification!
I wasn't able to mount the certificate folder and grant access directly. I kept running into issues. So instead, I created a new folder and copied the certificates there. Not the ideal setup, but it works for now.
Really appreciate you pointing out the permission issue. I had completely overlooked that.

@spyroskotsakis commented on GitHub (Apr 7, 2025): Thanks a lot for the clarification! I wasn't able to mount the certificate folder and grant access directly. I kept running into issues. So instead, I created a new folder and copied the certificates there. Not the ideal setup, but it works for now. Really appreciate you pointing out the permission issue. I had completely overlooked that.
yindo changed title from [BUG]: Issue Installing SSL Certificate with AnythingLLM Docker Setup to [GH-ISSUE #3608] [BUG]: Issue Installing SSL Certificate with AnythingLLM Docker Setup 2026-06-05 14:45:57 -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 possible bug
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#2331
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?