[GH-ISSUE #33] API keys wont go green. #22

Closed
opened 2026-02-22 18:17:29 -05:00 by yindo · 21 comments
Owner

Originally created by @luizbueno3d on GitHub (Jun 11, 2023).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/33

My .env.development looks like this:

SERVER_PORT=3001
OPEN_AI_KEY=sk-.....
OPEN_MODEL_PREF='gpt-3.5-turbo'
CACHE_VECTORS="true"

# Enable all below if you are using vector database: Chroma.
# VECTOR_DB="chroma"
# CHROMA_ENDPOINT='http://localhost:8000'

# Enable all below if you are using vector database: Pinecone.
VECTOR_DB="pinecone"
PINECONE_ENVIRONMENT=us-wes...
PINECONE_API_KEY=b5......
PINECONE_INDEX=default

# Enable all below if you are using vector database: LanceDB.
# VECTOR_DB="lancedb"

# CLOUD DEPLOYMENT VARIRABLES ONLY
# AUTH_TOKEN="hunter2" # This is the password to your application if remote hosting.
# JWT_SECRET="my-random-string-for-seeding" # Only needed if AUTH_TOKEN is set. Please generate random string at least 12 chars long.
# STORAGE_DIR= # absolute filesystem path with no trailing slash

with all correct and cross checked keys. Am I doing something obviously wrong?

When I send a chat message, I get a return: Could not send chat.
I check the API keys and they are RED. "Ensure all fields are green before attempting to use AnythingLLM or it may not function as expected!" in red.
I've tried everything I could think of. Could anyone help?

Originally created by @luizbueno3d on GitHub (Jun 11, 2023). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/33 My .env.development looks like this: ``` SERVER_PORT=3001 OPEN_AI_KEY=sk-..... OPEN_MODEL_PREF='gpt-3.5-turbo' CACHE_VECTORS="true" # Enable all below if you are using vector database: Chroma. # VECTOR_DB="chroma" # CHROMA_ENDPOINT='http://localhost:8000' # Enable all below if you are using vector database: Pinecone. VECTOR_DB="pinecone" PINECONE_ENVIRONMENT=us-wes... PINECONE_API_KEY=b5...... PINECONE_INDEX=default # Enable all below if you are using vector database: LanceDB. # VECTOR_DB="lancedb" # CLOUD DEPLOYMENT VARIRABLES ONLY # AUTH_TOKEN="hunter2" # This is the password to your application if remote hosting. # JWT_SECRET="my-random-string-for-seeding" # Only needed if AUTH_TOKEN is set. Please generate random string at least 12 chars long. # STORAGE_DIR= # absolute filesystem path with no trailing slash ``` with all correct and cross checked keys. Am I doing something obviously wrong? When I send a chat message, I get a return: Could not send chat. I check the API keys and they are RED. "Ensure all fields are green before attempting to use AnythingLLM or it may not function as expected!" in red. I've tried everything I could think of. Could anyone help?
yindo added the question label 2026-02-22 18:17:29 -05:00
yindo closed this issue 2026-02-22 18:17:29 -05:00
Author
Owner

@prakks1992 commented on GitHub (Jun 11, 2023):

same issue with me

@prakks1992 commented on GitHub (Jun 11, 2023): same issue with me
Author
Owner

@shipb commented on GitHub (Jun 12, 2023):

Yeah i'm having the same problem

@shipb commented on GitHub (Jun 12, 2023): Yeah i'm having the same problem
Author
Owner

@timothycarambat commented on GitHub (Jun 12, 2023):

Is this file in the server folder and also did you restart the server after making the changes?

Also be sure you are running yarn dev:server and not yarn prod:server

@timothycarambat commented on GitHub (Jun 12, 2023): Is this file in the `server` folder and also did you restart the server after making the changes? Also be sure you are running `yarn dev:server` and **not** `yarn prod:server`
Author
Owner

@luizbueno3d commented on GitHub (Jun 12, 2023):

Yes, all Exactly how you’ve said it.
All went smoothly in the installation. Followed every read me and your
YouTube video.
I’m wondering why I don’t get a Green from the keys. Did something change?
The structure of the key screen looks a little bit different. Yours has no
field “pinecone“ like ours.
Luiz

On Mon 12. Jun 2023 at 19:40, Timothy Carambat @.***>
wrote:

Is this file in the server folder and also did you restart the server
after making the changes?

Also be sure you are running yarn dev:server and not yarn prod:server


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

@luizbueno3d commented on GitHub (Jun 12, 2023): Yes, all Exactly how you’ve said it. All went smoothly in the installation. Followed every read me and your YouTube video. I’m wondering why I don’t get a Green from the keys. Did something change? The structure of the key screen looks a little bit different. Yours has no field “pinecone“ like ours. Luiz On Mon 12. Jun 2023 at 19:40, Timothy Carambat ***@***.***> wrote: > Is this file in the server folder and also did you restart the server > after making the changes? > > Also be sure you are running yarn dev:server and *not* yarn prod:server > > — > Reply to this email directly, view it on GitHub > <https://github.com/Mintplex-Labs/anything-llm/issues/33#issuecomment-1587779768>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIQUDDW2FFASAFTRG5QJEG3XK5H7TANCNFSM6AAAAAAZCTR6EA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Author
Owner

@timothycarambat commented on GitHub (Jun 13, 2023):

That video was made on a way earlier version of the repo, so other vector dbs were not supported. the current .env.example is the correct format.

@timothycarambat commented on GitHub (Jun 13, 2023): That video was made on a way earlier version of the repo, so other vector dbs were not supported. the current `.env.example` is the correct format.
Author
Owner

@luizbueno3d commented on GitHub (Jun 13, 2023):

Could you please install the current version from scratch? Git clone the
current repo, set up yarn , create the Python env, install the requirements
, every bit you’ve shown in your read me, running the watch, to collect ,
then starting the server , the frontend, and looking at the keys inside the
GUI?
I’m using a MacBook Air M2.

In the master folder , I had to run the commands in sudo.
In collection was not the case.

I’m excited to get this to work, seems promising.

On Tue 13. Jun 2023 at 06:58, Timothy Carambat @.***>
wrote:

That video was made on a way earlier version of the repo, so other vector
dbs were not supported. the current .env.example is the correct format.


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

@luizbueno3d commented on GitHub (Jun 13, 2023): Could you please install the current version from scratch? Git clone the current repo, set up yarn , create the Python env, install the requirements , every bit you’ve shown in your read me, running the watch, to collect , then starting the server , the frontend, and looking at the keys inside the GUI? I’m using a MacBook Air M2. In the master folder , I had to run the commands in sudo. In collection was not the case. I’m excited to get this to work, seems promising. On Tue 13. Jun 2023 at 06:58, Timothy Carambat ***@***.***> wrote: > That video was made on a way earlier version of the repo, so other vector > dbs were not supported. the current .env.example is the correct format. > > — > Reply to this email directly, view it on GitHub > <https://github.com/Mintplex-Labs/anything-llm/issues/33#issuecomment-1588545868>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIQUDDUAALWTIYNKW37DTPDXK7XNVANCNFSM6AAAAAAZCTR6EA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Author
Owner

@preeteshjain commented on GitHub (Jun 13, 2023):

Same issue. Did a fresh clone just a few minutes ago and installed everything as per the instructions. All the .env files are setup correctly.

Here's what I am seeing:

image
@preeteshjain commented on GitHub (Jun 13, 2023): Same issue. Did a fresh clone just a few minutes ago and installed everything as per the instructions. All the `.env` files are setup correctly. Here's what I am seeing: <img width="1416" alt="image" src="https://github.com/Mintplex-Labs/anything-llm/assets/6207830/9f6d2eb5-b62e-4f11-a86d-e9deabc94ebf">
Author
Owner

@luizbueno3d commented on GitHub (Jun 13, 2023):

Premesh, in your case, seems like you have not filled out the
.env.development

On Tue 13. Jun 2023 at 11:09, Preetesh Jain @.***>
wrote:

Same issue. Did a fresh clone just a few minutes ago and installed
everything as per the instructions.

Here's what I am seeing:
[image: image]
https://user-images.githubusercontent.com/6207830/245419565-9f6d2eb5-b62e-4f11-a86d-e9deabc94ebf.png


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

@luizbueno3d commented on GitHub (Jun 13, 2023): Premesh, in your case, seems like you have not filled out the .env.development On Tue 13. Jun 2023 at 11:09, Preetesh Jain ***@***.***> wrote: > Same issue. Did a fresh clone just a few minutes ago and installed > everything as per the instructions. > > Here's what I am seeing: > [image: image] > <https://user-images.githubusercontent.com/6207830/245419565-9f6d2eb5-b62e-4f11-a86d-e9deabc94ebf.png> > > — > Reply to this email directly, view it on GitHub > <https://github.com/Mintplex-Labs/anything-llm/issues/33#issuecomment-1588873446>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIQUDDVIGAE2KCMZ6JIY26DXLAU37ANCNFSM6AAAAAAZCTR6EA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Author
Owner

@luizbueno3d commented on GitHub (Jun 13, 2023):

Here is what I am seeing:
9C7ED95F-3DD4-4142-9646-0DD321A1BE0F

@luizbueno3d commented on GitHub (Jun 13, 2023): Here is what I am seeing: ![9C7ED95F-3DD4-4142-9646-0DD321A1BE0F](https://github.com/Mintplex-Labs/anything-llm/assets/35733902/f066f6c0-94fa-4e6b-aae6-a2ac7bba775b)
Author
Owner

@preeteshjain commented on GitHub (Jun 13, 2023):

@luizbueno3d Thanks that worked.

@preeteshjain commented on GitHub (Jun 13, 2023): @luizbueno3d Thanks that worked.
Author
Owner

@luizbueno3d commented on GitHub (Jun 13, 2023):

It works on your end now?
Can you chat with it and wont get errors when you send a chat?

On Tue, 13 Jun 2023 at 11:18, Preetesh Jain @.***>
wrote:

@luizbueno3d https://github.com/luizbueno3d Thanks that worked.


Reply to this email directly, view it on GitHub
https://github.com/Mintplex-Labs/anything-llm/issues/33#issuecomment-1588890023,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIQUDDSLTESW6SRZC5ZFL3DXLAV7XANCNFSM6AAAAAAZCTR6EA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@luizbueno3d commented on GitHub (Jun 13, 2023): It works on your end now? Can you chat with it and wont get errors when you send a chat? On Tue, 13 Jun 2023 at 11:18, Preetesh Jain ***@***.***> wrote: > @luizbueno3d <https://github.com/luizbueno3d> Thanks that worked. > > — > Reply to this email directly, view it on GitHub > <https://github.com/Mintplex-Labs/anything-llm/issues/33#issuecomment-1588890023>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIQUDDSLTESW6SRZC5ZFL3DXLAV7XANCNFSM6AAAAAAZCTR6EA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
Author
Owner

@luizbueno3d commented on GitHub (Jun 13, 2023):

You are having the same issue as I am.
As others too.

On Tue 13. Jun 2023 at 11:32, Preetesh Jain @.***>
wrote:

Hey @luizbueno3d https://github.com/luizbueno3d

It says "Could not send chat" when I send any message.
[image: image]
https://user-images.githubusercontent.com/6207830/245428125-be07ee67-1db0-4209-8309-5354b2f52d82.png

Though my configuration looks normal now
[image: image]
https://user-images.githubusercontent.com/6207830/245428722-655e18a6-d49e-4cfa-80b0-8beacda42e08.png


Reply to this email directly, view it on GitHub
https://github.com/Mintplex-Labs/anything-llm/issues/33#issuecomment-1588912676,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIQUDDUIL23UIACVV7UR7TLXLAXR5ANCNFSM6AAAAAAZCTR6EA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@luizbueno3d commented on GitHub (Jun 13, 2023): You are having the same issue as I am. As others too. On Tue 13. Jun 2023 at 11:32, Preetesh Jain ***@***.***> wrote: > Hey @luizbueno3d <https://github.com/luizbueno3d> > > It says "Could not send chat" when I send any message. > [image: image] > <https://user-images.githubusercontent.com/6207830/245428125-be07ee67-1db0-4209-8309-5354b2f52d82.png> > > Though my configuration looks normal now > [image: image] > <https://user-images.githubusercontent.com/6207830/245428722-655e18a6-d49e-4cfa-80b0-8beacda42e08.png> > > — > Reply to this email directly, view it on GitHub > <https://github.com/Mintplex-Labs/anything-llm/issues/33#issuecomment-1588912676>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIQUDDUIL23UIACVV7UR7TLXLAXR5ANCNFSM6AAAAAAZCTR6EA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
Author
Owner

@timothycarambat commented on GitHub (Jun 13, 2023):

Please pull in the latest changes and just run the application inside of Docker locally. It should have no issues!

@timothycarambat commented on GitHub (Jun 13, 2023): Please pull in the latest changes and just run the application inside of [Docker](https://docker.com) locally. It should have no issues!
Author
Owner

@rewphus commented on GitHub (Jun 14, 2023):

+1

@rewphus commented on GitHub (Jun 14, 2023): +1
Author
Owner

@xiong-zhitong commented on GitHub (Jun 15, 2023):

Finally, I got it running by moving this line to the end of the .env.development:

CACHE_VECTORS="true"

In my case, I guess there may be something wrong here:

"dev": "NODE_ENV=development nodemon --ignore documents --ignore vector-cache --trace-warnings index.js",

@xiong-zhitong commented on GitHub (Jun 15, 2023): Finally, I got it running by moving this line to the end of the .env.development: > CACHE_VECTORS="true" In my case, I guess there may be something wrong here: > "dev": "NODE_ENV=development nodemon --ignore documents --ignore vector-cache --trace-warnings index.js",
Author
Owner

@classmatewu commented on GitHub (Jun 18, 2023):

You are having the same issue as I am. In which folder is the .env file located, docker or server?

@classmatewu commented on GitHub (Jun 18, 2023): You are having the same issue as I am. In which folder is the .env file located, docker or server?
Author
Owner

@luizbueno3d commented on GitHub (Jun 19, 2023):

I have to admit I gave up on this project. It feels like Mintplex Labs has
bigger fish to fry. I spent some days trying to make it work with no
success. There are times we got to know when it is enough.

Shame cause it seems promising and useful

Luiz

On Mon 19. Jun 2023 at 05:20, zelinwu @.***> wrote:

You are having the same issue as I am. In which folder is the .env file
located, docker or server?


Reply to this email directly, view it on GitHub
https://github.com/Mintplex-Labs/anything-llm/issues/33#issuecomment-1596434864,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIQUDDXMHJM4OSOW3WKYN3DXL7AO7ANCNFSM6AAAAAAZCTR6EA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@luizbueno3d commented on GitHub (Jun 19, 2023): I have to admit I gave up on this project. It feels like Mintplex Labs has bigger fish to fry. I spent some days trying to make it work with no success. There are times we got to know when it is enough. Shame cause it seems promising and useful Luiz On Mon 19. Jun 2023 at 05:20, zelinwu ***@***.***> wrote: > You are having the same issue as I am. In which folder is the .env file > located, docker or server? > > — > Reply to this email directly, view it on GitHub > <https://github.com/Mintplex-Labs/anything-llm/issues/33#issuecomment-1596434864>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIQUDDXMHJM4OSOW3WKYN3DXL7AO7ANCNFSM6AAAAAAZCTR6EA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
Author
Owner

@vexersa commented on GitHub (Jun 19, 2023):

Same issue for me.

Configured .env underneath /docker folder.

Seems the .env variables are not respected/loaded?

@vexersa commented on GitHub (Jun 19, 2023): Same issue for me. Configured .env underneath /docker folder. Seems the .env variables are not respected/loaded?
Author
Owner

@bibi-b commented on GitHub (Jun 19, 2023):

Same here. I try to run it with docker but it seems that the .env isnt recognized. Any hints?

@bibi-b commented on GitHub (Jun 19, 2023): Same here. I try to run it with docker but it seems that the .env isnt recognized. Any hints?
Author
Owner

@bibi-b commented on GitHub (Jun 20, 2023):

Found a related post on discord. If you run the project on a server and open the URL remotely, it opens the side, but it seems the .env is not loaded. All you have to do is to hardcode the server's address here and rebuild the docker:
frontend/src/utils/constants.js
(change localhost here to your IP)

@bibi-b commented on GitHub (Jun 20, 2023): Found a related post on discord. If you run the project on a server and open the URL remotely, it opens the side, but it seems the .env is not loaded. All you have to do is to hardcode the server's address here and rebuild the docker: frontend/src/utils/constants.js (change localhost here to your IP)
Author
Owner

@abibell commented on GitHub (Jun 20, 2023):

Same issue here. I created a fresh Docker setup from scratch 20 mins ago.
Screenshot 2023-06-20 155606

@abibell commented on GitHub (Jun 20, 2023): Same issue here. I created a fresh Docker setup from scratch 20 mins ago. ![Screenshot 2023-06-20 155606](https://github.com/Mintplex-Labs/anything-llm/assets/544653/5b677f07-a57d-4ddc-8062-e89142ff124b)
yindo changed title from API keys wont go green. to [GH-ISSUE #33] API keys wont go green. 2026-06-05 14:33:03 -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#22