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

[GH-ISSUE #4233] [BUG]: no users available to assign #2692

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

Originally created by @marcoben73 on GitHub (Aug 1, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4233

How are you running AnythingLLM?

Docker (local)

What happened?

We are testing AnythingLLM, just updated to version v1.8.2
I've users in my instance
Image

Suddenly I can't find user any more when I try to assign users to workspaces
Image

Last week I was able to add members to workspaces, here an example
Image

No errors in logs

[collector] info: [TikTokenTokenizer] Initialized new TikTokenTokenizer instance.
[collector] info: Collector hot directory and tmp storage wiped!
[collector] info: Document processor app listening on port 8888
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma

✔ Generated Prisma Client (v5.3.1) to ./node_modules/@prisma/client in 174ms

Start using Prisma Client in Node.js (See: https://pris.ly/d/client)

import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()

or start using Prisma Client at the edge (See: https://pris.ly/d/accelerate)

import { PrismaClient } from '@prisma/client/edge'
const prisma = new PrismaClient()


See other ways of importing Prisma Client: http://pris.ly/d/importing-client

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "anythingllm.db" at "file:../storage/anythingllm.db"

32 migrations found in prisma/migrations


No pending migrations to apply.
┌─────────────────────────────────────────────────────────┐
│  Update available 5.3.1 -> 6.13.0                       │
│                                                         │
│  This is a major update - please follow the guide at    │
│  https://pris.ly/d/major-version-upgrade                │
│                                                         │
│  Run the following to update                            │
│    npm i --save-dev prisma@latest                       │
│    npm i @prisma/client@latest                          │
└─────────────────────────────────────────────────────────┘
[backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data.
[backend] info: [TokenManager] Initialized new TokenManager instance for model: gpt-3.5-turbo
[backend] info: [TokenManager] Returning existing instance for model: gpt-3.5-turbo
[backend] info: [TELEMETRY ENABLED] Anonymous Telemetry enabled. Telemetry helps Mintplex Labs Inc improve AnythingLLM.
[backend] info: prisma:info Starting a sqlite pool with 33 connections.
[backend] info: [TELEMETRY SENT] {"event":"server_boot","distinctId":"21275e93-5867-43c2-9bb7-378c76d2ccd8","properties":{"commit":"--","runtime":"docker"}}
[backend] info: [CommunicationKey] RSA key pair generated for signed payloads within AnythingLLM services.
[backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data.
[backend] info: Primary server in HTTP mode listening on port 3001
[backend] info: [BackgroundWorkerService] Feature is not enabled and will not be started.
[backend] info: [MetaGenerator] fetching custom meta tag settings...

Are there known steps to reproduce?

No response

Originally created by @marcoben73 on GitHub (Aug 1, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4233 ### How are you running AnythingLLM? Docker (local) ### What happened? We are testing AnythingLLM, just updated to version v1.8.2 I've users in my instance <img width="1235" height="364" alt="Image" src="https://github.com/user-attachments/assets/dd6f0811-9b03-43d4-8866-ca29498b29c6" /> Suddenly I can't find user any more when I try to assign users to workspaces <img width="1538" height="723" alt="Image" src="https://github.com/user-attachments/assets/4ff9c586-3304-4ea3-b48d-177866be0cc1" /> Last week I was able to add members to workspaces, here an example <img width="1051" height="281" alt="Image" src="https://github.com/user-attachments/assets/014bb2ea-d7e6-47d8-b471-e6f007e82585" /> No errors in logs ``` [collector] info: [TikTokenTokenizer] Initialized new TikTokenTokenizer instance. [collector] info: Collector hot directory and tmp storage wiped! [collector] info: Document processor app listening on port 8888 Environment variables loaded from .env Prisma schema loaded from prisma/schema.prisma ✔ Generated Prisma Client (v5.3.1) to ./node_modules/@prisma/client in 174ms Start using Prisma Client in Node.js (See: https://pris.ly/d/client) import { PrismaClient } from '@prisma/client' const prisma = new PrismaClient() or start using Prisma Client at the edge (See: https://pris.ly/d/accelerate) import { PrismaClient } from '@prisma/client/edge' const prisma = new PrismaClient() See other ways of importing Prisma Client: http://pris.ly/d/importing-client Environment variables loaded from .env Prisma schema loaded from prisma/schema.prisma Datasource "db": SQLite database "anythingllm.db" at "file:../storage/anythingllm.db" 32 migrations found in prisma/migrations No pending migrations to apply. ┌─────────────────────────────────────────────────────────┐ │ Update available 5.3.1 -> 6.13.0 │ │ │ │ This is a major update - please follow the guide at │ │ https://pris.ly/d/major-version-upgrade │ │ │ │ Run the following to update │ │ npm i --save-dev prisma@latest │ │ npm i @prisma/client@latest │ └─────────────────────────────────────────────────────────┘ [backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data. [backend] info: [TokenManager] Initialized new TokenManager instance for model: gpt-3.5-turbo [backend] info: [TokenManager] Returning existing instance for model: gpt-3.5-turbo [backend] info: [TELEMETRY ENABLED] Anonymous Telemetry enabled. Telemetry helps Mintplex Labs Inc improve AnythingLLM. [backend] info: prisma:info Starting a sqlite pool with 33 connections. [backend] info: [TELEMETRY SENT] {"event":"server_boot","distinctId":"21275e93-5867-43c2-9bb7-378c76d2ccd8","properties":{"commit":"--","runtime":"docker"}} [backend] info: [CommunicationKey] RSA key pair generated for signed payloads within AnythingLLM services. [backend] info: [EncryptionManager] Loaded existing key & salt for encrypting arbitrary data. [backend] info: Primary server in HTTP mode listening on port 3001 [backend] info: [BackgroundWorkerService] Feature is not enabled and will not be started. [backend] info: [MetaGenerator] fetching custom meta tag settings... ``` ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:30:49 -05:00
yindo closed this issue 2026-02-22 18:30:49 -05:00
yindo commented 2026-02-22 18:30:50 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Aug 1, 2025):

Managers can already see all workspaces, no need to assign them. Default is the only role requiring assignment

@timothycarambat commented on GitHub (Aug 1, 2025): Managers can already see all workspaces, no need to assign them. Default is the only role requiring assignment
yindo changed title from [BUG]: no users available to assign to [GH-ISSUE #4233] [BUG]: no users available to assign 2026-06-05 14:47:59 -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#2692
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?