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 #2861] [ISSUE]: Unable to login after a reboot of my container #1820

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

Originally created by @JOduMonT on GitHub (Dec 17, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2861

How are you running AnythingLLM?

Docker (remote machine)

What happened?

Unable to login after a reboot of my container

image

  • ./volumes are owned by: 1000:1000
  • I think users are stocked in sqlite: anythingllm.db
  • I use a local Qdrant as VectorDB: but I believe this DB is just for documents
    image

So if I create a user
then restart my container
I lose access.

If I reset my password with the Recovery Codes
it still doesn't work

PS: I use VaultWarden as Password Manager so yes my cut-and-paste skill are fine.

Are there known steps to reproduce?

spin the docker anythingllm
enable multi-user
shutdown your container
restart yout container

Originally created by @JOduMonT on GitHub (Dec 17, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2861 ### How are you running AnythingLLM? Docker (remote machine) ### What happened? # Unable to login after a reboot of my container ![image](https://github.com/user-attachments/assets/21554a58-a8af-4f26-8f74-3e79f14af224) - ./volumes are owned by: 1000:1000 - I think users are stocked in sqlite: anythingllm.db - I use a local Qdrant as VectorDB: but I believe this DB is just for documents ![image](https://github.com/user-attachments/assets/b2aac979-4193-4dcc-b30b-8756d7c0d60f) So if I create a user then restart my container I lose access. If I reset my password with the Recovery Codes it still doesn't work PS: I use VaultWarden as Password Manager so yes my cut-and-paste skill are fine. ### Are there known steps to reproduce? spin the docker anythingllm enable multi-user shutdown your container restart yout container
yindo added the possible bug label 2026-02-22 18:26:40 -05:00
yindo closed this issue 2026-02-22 18:26:40 -05:00
yindo commented 2026-02-22 18:26:40 -05:00
Author
Owner
Copy Link
Copy Source

@JOduMonT commented on GitHub (Dec 17, 2024):

so at the beginning my container was unable to run when I was binding .env inside it.

now everything is fine;
the main issue was the missing binding of .env

@JOduMonT commented on GitHub (Dec 17, 2024): so at the beginning my container was unable to run when I was binding .env inside it. now everything is fine; the main issue was the missing binding of .env
yindo changed title from [ISSUE]: Unable to login after a reboot of my container to [GH-ISSUE #2861] [ISSUE]: Unable to login after a reboot of my container 2026-06-05 14:42:52 -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#1820
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?