#PaLM not showing
1 messages · Page 1 of 1 (latest)
In the .env file you could try to set it as user provided and load it from the UI, you’ll at least know if the the json is correct if you try this...
Also remember to restart the node workers
Sometimes can be a problem when the file didn’t exist upon first run
my json file is correct but when i put it /api/data it doesnt work
So just confirming
- The full path is
/api/data/auth.json - PALM_KEY in your .env is blank?
- You are running the latest version (check /package.json has 0.4.6)
i left PALM_KEY blank cuz idk what to set
Yes I think it has to be completely empty or commented out
so how do I fix it
Sorry I was just checking that you’ve reviewed all of the above and you’ve restarted both the frontend and backend scripts?
I think restarting the docker container restarts both of them
Yea it does. Have you also tried rebuilding the docker container?
Not just re-running but rebuilding
so I should try to redeploy the stacks?
You’ve lost me. I’ve got to head off anyway. Someone might be able to help later. In the meantime I suggest rebuilding your docker container using the docker compose —rm parameter
The next step after that would be to open terminal in the docker and confirm the files are there. Could be a file map thing
Chatgpt could probably direct you on how to do that.
I've tried to delete the whole stack and re-deployed it and pushed the auth.json to the path already
Failing that still, you’ll need to compile all your OS/setup information and post it here to see if someone can replicate the problem
Okay off for real now. Have a goood night/day
comment out PALM_KEY
ok let me try it
2023-05-20T09:06:33.326453557Z No 'auth.json' file (service account key) found in /api/data/ for PaLM models
and I'm assuming you have the file in api/data
you have PALM_KEY=PALM_KEY
yes
it should be completely removed
then?
PALM_KEY only exists to allow user_provided json from the frontend
but after removing it I still can't see PALM in the endpoint
so you can delete the PALM_KEY line
this may be due to building from docker image, if you are doing that
then you should set PALM_KEY=user_provided
so I can fix it by rebuilding it?
before I build it I have to put the auth.json in the /api/data?
yes
ok let me try it