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 #4152] [BUG]: Failed to save LLM settings: Unexpected token 'I', "Internal S"... is not valid JSON #2643

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

Originally created by @jauser2 on GitHub (Jul 15, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4152

How are you running AnythingLLM?

Docker (local)

What happened?

Hi Community,

I'm trying unsuccessfully to run the docker (built) configuration from https://github.com/Mintplex-Labs/anything-llm.

My configuration

  • Host machine: Windows 10
  • Virtualization engine: Virtualbox v7.1.4
  • Guest machine:
    * 4 vcores
    * 8 Gb RAM
    * Ubuntu server 24.04
    * Docker v28.3.2
  • Ollama server is hosted on host machine at 127.0.0.1:11434
  • Browser used for frontend: Brave v1.80.120

The behaviour.
The frontend is loading fine, but when I try to connect the Ollama server, the following error is notified:

Image

If ignoring that error and trying to chat with Ollama, I got the following error:

Image

What I then did.
Seen from the guest machine, the Ollama server sits at 10.0.2.2:11434.

I verified it with a curl request.

Image

In other JS apps issues, it's been reported that the problem may arise when nodejs version in the host machine is different from the one in the guest machine (here my docker container). I checked a version 18.20 in my anythingllm container and updated accordingly nodejs in my VM.

Unfortunately no change.

Does anybody have any idea?

Are there known steps to reproduce?

No response

Originally created by @jauser2 on GitHub (Jul 15, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4152 ### How are you running AnythingLLM? Docker (local) ### What happened? Hi Community, I'm trying unsuccessfully to run the docker (built) configuration from https://github.com/Mintplex-Labs/anything-llm. **My configuration** - Host machine: Windows 10 - Virtualization engine: Virtualbox v7.1.4 - Guest machine: * 4 vcores * 8 Gb RAM * Ubuntu server 24.04 * Docker v28.3.2 - Ollama server is hosted on host machine at 127.0.0.1:11434 - Browser used for frontend: Brave v1.80.120 **The behaviour.** The frontend is loading fine, but when I try to connect the Ollama server, the following error is notified: <img width="416" height="163" alt="Image" src="https://github.com/user-attachments/assets/c229e410-1eed-432f-8a73-4a24fc854e6c" /> If ignoring that error and trying to chat with Ollama, I got the following error: <img width="684" height="350" alt="Image" src="https://github.com/user-attachments/assets/5ffa8e85-1f5f-4c89-aff5-51eb5fdd09e7" /> **What I then did.** Seen from the guest machine, the Ollama server sits at 10.0.2.2:11434. I verified it with a curl request. <img width="1015" height="124" alt="Image" src="https://github.com/user-attachments/assets/501f2a5b-d518-43b6-8a36-0bb88a3ae1cc" /> In other JS apps issues, it's been reported that the problem may arise when nodejs version in the host machine is different from the one in the guest machine (here my docker container). I checked a version 18.20 in my anythingllm container and updated accordingly nodejs in my VM. Unfortunately no change. Does anybody have any idea? ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:30:34 -05:00
yindo closed this issue 2026-02-22 18:30:34 -05:00
yindo commented 2026-02-22 18:30:35 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 15, 2025):

The backend server is not running in your container. You should be able to rebuild the container in the root repo with just docker build -f docker/Dockerfile .

Then when the container is live just run
https://docs.anythingllm.com/installation-docker/quickstart

Obviously, with your image instead of the prebuilt one. One thing that might be missing, depending on how you are building the container it very well might be trying to use local .env files stored and copying them to the conatiner. In which case be sure to run yarn setup so the proper .env files are clones to their respective locations.

@timothycarambat commented on GitHub (Jul 15, 2025): The backend server is not running in your container. You should be able to rebuild the container in the root repo with just `docker build -f docker/Dockerfile .` Then when the container is live just run https://docs.anythingllm.com/installation-docker/quickstart Obviously, with your image instead of the prebuilt one. One thing that might be missing, depending on how you are building the container it very well might be trying to use local `.env` files stored and copying them to the conatiner. In which case be sure to run `yarn setup` so the proper `.env` files are clones to their respective locations.
yindo changed title from [BUG]: Failed to save LLM settings: Unexpected token 'I', "Internal S"... is not valid JSON to [GH-ISSUE #4152] [BUG]: Failed to save LLM settings: Unexpected token 'I', "Internal S"... is not valid JSON 2026-06-05 14:47:42 -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#2643
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?