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 #5002] [BUG]: Cannot save LLM setting on install - TRuenas scale AnythingLLM app. #3140

New Issue
Closed
opened 2026-02-22 18:32:47 -05:00 by yindo · 8 comments
yindo commented 2026-02-22 18:32:47 -05:00
Owner
Copy Link
Copy Source

Originally created by @Xxxyz721 on GitHub (Feb 14, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5002

How are you running AnythingLLM?

Docker (local)

What happened?

trying to setup anythingLLM on TRuenas scale with locally hosted Ollama.

When installing the app seems to go on ok but on startup and accessing the web interface the configuration steps cannot be completed as it reports:-

"Failed to save LLM settings :Failed to load" or the same but with "Network error".

On the webpage I select Ollama from the list and specify the explicit lan IP address and port (http://192.168.1.16:11434) into the box.

The screen refreshes and shows me the list of models from the ollama instance and I can select one of those (chosing Phi3 initially).

then I click on save and it thinks for a bit, then pops up the error.

I have read that it could be a rights issue to the .env file in the server folder, so looking at that I could see the file was owned by the internal container anythingllm user and I could set it with chmod 777 etc.

initially the folder liiked like this:-

$ cd server
$ ls -alr
total 587
-rw-r--r-- 1 anythingllm anythingllm 371099 Jan 24 00:12 yarn.lock
drwxr-xr-x 28 anythingllm anythingllm 28 Jan 24 00:12 utils
drwxr-xr-x 2 anythingllm anythingllm 8 Jan 24 00:12 swagger
drwxr-xr-x 5 anythingllm anythingllm 6 Feb 14 16:49 storage
drwxr-xr-x 5 anythingllm anythingllm 106 Jan 24 00:14 public
drwxr-xr-x 3 anythingllm anythingllm 5 Jan 24 00:12 prisma
-rw-r--r-- 1 anythingllm anythingllm 3445 Jan 24 00:12 package.json
-rw-r--r-- 1 anythingllm anythingllm 80 Jan 24 00:12 nodemon.json
drwxr-xr-x 1 anythingllm anythingllm 3 Jan 24 00:23 node_modules
drwxr-xr-x 2 anythingllm anythingllm 31 Jan 24 00:12 models
drwxr-xr-x 2 anythingllm anythingllm 3 Jan 24 00:12 middleware
-rw-r--r-- 1 anythingllm anythingllm 244 Jan 24 00:12 jsconfig.json
drwxr-xr-x 3 anythingllm anythingllm 5 Jan 24 00:12 jobs
-rw-r--r-- 1 anythingllm anythingllm 5230 Jan 24 00:12 index.js
drwxr-xr-x 8 anythingllm anythingllm 23 Jan 24 00:12 endpoints
drwxr-xr-x 4 anythingllm anythingllm 4 Jan 24 00:12 tests
-rw-r--r-- 1 anythingllm anythingllm 8 Jan 24 00:12 .nvmrc
-rw-r--r-- 1 anythingllm anythingllm 575 Jan 24 00:12 .gitignore
-rw-r--r-- 1 anythingllm anythingllm 367 Jan 24 00:12 .flowconfig
-rw-r--r-- 1 anythingllm anythingllm 14676 Jan 15 00:12 .env
drwxr-x--- 1 anythingllm anythingllm 5 Jan 24 00:22 ..
drwxr-xr-x 1 anythingllm anythingllm 3 Jan 24 01:15 .
$

then could be set to this after chmod 777:-

$ cd server
$ ls -alr
total 587
-rw-r--r-- 1 anythingllm anythingllm 371099 Jan 24 00:12 yarn.lock
drwxr-xr-x 28 anythingllm anythingllm 28 Jan 24 00:12 utils
drwxr-xr-x 2 anythingllm anythingllm 8 Jan 24 00:12 swagger
drwxr-xr-x 5 anythingllm anythingllm 6 Feb 14 16:49 storage
drwxr-xr-x 5 anythingllm anythingllm 106 Jan 24 00:14 public
drwxr-xr-x 3 anythingllm anythingllm 5 Jan 24 00:12 prisma
-rw-r--r-- 1 anythingllm anythingllm 3445 Jan 24 00:12 package.json
-rw-r--r-- 1 anythingllm anythingllm 80 Jan 24 00:12 nodemon.json
drwxr-xr-x 1 anythingllm anythingllm 3 Jan 24 00:23 node_modules
drwxr-xr-x 2 anythingllm anythingllm 31 Jan 24 00:12 models
drwxr-xr-x 2 anythingllm anythingllm 3 Jan 24 00:12 middleware
-rw-r--r-- 1 anythingllm anythingllm 244 Jan 24 00:12 jsconfig.json
drwxr-xr-x 3 anythingllm anythingllm 5 Jan 24 00:12 jobs
-rw-r--r-- 1 anythingllm anythingllm 5230 Jan 24 00:12 index.js
drwxr-xr-x 8 anythingllm anythingllm 23 Jan 24 00:12 endpoints
drwxr-xr-x 4 anythingllm anythingllm 4 Jan 24 00:12 tests
-rw-r--r-- 1 anythingllm anythingllm 8 Jan 24 00:12 .nvmrc
-rw-r--r-- 1 anythingllm anythingllm 575 Jan 24 00:12 .gitignore
-rw-r--r-- 1 anythingllm anythingllm 367 Jan 24 00:12 .flowconfig
-rwxrwxrwx 1 anythingllm anythingllm 14676 Jan 15 00:12 .env
drwxr-x--- 1 anythingllm anythingllm 5 Jan 24 00:22 ..
drwxr-xr-x 1 anythingllm anythingllm 4 Jan 24 01:15 .
$ ^C
$

However, this didnt allow the .env to be set or saved it seems, plus on restarting the service the file permissions had reset back to the original levels.

Super frustrating as I want to simply use this all in house with my own self hosted system but I can't get it to accept the config.

Its not as if the app cant see ollama, it's talking to the api fine as it can access the model list and all that. just wont allow me to progress with the configuration.

Any suggestions?

TRUENAS Scale Version:-
25.04.2.6

AnythingLLM app Version:-
Name:
anything-llm
App Version:
v1.10.0
Version:
v1.0.16
Source:
github.com/Mintplex-Labs/anything-llm
Train:
community

Thanks,

STu.

Are there known steps to reproduce?

No response

Originally created by @Xxxyz721 on GitHub (Feb 14, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5002 ### How are you running AnythingLLM? Docker (local) ### What happened? trying to setup anythingLLM on TRuenas scale with locally hosted Ollama. When installing the app seems to go on ok but on startup and accessing the web interface the configuration steps cannot be completed as it reports:- "Failed to save LLM settings :Failed to load" or the same but with "Network error". On the webpage I select Ollama from the list and specify the explicit lan IP address and port (http://192.168.1.16:11434) into the box. The screen refreshes and shows me the list of models from the ollama instance and I can select one of those (chosing Phi3 initially). then I click on save and it thinks for a bit, then pops up the error. I have read that it could be a rights issue to the .env file in the server folder, so looking at that I could see the file was owned by the internal container anythingllm user and I could set it with chmod 777 etc. initially the folder liiked like this:- $ cd server $ ls -alr total 587 -rw-r--r-- 1 anythingllm anythingllm 371099 Jan 24 00:12 yarn.lock drwxr-xr-x 28 anythingllm anythingllm 28 Jan 24 00:12 utils drwxr-xr-x 2 anythingllm anythingllm 8 Jan 24 00:12 swagger drwxr-xr-x 5 anythingllm anythingllm 6 Feb 14 16:49 storage drwxr-xr-x 5 anythingllm anythingllm 106 Jan 24 00:14 public drwxr-xr-x 3 anythingllm anythingllm 5 Jan 24 00:12 prisma -rw-r--r-- 1 anythingllm anythingllm 3445 Jan 24 00:12 package.json -rw-r--r-- 1 anythingllm anythingllm 80 Jan 24 00:12 nodemon.json drwxr-xr-x 1 anythingllm anythingllm 3 Jan 24 00:23 node_modules drwxr-xr-x 2 anythingllm anythingllm 31 Jan 24 00:12 models drwxr-xr-x 2 anythingllm anythingllm 3 Jan 24 00:12 middleware -rw-r--r-- 1 anythingllm anythingllm 244 Jan 24 00:12 jsconfig.json drwxr-xr-x 3 anythingllm anythingllm 5 Jan 24 00:12 jobs -rw-r--r-- 1 anythingllm anythingllm 5230 Jan 24 00:12 index.js drwxr-xr-x 8 anythingllm anythingllm 23 Jan 24 00:12 endpoints drwxr-xr-x 4 anythingllm anythingllm 4 Jan 24 00:12 __tests__ -rw-r--r-- 1 anythingllm anythingllm 8 Jan 24 00:12 .nvmrc -rw-r--r-- 1 anythingllm anythingllm 575 Jan 24 00:12 .gitignore -rw-r--r-- 1 anythingllm anythingllm 367 Jan 24 00:12 .flowconfig -rw-r--r-- 1 anythingllm anythingllm 14676 Jan 15 00:12 .env drwxr-x--- 1 anythingllm anythingllm 5 Jan 24 00:22 .. drwxr-xr-x 1 anythingllm anythingllm 3 Jan 24 01:15 . $ then could be set to this after chmod 777:- $ cd server $ ls -alr total 587 -rw-r--r-- 1 anythingllm anythingllm 371099 Jan 24 00:12 yarn.lock drwxr-xr-x 28 anythingllm anythingllm 28 Jan 24 00:12 utils drwxr-xr-x 2 anythingllm anythingllm 8 Jan 24 00:12 swagger drwxr-xr-x 5 anythingllm anythingllm 6 Feb 14 16:49 storage drwxr-xr-x 5 anythingllm anythingllm 106 Jan 24 00:14 public drwxr-xr-x 3 anythingllm anythingllm 5 Jan 24 00:12 prisma -rw-r--r-- 1 anythingllm anythingllm 3445 Jan 24 00:12 package.json -rw-r--r-- 1 anythingllm anythingllm 80 Jan 24 00:12 nodemon.json drwxr-xr-x 1 anythingllm anythingllm 3 Jan 24 00:23 node_modules drwxr-xr-x 2 anythingllm anythingllm 31 Jan 24 00:12 models drwxr-xr-x 2 anythingllm anythingllm 3 Jan 24 00:12 middleware -rw-r--r-- 1 anythingllm anythingllm 244 Jan 24 00:12 jsconfig.json drwxr-xr-x 3 anythingllm anythingllm 5 Jan 24 00:12 jobs -rw-r--r-- 1 anythingllm anythingllm 5230 Jan 24 00:12 index.js drwxr-xr-x 8 anythingllm anythingllm 23 Jan 24 00:12 endpoints drwxr-xr-x 4 anythingllm anythingllm 4 Jan 24 00:12 __tests__ -rw-r--r-- 1 anythingllm anythingllm 8 Jan 24 00:12 .nvmrc -rw-r--r-- 1 anythingllm anythingllm 575 Jan 24 00:12 .gitignore -rw-r--r-- 1 anythingllm anythingllm 367 Jan 24 00:12 .flowconfig -rwxrwxrwx 1 anythingllm anythingllm 14676 Jan 15 00:12 .env drwxr-x--- 1 anythingllm anythingllm 5 Jan 24 00:22 .. drwxr-xr-x 1 anythingllm anythingllm 4 Jan 24 01:15 . $ ^C $ However, this didnt allow the .env to be set or saved it seems, plus on restarting the service the file permissions had reset back to the original levels. Super frustrating as I want to simply use this all in house with my own self hosted system but I can't get it to accept the config. Its not as if the app cant see ollama, it's talking to the api fine as it can access the model list and all that. just wont allow me to progress with the configuration. Any suggestions? TRUENAS Scale Version:- 25.04.2.6 AnythingLLM app Version:- Name: anything-llm App Version: v1.10.0 Version: v1.0.16 Source: [github.com/Mintplex-Labs/anything-llm](https://github.com/Mintplex-Labs/anything-llm) Train: community Thanks, STu. ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:32:47 -05:00
yindo closed this issue 2026-02-22 18:32:47 -05:00
yindo commented 2026-02-22 18:32:47 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 16, 2026):

Are you using the official start command in our docs? It is all there and you should additionally be seeing an error message in the container on boot exactly when this happens (no storage dir)
https://docs.anythingllm.com/installation-docker/quickstart

@timothycarambat commented on GitHub (Feb 16, 2026): Are you using the official start command in our docs? It is all there and you should additionally be seeing an error message in the container on boot exactly when this happens (no storage dir) https://docs.anythingllm.com/installation-docker/quickstart
yindo commented 2026-02-22 18:32:47 -05:00
Author
Owner
Copy Link
Copy Source

@Xxxyz721 commented on GitHub (Feb 16, 2026):

Not sure from that guide exactly what needs to be setup here as I’m running the anythingllm app from the official IX catalogue.

Do I need to specifically add storage and config folders on the server? The ix-apps jails generally handle it all internally for other apps. Running in verbose logging for the app/container gives no additional information I can see and the inbuilt anythingllm account is the active logged on user and should surely have rights?

It can access all the application files and launch the app, just seems to either not know where the config .env file is or can only see it as read only….

I’ll go through the docs for sure, is there a specific set of command line options I need to add though to the launch parameters in the the app settings?

I know it’s slightly different in truenas as the containerisation of apps is slightly different but it’s all running in a docker-esque fashion…

Maybe I can copy that launch script and put it into the app via dockge?

Ta,

Stu.

@Xxxyz721 commented on GitHub (Feb 16, 2026): Not sure from that guide exactly what needs to be setup here as I’m running the anythingllm app from the official IX catalogue. Do I need to specifically add storage and config folders on the server? The ix-apps jails generally handle it all internally for other apps. Running in verbose logging for the app/container gives no additional information I can see and the inbuilt anythingllm account is the active logged on user and should surely have rights? It can access all the application files and launch the app, just seems to either not know where the config .env file is or can only see it as read only…. I’ll go through the docs for sure, is there a specific set of command line options I need to add though to the launch parameters in the the app settings? I know it’s slightly different in truenas as the containerisation of apps is slightly different but it’s all running in a docker-esque fashion… Maybe I can copy that launch script and put it into the app via dockge? Ta, Stu.
yindo commented 2026-02-22 18:32:47 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 16, 2026):

Ah, then that is likely the case. I am not familiar with the IX Catalogue but we certainly dont maintain that setup and so because of that I can say that is likely the whole cause - if not most.

But if you have docker on your machine, which i presume you do since that is how to launch the dockerized version of the app - if you had this in a command it would work

export STORAGE_LOCATION=$HOME/anythingllm && \
mkdir -p $STORAGE_LOCATION && \
touch "$STORAGE_LOCATION/.env" && \
docker run -d -p 3001:3001 \
--cap-add SYS_ADMIN \
-v ${STORAGE_LOCATION}:/app/server/storage \
-v ${STORAGE_LOCATION}/.env:/app/server/.env \
-e STORAGE_DIR="/app/server/storage" \
mintplexlabs/anythingllm:latest

One thing to note, in that script we assume the storage is under the user homespace because top-level folders you will need to chmod -R 777 so that you can read/write to them.

@timothycarambat commented on GitHub (Feb 16, 2026): Ah, then that is likely the case. I am not familiar with the IX Catalogue but we certainly dont maintain that setup and so because of that I can say that is likely the whole cause - if not most. But if you have docker on your machine, which i presume you do since that is how to launch the dockerized version of the app - if you had this in a command it would work ``` export STORAGE_LOCATION=$HOME/anythingllm && \ mkdir -p $STORAGE_LOCATION && \ touch "$STORAGE_LOCATION/.env" && \ docker run -d -p 3001:3001 \ --cap-add SYS_ADMIN \ -v ${STORAGE_LOCATION}:/app/server/storage \ -v ${STORAGE_LOCATION}/.env:/app/server/.env \ -e STORAGE_DIR="/app/server/storage" \ mintplexlabs/anythingllm:latest ``` One thing to note, in that script we assume the storage is under the user homespace because top-level folders you will need to `chmod -R 777` so that you can read/write to them.
yindo commented 2026-02-22 18:32:47 -05:00
Author
Owner
Copy Link
Copy Source

@Xxxyz721 commented on GitHub (Feb 16, 2026):

Ok cheers :).On 16 Feb 2026, at 22:21, Timothy Carambat @.***> wrote:timothycarambat left a comment (Mintplex-Labs/anything-llm#5002)
Ah, then that is likely the case. I am not familiar with the IX Catalogue but we certainly dont maintain that setup and so because of that I can say that is likely the whole cause - if not most.
But if you have docker on your machine, which i presume you do since that is how to launch the dockerized version of the app - if you had this in a command it would work
export STORAGE_LOCATION=$HOME/anythingllm &&
mkdir -p $STORAGE_LOCATION &&
touch "$STORAGE_LOCATION/.env" &&
docker run -d -p 3001:3001
--cap-add SYS_ADMIN
-v ${STORAGE_LOCATION}:/app/server/storage
-v ${STORAGE_LOCATION}/.env:/app/server/.env
-e STORAGE_DIR="/app/server/storage"
mintplexlabs/anythingllm:latest

One thing to note, in that script we assume the storage is under the user homespace because top-level folders you will need to chmod -R 777 so that you can read/write to them.

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

@Xxxyz721 commented on GitHub (Feb 16, 2026): Ok cheers :).On 16 Feb 2026, at 22:21, Timothy Carambat ***@***.***> wrote:timothycarambat left a comment (Mintplex-Labs/anything-llm#5002) Ah, then that is likely the case. I am not familiar with the IX Catalogue but we certainly dont maintain that setup and so because of that I can say that is likely the whole cause - if not most. But if you have docker on your machine, which i presume you do since that is how to launch the dockerized version of the app - if you had this in a command it would work export STORAGE_LOCATION=$HOME/anythingllm && \ mkdir -p $STORAGE_LOCATION && \ touch "$STORAGE_LOCATION/.env" && \ docker run -d -p 3001:3001 \ --cap-add SYS_ADMIN \ -v ${STORAGE_LOCATION}:/app/server/storage \ -v ${STORAGE_LOCATION}/.env:/app/server/.env \ -e STORAGE_DIR="/app/server/storage" \ mintplexlabs/anythingllm:latest One thing to note, in that script we assume the storage is under the user homespace because top-level folders you will need to chmod -R 777 so that you can read/write to them. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
yindo changed title from [BUG]: Cannot save LLM setting on install - TRuenas scale AnythingLLM app. to [GH-ISSUE #5002] [BUG]: Cannot save LLM setting on install - TRuenas scale AnythingLLM app. 2026-06-05 14:50:32 -04:00
yindo commented 2026-06-05 14:50:33 -04:00
Author
Owner
Copy Link
Copy Source

@BenJ2002 commented on GitHub (Apr 28, 2026):

Thank you for the responses, but I think that the point has been missed that this is a challenge in TrueNAS when loading AnythingLLM from the TrueCharts repository. This does not allow the average user to use or modify .yaml files.

TrueNAS does not allow you to access the .yaml file. You can certainly make a manual manifest.yaml but that only works with the initial pull. Afterthe container has been setup you lose access to that .yaml.

I have traced data to identify the container, but TrueNAS blocks so many apps and permissions (good security posture) that it's very difficult to find the container or change the internal .env or .yaml files. TrueNAS does not let you use editors in the shell.

I have Dockhand installed, but changes do not persistent when the container is restarted or stopped/restarted (compose down/up) in TrueNAS.

My Dataset has been built with the proper permissions in NFSv4 for R/W/X for Owner & Group and R/W for Users and Others. I've tried R/W/X for the user (568). No help.

I've set and forced ACL in TrueNAS's App edit screen. No help.

I've verified that the .env has the correct path.

What I think the problem could be: TrueNAS creates a mount point that maps your dataset to /app/server/storage. The app runs fine, it does not give any errors and says that AI Providers are saved. I think we need to find a way to make that mount point persist when the container changes.

Interestingly, my user data, branding and whitelabeling, Agent Skills and Community Hub downloads all persist. It's the AI Providers (LLM, Vector, Embedder, etc.) that do not persist.

I've also read Data not persisting in Truenas Scale #4546. I checked the path that was listed and it persists. I took it out of the .ix-apps directory because of how I have my pools organized and it works fine. I moved it back to .ix-apps and the settings did not persist.

I noted that anythingllm uses 1000:1000. I set ownership to 1000:1000. No help.

Any more ideas?

Thanks for the help!

<!-- gh-comment-id:4338080783 --> @BenJ2002 commented on GitHub (Apr 28, 2026): Thank you for the responses, but I think that the point has been missed that this is a challenge in TrueNAS when loading AnythingLLM from the TrueCharts repository. This does not allow the average user to use or modify .yaml files. TrueNAS does not allow you to access the .yaml file. You can certainly make a manual manifest.yaml but that only works with the initial pull. Afterthe container has been setup you lose access to that .yaml. I have traced data to identify the container, but TrueNAS blocks so many apps and permissions (good security posture) that it's very difficult to find the container or change the internal .env or .yaml files. TrueNAS does not let you use editors in the shell. I have Dockhand installed, but changes do not persistent when the container is restarted or stopped/restarted (compose down/up) in TrueNAS. My Dataset has been built with the proper permissions in NFSv4 for R/W/X for Owner & Group and R/W for Users and Others. I've tried R/W/X for the user (568). <b> No help. </b> I've set and forced ACL in TrueNAS's App edit screen. <b> No help. </b> I've verified that the .env has the correct path. What I think the problem could be: TrueNAS creates a mount point that maps your dataset to /app/server/storage. The app runs fine, it does not give any errors and says that AI Providers are saved. I think we need to find a way to make that mount point persist when the container changes. Interestingly, my user data, branding and whitelabeling, Agent Skills and Community Hub downloads all persist. It's the AI Providers (LLM, Vector, Embedder, etc.) that do not persist. I've also read Data not persisting in Truenas Scale #4546. I checked the path that was listed and it persists. I took it out of the .ix-apps directory because of how I have my pools organized and it works fine. I moved it back to .ix-apps and the settings did not persist. I noted that anythingllm uses 1000:1000. I set ownership to 1000:1000. <b> No help. </b> Any more ideas? Thanks for the help!
yindo commented 2026-06-05 14:50:33 -04:00
Author
Owner
Copy Link
Copy Source

@cleber7up commented on GitHub (May 20, 2026):

I had this problem on TrueNas among with others on AnythingLLM... First make sure you can replace the UID and GID to your default... usually for apps is 568... If you can't edit and installed it from TrueNas app store (1000:1000), make sure to map a host path and use a policy to allow full modify for app users and add a @everyone users to the same folder and allow full modify or chmod777.

Make sure to map/mount these:

/app/server/storage/anythingllm-fs (your path to folder that agent will create files and other things)

/app/server/.env (your path to .env file to get persistent configurations saved across reboots and app restarts, don't forget to put yourpath/.env)

maybe you need to create .env before with touch command on shell before mount

don't map again /app/server/storage, instead use the original config on pre deployment and map to your host path on storage settings

if all followed you will get it booted up and running and configs persistent across all restarts and reboots.

<!-- gh-comment-id:4504285156 --> @cleber7up commented on GitHub (May 20, 2026): I had this problem on TrueNas among with others on AnythingLLM... First make sure you can replace the UID and GID to your default... usually for apps is 568... If you can't edit and installed it from TrueNas app store (1000:1000), make sure to map a host path and use a policy to allow full modify for app users and add a @everyone users to the same folder and allow full modify or chmod777. Make sure to map/mount these: /app/server/storage/anythingllm-fs (your path to folder that agent will create files and other things) /app/server/.env (your path to .env file to get persistent configurations saved across reboots and app restarts, don't forget to put yourpath/_.env_) maybe you need to create .env before with touch command on shell before mount don't map again /app/server/storage, instead use the original config on pre deployment and map to your host path on storage settings if all followed you will get it booted up and running and configs persistent across all restarts and reboots.
yindo commented 2026-06-05 14:50:33 -04:00
Author
Owner
Copy Link
Copy Source

@BenJ2002 commented on GitHub (May 28, 2026):

Thanks for the help.
I played around with permissions until I was blue in the face. Then I converted the app to a custom app and added a new bind point to the .env like you mentioned.

That is the fix for this app in TrueNAS. I’m sure you can do this with the docker-compose.yaml, but that’s more difficult to track down and I also feared that it would erase my bind on the next update.

I think custom apps with the modified environment file might be safer.

Thanks again!

I had this problem on TrueNas among with others on AnythingLLM... First make sure you can replace the UID and GID to your default... usually for apps is 568... If you can't edit and installed it from TrueNas app store (1000:1000), make sure to map a host path and use a policy to allow full modify for app users and add a @everyone users to the same folder and allow full modify or chmod777.

Make sure to map/mount these:

/app/server/storage/anythingllm-fs (your path to folder that agent will create files and other things)

/app/server/.env (your path to .env file to get persistent configurations saved across reboots and app restarts, don't forget to put yourpath/.env)

maybe you need to create .env before with touch command on shell before mount

don't map again /app/server/storage, instead use the original config on pre deployment and map to your host path on storage settings

if all followed you will get it booted up and running and configs persistent across all restarts and reboots.

<!-- gh-comment-id:4568795859 --> @BenJ2002 commented on GitHub (May 28, 2026): Thanks for the help. I played around with permissions until I was blue in the face. Then I converted the app to a custom app and added a new bind point to the .env like you mentioned. That is the fix for this app in TrueNAS. I’m sure you can do this with the docker-compose.yaml, but that’s more difficult to track down and I also feared that it would erase my bind on the next update. I think custom apps with the modified environment file might be safer. Thanks again! > I had this problem on TrueNas among with others on AnythingLLM... First make sure you can replace the UID and GID to your default... usually for apps is 568... If you can't edit and installed it from TrueNas app store (1000:1000), make sure to map a host path and use a policy to allow full modify for app users and add a [@everyone](https://github.com/everyone) users to the same folder and allow full modify or chmod777. > > Make sure to map/mount these: > > /app/server/storage/anythingllm-fs (your path to folder that agent will create files and other things) > > /app/server/.env (your path to .env file to get persistent configurations saved across reboots and app restarts, don't forget to put yourpath/_.env_) > > maybe you need to create .env before with touch command on shell before mount > > don't map again /app/server/storage, instead use the original config on pre deployment and map to your host path on storage settings > > if all followed you will get it booted up and running and configs persistent across all restarts and reboots.
yindo commented 2026-06-05 14:50:33 -04:00
Author
Owner
Copy Link
Copy Source

@cleber7up commented on GitHub (Jun 4, 2026):

Glad to help!

These days i was out putting to fry my brain getting set up vllm (0.22 cuda12.9) and litellm with full attention and kv cache plus cuda graph... and now putting hermes agent to work out...

for curiosity, dual rtx 3060 is outputing 80 tokens/sec on qwen 3.5 9bi with 128k context plus qwen 3 embedding 8bi with 32k context... just letting few megabytes of free vram, but i managed to get it fitted.

Anythingllm is blazing fast now outputing 4096 vector to Qdrant and giving smart and fast responses compared to qwen 2.5 and 3 on ollama.

<!-- gh-comment-id:4627546687 --> @cleber7up commented on GitHub (Jun 4, 2026): Glad to help! These days i was out putting to fry my brain getting set up vllm (0.22 cuda12.9) and litellm with full attention and kv cache plus cuda graph... and now putting hermes agent to work out... for curiosity, dual rtx 3060 is outputing 80 tokens/sec on qwen 3.5 9bi with 128k context plus qwen 3 embedding 8bi with 32k context... just letting few megabytes of free vram, but i managed to get it fitted. Anythingllm is blazing fast now outputing 4096 vector to Qdrant and giving smart and fast responses compared to qwen 2.5 and 3 on ollama.
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#3140
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?