[GH-ISSUE #4839] [BUG]: failed to save LLM settings: failed to fetch #3046

Closed
opened 2026-02-22 18:32:24 -05:00 by yindo · 7 comments
Owner

Originally created by @robert-winkler on GitHub (Jan 8, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4839

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

I installed the Linux AppImage, using the installer.sh script on Fedora 43.

I tried connecting to my Groq.com and Mistral.ai models, using API keys. In the case of Groq. com, I can select between models, but when trying to move forward, I get the error: failed to save LLM settings: failed to fetch.

The same happens with Mistral.ai; however, I cannot even select between models.

Both AI API providers work on my Open WebUI instance.

I'm using version v1.9.1

Are there known steps to reproduce?

No response

Originally created by @robert-winkler on GitHub (Jan 8, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4839 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? I installed the Linux AppImage, using the installer.sh script on Fedora 43. I tried connecting to my Groq.com and Mistral.ai models, using API keys. In the case of Groq. com, I can select between models, but when trying to move forward, I get the error: failed to save LLM settings: failed to fetch. The same happens with Mistral.ai; however, I cannot even select between models. Both AI API providers work on my Open WebUI instance. I'm using version v1.9.1 ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:32:24 -05:00
yindo closed this issue 2026-02-22 18:32:24 -05:00
Author
Owner

@timothycarambat commented on GitHub (Jan 8, 2026):

In order to see the real issue you will need to pull the logs which are in the storage folder: https://docs.anythingllm.com/installation-desktop/storage#where-is-my-data-located

That error typically indicates that the permissions are invalid to create the storage folder and so the backend crashes

@timothycarambat commented on GitHub (Jan 8, 2026): In order to see the real issue you will need to pull the logs which are in the storage folder: https://docs.anythingllm.com/installation-desktop/storage#where-is-my-data-located That error typically indicates that the permissions are invalid to create the storage folder and so the backend crashes
Author
Owner

@robert-winkler commented on GitHub (Jan 9, 2026):

Hi, I checked the ownership and permissions in the
~/.config/anythingllm-desktop/storage/

And they seemed correct. To make sure that missing
access/reading/writing permissions are the problem, I changed the
permissions of all files to 777:

chmod -Rvf 777 anythingllm-desktop/

The problems persist.

tail backend-2026-01-09.log
{"level":"info","message":"OllamaAPI offline - retrying.
1/3","service":"backend"}
{"level":"info","message":"\u001b[36m[AnythingLLMOllama]\u001b[0m
Applying custom fetch w/timeout of 10 minutes.","service":"backend"}
{"level":"info","message":"\u001b[36m[NativeEmbedder]\u001b[0m
Initialized Xenova/all-MiniLM-L6-v2","service":"backend"}
{"level":"info","message":"\u001b[36m[AnythingLLMOllama]\u001b[0m
initialized with model: undefined","service":"backend"}
{"level":"info","message":"\u001b[33m[83780:84021]\u001b[0m: No direct
uploads path found - exiting.","service":"backend"}
{"level":"info","message":"\u001b[33m[83780:84021]\u001b[0m: No direct
uploads path found -
exiting.","origin":"cleanup-orphan-documents","service":"bg-worker"}
{"level":"warn","message":"Child process exited with code 0 and signal
null","service":"backend"}
{"level":"info","message":"Worker for job "cleanup-orphan-documents"
exited with code 0","service":"backend"}
{"level":"info","message":"EmbeddingEngine changed from undefined to
native - resetting undefined namespaces","service":"backend"}
{"level":"info","message":"\u001b[32m[Event Logged]\u001b[0m -
workspace_vectors_reset","service":"backend"}

tail collector-2026-01-09.log
{"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m
Initialized new TikTokenTokenizer instance.","service":"collector"}
{"level":"info","message":"Collector hot directory and tmp storage
wiped!","service":"collector"}
{"level":"info","message":"[production] AnythingLLM Standalone Document
processor listening on port 8888.","service":"collector"}
{"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m
Initialized new TikTokenTokenizer instance.","service":"collector"}
{"level":"info","message":"Collector hot directory and tmp storage
wiped!","service":"collector"}
{"level":"info","message":"[production] AnythingLLM Standalone Document
processor listening on port 8888.","service":"collector"}

any idea?

On 1/8/26 18:31, Timothy Carambat wrote:

timothycarambat left a comment (Mintplex-Labs/anything-llm#4839)
https://github.com/Mintplex-Labs/anything-llm/issues/4839#issuecomment-3726538348

In order to see the real issue you will need to pull the logs which
are in the storage folder:
https://docs.anythingllm.com/installation-desktop/storage#where-is-my-data-located

That error typically indicates that the permissions are invalid to
create the storage folder and so the backend crashes


Reply to this email directly, view it on GitHub
https://github.com/Mintplex-Labs/anything-llm/issues/4839#issuecomment-3726538348,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACMIC3JSGY4F4PURC2NFYHL4F3ZFTAVCNFSM6AAAAACRDWABPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMRWGUZTQMZUHA.
You are receiving this because you authored the thread.Message ID:
@.***>

@robert-winkler commented on GitHub (Jan 9, 2026): Hi, I checked the ownership and permissions in the ~/.config/anythingllm-desktop/storage/ And they seemed correct. To make sure that missing access/reading/writing permissions are the problem, I changed the permissions of all files to 777: chmod -Rvf 777 anythingllm-desktop/ The problems persist. tail backend-2026-01-09.log {"level":"info","message":"OllamaAPI offline - retrying. 1/3","service":"backend"} {"level":"info","message":"\u001b[36m[AnythingLLMOllama]\u001b[0m Applying custom fetch w/timeout of 10 minutes.","service":"backend"} {"level":"info","message":"\u001b[36m[NativeEmbedder]\u001b[0m Initialized Xenova/all-MiniLM-L6-v2","service":"backend"} {"level":"info","message":"\u001b[36m[AnythingLLMOllama]\u001b[0m initialized with model: undefined","service":"backend"} {"level":"info","message":"\u001b[33m[83780:84021]\u001b[0m: No direct uploads path found - exiting.","service":"backend"} {"level":"info","message":"\u001b[33m[83780:84021]\u001b[0m: No direct uploads path found - exiting.","origin":"cleanup-orphan-documents","service":"bg-worker"} {"level":"warn","message":"Child process exited with code 0 and signal null","service":"backend"} {"level":"info","message":"Worker for job \"cleanup-orphan-documents\" exited with code 0","service":"backend"} {"level":"info","message":"EmbeddingEngine changed from undefined to native - resetting undefined namespaces","service":"backend"} {"level":"info","message":"\u001b[32m[Event Logged]\u001b[0m - workspace_vectors_reset","service":"backend"} tail collector-2026-01-09.log {"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Initialized new TikTokenTokenizer instance.","service":"collector"} {"level":"info","message":"Collector hot directory and tmp storage wiped!","service":"collector"} {"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"} {"level":"info","message":"\u001b[35m[TikTokenTokenizer]\u001b[0m Initialized new TikTokenTokenizer instance.","service":"collector"} {"level":"info","message":"Collector hot directory and tmp storage wiped!","service":"collector"} {"level":"info","message":"[production] AnythingLLM Standalone Document processor listening on port 8888.","service":"collector"} any idea? On 1/8/26 18:31, Timothy Carambat wrote: > *timothycarambat* left a comment (Mintplex-Labs/anything-llm#4839) > <https://github.com/Mintplex-Labs/anything-llm/issues/4839#issuecomment-3726538348> > > In order to see the real issue you will need to pull the logs which > are in the storage folder: > https://docs.anythingllm.com/installation-desktop/storage#where-is-my-data-located > > That error typically indicates that the permissions are invalid to > create the storage folder and so the backend crashes > > — > Reply to this email directly, view it on GitHub > <https://github.com/Mintplex-Labs/anything-llm/issues/4839#issuecomment-3726538348>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACMIC3JSGY4F4PURC2NFYHL4F3ZFTAVCNFSM6AAAAACRDWABPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMRWGUZTQMZUHA>. > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Author
Owner

@timothycarambat commented on GitHub (Jan 9, 2026):

🤔 That is weird. If you just boot up the application and then open a browser or curl localhost:30001/api/ping do you get a 200OK?

The failure to save is quite odd. Is it possible you have another process using 3001 and our frontend see that and tries to send to that endpoint which obviously fails.

sudo lsof -i :3001

The backend log should announce the port at the top of the log and that is trimmed in that output, but its 3001 by default and it should port-hunt in a similar range if 3001 is occupied.

@timothycarambat commented on GitHub (Jan 9, 2026): 🤔 That is weird. If you just boot up the application and then open a browser or curl localhost:30001/api/ping do you get a 200OK? The failure to save is quite odd. Is it possible you have another process using 3001 and our frontend see _that_ and tries to send to that endpoint which obviously fails. `sudo lsof -i :3001` The backend log should announce the port at the top of the log and that is trimmed in that output, but its 3001 by default and it should port-hunt in a similar range if 3001 is occupied.
Author
Owner

@robert-winkler commented on GitHub (Jan 9, 2026):

Well, it give me:
sudo lsof -i :3001
[sudo] password for rob:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
anythingl 104204 rob 39u IPv4 875715 0t0 TCP localhost:origo-native (LISTEN)

Robert Winkler - Chat @ Spike [3glcxf]

On January 9, 2026 at 18:30 GMT, Timothy Carambat @.***> wrote:

timothycarambat left a comment (Mintplex-Labs/anything-llm#4839)

🤔 That is weird. If you just boot up the application and then open a browser or curl localhost:30001/api/ping do you get a 200OK?

The failure to save is quite odd. Is it possible you have another process using 3001 and our frontend see that and tries to send to that endpoint which obviously fails.

sudo lsof -i :3001

The backend log should announce the port at the top of the log and that is trimmed in that output, but its 3001 by default and it should port-hunt in a similar range if 3001 is occupied.


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@robert-winkler commented on GitHub (Jan 9, 2026): Well, it give me: sudo lsof -i :3001 [sudo] password for rob: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME anythingl 104204 rob 39u IPv4 875715 0t0 TCP localhost:origo-native (LISTEN) [Robert Winkler - Chat @ Spike](https://spikenow.com/r/a/?ref=spike-organic-signature&_ts=3glcxf) [3glcxf] On January 9, 2026 at 18:30 GMT, Timothy Carambat ***@***.***> wrote: timothycarambat left a comment [(Mintplex-Labs/anything-llm#4839)](https://github.com/Mintplex-Labs/anything-llm/issues/4839#issuecomment-3730097287) 🤔 That is weird. If you just boot up the application and then open a browser or curl localhost:30001/api/ping do you get a 200OK? The failure to save is quite odd. Is it possible you have another process using 3001 and our frontend see that and tries to send to that endpoint which obviously fails. sudo lsof -i :3001 The backend log should announce the port at the top of the log and that is trimmed in that output, but its 3001 by default and it should port-hunt in a similar range if 3001 is occupied. — Reply to this email directly, [view it on GitHub](https://github.com/Mintplex-Labs/anything-llm/issues/4839#issuecomment-3730097287), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ACMIC3N3GTW4JPN4YG54VXD4F7XVHAVCNFSM6AAAAACRDWABPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZQGA4TOMRYG4). You are receiving this because you authored the thread.Message ID: ***@***.***>
Author
Owner

@robert-winkler commented on GitHub (Jan 9, 2026):

I also tried to start de AppImage and configure a local ollama model.
Again, an error occurs:
[OllamaProcessManager] Ollama will bind on port 11434 when booted.
[OllamaProcessManager] Creating Ollama models folder in application storage. {
destination: '/home/rob/.config/anythingllm-desktop/storage/models/ollama'
}
[ManualBrowser] Listening for IPC messages from main renderer process!
[OllamaProcessManager] SINGLETON LOCK: Using existing OllamaProcessManager.
[OllamaProcessManager] [nix] Ollama subprocess running. Port 11434. PID 123392.
[123123:0109/151302.308378:ERROR:browser_main_loop.cc(278)] GLib-GObject: ../gobject/gsignal.c:2700: instance '0x212802bdd400' has no handler with id '4780'

Robert Winkler - Chat @ Spike [3gljf2]

On January 9, 2026 at 18:55 GMT, Robert Winkler @.***> wrote:

Well, it give me:
sudo lsof -i :3001
[sudo] password for rob:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
anythingl 104204 rob 39u IPv4 875715 0t0 TCP localhost:origo-native (LISTEN)

Robert Winkler - Chat @ Spike [3glcxf]

On January 9, 2026 at 18:30 GMT, Timothy Carambat @.***> wrote:

timothycarambat left a comment (Mintplex-Labs/anything-llm#4839)

🤔 That is weird. If you just boot up the application and then open a browser or curl localhost:30001/api/ping do you get a 200OK?

The failure to save is quite odd. Is it possible you have another process using 3001 and our frontend see that and tries to send to that endpoint which obviously fails.

sudo lsof -i :3001

The backend log should announce the port at the top of the log and that is trimmed in that output, but its 3001 by default and it should port-hunt in a similar range if 3001 is occupied.


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@robert-winkler commented on GitHub (Jan 9, 2026): I also tried to start de AppImage and configure a local ollama model. Again, an error occurs: [OllamaProcessManager] Ollama will bind on port 11434 when booted. [OllamaProcessManager] Creating Ollama models folder in application storage. { destination: '/home/rob/.config/anythingllm-desktop/storage/models/ollama' } [ManualBrowser] Listening for IPC messages from main renderer process! [OllamaProcessManager] SINGLETON LOCK: Using existing OllamaProcessManager. [OllamaProcessManager] [nix] Ollama subprocess running. Port 11434. PID 123392. [123123:0109/151302.308378:ERROR:browser_main_loop.cc(278)] GLib-GObject: ../gobject/gsignal.c:2700: instance '0x212802bdd400' has no handler with id '4780' [Robert Winkler - Chat @ Spike](https://spikenow.com/r/a/?ref=spike-organic-signature&_ts=3gljf2) [3gljf2] On January 9, 2026 at 18:55 GMT, Robert Winkler ***@***.***> wrote: Well, it give me: sudo lsof -i :3001 [sudo] password for rob: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME anythingl 104204 rob 39u IPv4 875715 0t0 TCP localhost:origo-native (LISTEN) [Robert Winkler - Chat @ Spike](https://spikenow.com/r/a/?ref=spike-organic-signature&_ts=3glcxf) [3glcxf] On January 9, 2026 at 18:30 GMT, Timothy Carambat ***@***.***> wrote: timothycarambat left a comment [(Mintplex-Labs/anything-llm#4839)](https://github.com/Mintplex-Labs/anything-llm/issues/4839#issuecomment-3730097287) 🤔 That is weird. If you just boot up the application and then open a browser or curl localhost:30001/api/ping do you get a 200OK? The failure to save is quite odd. Is it possible you have another process using 3001 and our frontend see that and tries to send to that endpoint which obviously fails. sudo lsof -i :3001 The backend log should announce the port at the top of the log and that is trimmed in that output, but its 3001 by default and it should port-hunt in a similar range if 3001 is occupied. — Reply to this email directly, [view it on GitHub](https://github.com/Mintplex-Labs/anything-llm/issues/4839#issuecomment-3730097287), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ACMIC3N3GTW4JPN4YG54VXD4F7XVHAVCNFSM6AAAAACRDWABPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZQGA4TOMRYG4). You are receiving this because you authored the thread.Message ID: ***@***.***>
Author
Owner

@robert-winkler commented on GitHub (Jan 9, 2026):

I intended to start the docker image according to the instructions (I have various docker instances running in production, e.g. Open WebUI). However, even if there is a anythinllm container running and bound to 3001:3001, the web GUI is not accesible.

Robert Winkler - Chat @ Spike [3gljhx]

On January 9, 2026 at 21:15 GMT, Robert Winkler @.***> wrote:

I also tried to start de AppImage and configure a local ollama model.
Again, an error occurs:
[OllamaProcessManager] Ollama will bind on port 11434 when booted.
[OllamaProcessManager] Creating Ollama models folder in application storage. {
destination: '/home/rob/.config/anythingllm-desktop/storage/models/ollama'
}
[ManualBrowser] Listening for IPC messages from main renderer process!
[OllamaProcessManager] SINGLETON LOCK: Using existing OllamaProcessManager.
[OllamaProcessManager] [nix] Ollama subprocess running. Port 11434. PID 123392.
[123123:0109/151302.308378:ERROR:browser_main_loop.cc(278)] GLib-GObject: ../gobject/gsignal.c:2700: instance '0x212802bdd400' has no handler with id '4780'

Robert Winkler - Chat @ Spike [3gljf2]

On January 9, 2026 at 18:55 GMT, Robert Winkler @.***> wrote:

Well, it give me:
sudo lsof -i :3001
[sudo] password for rob:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
anythingl 104204 rob 39u IPv4 875715 0t0 TCP localhost:origo-native (LISTEN)

Robert Winkler - Chat @ Spike [3glcxf]

On January 9, 2026 at 18:30 GMT, Timothy Carambat @.***> wrote:

timothycarambat left a comment (Mintplex-Labs/anything-llm#4839)

🤔 That is weird. If you just boot up the application and then open a browser or curl localhost:30001/api/ping do you get a 200OK?

The failure to save is quite odd. Is it possible you have another process using 3001 and our frontend see that and tries to send to that endpoint which obviously fails.

sudo lsof -i :3001

The backend log should announce the port at the top of the log and that is trimmed in that output, but its 3001 by default and it should port-hunt in a similar range if 3001 is occupied.


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@robert-winkler commented on GitHub (Jan 9, 2026): I intended to start the docker image according to the instructions (I have various docker instances running in production, e.g. Open WebUI). However, even if there is a anythinllm container running and bound to 3001:3001, the web GUI is not accesible. [Robert Winkler - Chat @ Spike](https://spikenow.com/r/a/?ref=spike-organic-signature&_ts=3gljhx) [3gljhx] On January 9, 2026 at 21:15 GMT, Robert Winkler ***@***.***> wrote: I also tried to start de AppImage and configure a local ollama model. Again, an error occurs: [OllamaProcessManager] Ollama will bind on port 11434 when booted. [OllamaProcessManager] Creating Ollama models folder in application storage. { destination: '/home/rob/.config/anythingllm-desktop/storage/models/ollama' } [ManualBrowser] Listening for IPC messages from main renderer process! [OllamaProcessManager] SINGLETON LOCK: Using existing OllamaProcessManager. [OllamaProcessManager] [nix] Ollama subprocess running. Port 11434. PID 123392. [123123:0109/151302.308378:ERROR:browser_main_loop.cc(278)] GLib-GObject: ../gobject/gsignal.c:2700: instance '0x212802bdd400' has no handler with id '4780' [Robert Winkler - Chat @ Spike](https://spikenow.com/r/a/?ref=spike-organic-signature&_ts=3gljf2) [3gljf2] On January 9, 2026 at 18:55 GMT, Robert Winkler ***@***.***> wrote: Well, it give me: sudo lsof -i :3001 [sudo] password for rob: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME anythingl 104204 rob 39u IPv4 875715 0t0 TCP localhost:origo-native (LISTEN) [Robert Winkler - Chat @ Spike](https://spikenow.com/r/a/?ref=spike-organic-signature&_ts=3glcxf) [3glcxf] On January 9, 2026 at 18:30 GMT, Timothy Carambat ***@***.***> wrote: timothycarambat left a comment [(Mintplex-Labs/anything-llm#4839)](https://github.com/Mintplex-Labs/anything-llm/issues/4839#issuecomment-3730097287) 🤔 That is weird. If you just boot up the application and then open a browser or curl localhost:30001/api/ping do you get a 200OK? The failure to save is quite odd. Is it possible you have another process using 3001 and our frontend see that and tries to send to that endpoint which obviously fails. sudo lsof -i :3001 The backend log should announce the port at the top of the log and that is trimmed in that output, but its 3001 by default and it should port-hunt in a similar range if 3001 is occupied. — Reply to this email directly, [view it on GitHub](https://github.com/Mintplex-Labs/anything-llm/issues/4839#issuecomment-3730097287), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ACMIC3N3GTW4JPN4YG54VXD4F7XVHAVCNFSM6AAAAACRDWABPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZQGA4TOMRYG4). You are receiving this because you authored the thread.Message ID: ***@***.***>
Author
Owner

@robert-winkler commented on GitHub (Jan 9, 2026):

BTW: I have the same problem of "failed to save LLM settings: failed to fetch" with the AnythingLLM AppImage on Debian.

Robert Winkler - Chat @ Spike [3gllc3]

On January 9, 2026 at 21:17 GMT, Robert Winkler @.***> wrote:

I intended to start the docker image according to the instructions (I have various docker instances running in production, e.g. Open WebUI). However, even if there is a anythinllm container running and bound to 3001:3001, the web GUI is not accesible.

Robert Winkler - Chat @ Spike [3gljhx]

On January 9, 2026 at 21:15 GMT, Robert Winkler @.***> wrote:

I also tried to start de AppImage and configure a local ollama model.
Again, an error occurs:
[OllamaProcessManager] Ollama will bind on port 11434 when booted.
[OllamaProcessManager] Creating Ollama models folder in application storage. {
destination: '/home/rob/.config/anythingllm-desktop/storage/models/ollama'
}
[ManualBrowser] Listening for IPC messages from main renderer process!
[OllamaProcessManager] SINGLETON LOCK: Using existing OllamaProcessManager.
[OllamaProcessManager] [nix] Ollama subprocess running. Port 11434. PID 123392.
[123123:0109/151302.308378:ERROR:browser_main_loop.cc(278)] GLib-GObject: ../gobject/gsignal.c:2700: instance '0x212802bdd400' has no handler with id '4780'

Robert Winkler - Chat @ Spike [3gljf2]

On January 9, 2026 at 18:55 GMT, Robert Winkler @.***> wrote:

Well, it give me:
sudo lsof -i :3001
[sudo] password for rob:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
anythingl 104204 rob 39u IPv4 875715 0t0 TCP localhost:origo-native (LISTEN)

Robert Winkler - Chat @ Spike [3glcxf]

On January 9, 2026 at 18:30 GMT, Timothy Carambat @.***> wrote:

timothycarambat left a comment (Mintplex-Labs/anything-llm#4839)

🤔 That is weird. If you just boot up the application and then open a browser or curl localhost:30001/api/ping do you get a 200OK?

The failure to save is quite odd. Is it possible you have another process using 3001 and our frontend see that and tries to send to that endpoint which obviously fails.

sudo lsof -i :3001

The backend log should announce the port at the top of the log and that is trimmed in that output, but its 3001 by default and it should port-hunt in a similar range if 3001 is occupied.


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@robert-winkler commented on GitHub (Jan 9, 2026): BTW: I have the same problem of "failed to save LLM settings: failed to fetch" with the AnythingLLM AppImage on Debian. [Robert Winkler - Chat @ Spike](https://spikenow.com/r/a/?ref=spike-organic-signature&_ts=3gllc3) [3gllc3] On January 9, 2026 at 21:17 GMT, Robert Winkler ***@***.***> wrote: I intended to start the docker image according to the instructions (I have various docker instances running in production, e.g. Open WebUI). However, even if there is a anythinllm container running and bound to 3001:3001, the web GUI is not accesible. [Robert Winkler - Chat @ Spike](https://spikenow.com/r/a/?ref=spike-organic-signature&_ts=3gljhx) [3gljhx] On January 9, 2026 at 21:15 GMT, Robert Winkler ***@***.***> wrote: I also tried to start de AppImage and configure a local ollama model. Again, an error occurs: [OllamaProcessManager] Ollama will bind on port 11434 when booted. [OllamaProcessManager] Creating Ollama models folder in application storage. { destination: '/home/rob/.config/anythingllm-desktop/storage/models/ollama' } [ManualBrowser] Listening for IPC messages from main renderer process! [OllamaProcessManager] SINGLETON LOCK: Using existing OllamaProcessManager. [OllamaProcessManager] [nix] Ollama subprocess running. Port 11434. PID 123392. [123123:0109/151302.308378:ERROR:browser_main_loop.cc(278)] GLib-GObject: ../gobject/gsignal.c:2700: instance '0x212802bdd400' has no handler with id '4780' [Robert Winkler - Chat @ Spike](https://spikenow.com/r/a/?ref=spike-organic-signature&_ts=3gljf2) [3gljf2] On January 9, 2026 at 18:55 GMT, Robert Winkler ***@***.***> wrote: Well, it give me: sudo lsof -i :3001 [sudo] password for rob: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME anythingl 104204 rob 39u IPv4 875715 0t0 TCP localhost:origo-native (LISTEN) [Robert Winkler - Chat @ Spike](https://spikenow.com/r/a/?ref=spike-organic-signature&_ts=3glcxf) [3glcxf] On January 9, 2026 at 18:30 GMT, Timothy Carambat ***@***.***> wrote: timothycarambat left a comment [(Mintplex-Labs/anything-llm#4839)](https://github.com/Mintplex-Labs/anything-llm/issues/4839#issuecomment-3730097287) 🤔 That is weird. If you just boot up the application and then open a browser or curl localhost:30001/api/ping do you get a 200OK? The failure to save is quite odd. Is it possible you have another process using 3001 and our frontend see that and tries to send to that endpoint which obviously fails. sudo lsof -i :3001 The backend log should announce the port at the top of the log and that is trimmed in that output, but its 3001 by default and it should port-hunt in a similar range if 3001 is occupied. — Reply to this email directly, [view it on GitHub](https://github.com/Mintplex-Labs/anything-llm/issues/4839#issuecomment-3730097287), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ACMIC3N3GTW4JPN4YG54VXD4F7XVHAVCNFSM6AAAAACRDWABPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZQGA4TOMRYG4). You are receiving this because you authored the thread.Message ID: ***@***.***>
yindo changed title from [BUG]: failed to save LLM settings: failed to fetch to [GH-ISSUE #4839] [BUG]: failed to save LLM settings: failed to fetch 2026-06-05 14:50:01 -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#3046