[GH-ISSUE #3006] [BUG]: error: addDocumentToNamespace Forbidden access to file: "https://s3.us-west-1.amazonaws.com/public.useanything.com/support/models/Xenova/all-MiniLM-L6-v2/tokenizer.json". #1921

Closed
opened 2026-02-22 18:27:16 -05:00 by yindo · 1 comment
Owner

Originally created by @HeartIsBeat on GitHub (Jan 23, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3006

How are you running AnythingLLM?

Docker (local)

What happened?

Image
fetch website and move to workspace, raise exception:
error: addDocumentToNamespace Forbidden access to file: "https://s3.us-west-1.amazonaws.com/public.useanything.com/support/models/Xenova/all-MiniLM-L6-v2/tokenizer.json".

Are there known steps to reproduce?

No response

Originally created by @HeartIsBeat on GitHub (Jan 23, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3006 ### How are you running AnythingLLM? Docker (local) ### What happened? ![Image](https://github.com/user-attachments/assets/ec90ca31-c366-42ad-ae9d-747642754e27) fetch website and move to workspace, raise exception: error: addDocumentToNamespace Forbidden access to file: "https://s3.us-west-1.amazonaws.com/public.useanything.com/support/models/Xenova/all-MiniLM-L6-v2/tokenizer.json". ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:27:16 -05:00
yindo closed this issue 2026-02-22 18:27:16 -05:00
Author
Owner

@timothycarambat commented on GitHub (Jan 23, 2025):

Update your image - we moved all of our assets to our CDN now because people were abusing our S3 bucket resulting in absurd S3 costs. The only reason you are reaching that endpoint is because HF blocks your IP/geo and we replicate on our bucket as a failover.

This has been live for nearly a month and we disabled it earlier this week fully as the cost was just too much to be reasonable. We knew it would break some peoples forks and deployments, but upgrade to the latest image works the same.

@timothycarambat commented on GitHub (Jan 23, 2025): Update your image - we moved all of our assets to our CDN now because people were abusing our S3 bucket resulting in absurd S3 costs. The only reason you are reaching that endpoint is because HF blocks your IP/geo and we replicate on our bucket as a failover. This has been live for nearly a month and we disabled it earlier this week fully as the cost was just too much to be reasonable. We knew it would break some peoples forks and deployments, but upgrade to the latest image works the same.
yindo changed title from [BUG]: error: addDocumentToNamespace Forbidden access to file: "https://s3.us-west-1.amazonaws.com/public.useanything.com/support/models/Xenova/all-MiniLM-L6-v2/tokenizer.json". to [GH-ISSUE #3006] [BUG]: error: addDocumentToNamespace Forbidden access to file: "https://s3.us-west-1.amazonaws.com/public.useanything.com/support/models/Xenova/all-MiniLM-L6-v2/tokenizer.json". 2026-06-05 14:43:28 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1921