I setup a Deepseek account and copied in my api key but received a 401 error when running bolt.ai. Has anyone else experienced this?
Are you running via docker? If so, it looks like the env var didnāt make it to the docker-compose.yaml and Dockerfile. Please confirm and Iāll add an issue, should be a quick fix.
Had issues getting docker to work. Running directly from NPM.
I just updated my codebase and tried docker again. 127.0.0.1 refuses to connect. When I run docker it launches the server but I do have the follow error: 2024-11-14 12:56:00 ./bindings.sh: line 12: .env.local: No such file or directory even though the env.local file is in the folder (see screenshot). Maybe thereās something wrong with the file?
(Iām on a mac)
Update: Still not working. the api does not work when entered directly in the interface. I double checked to make sure itās correct - it is.
Can you try with this PR
Sure. How do I pull just that pull request in Git?
1 Like
Hey there,
This PR is now merged into main, so you can try by doing a new pull. Iāll be monitoring results and this one was one of the first that came up (Deepseek support), so I may ask for assistance with testing that specific provider. Cheers!
Also for future reference, you can navigate to the source of a pull request via a link at the top of the page to the sourceās repo. I usually just git clone that repo in a separate āreviewā or ātestā directory and replace it as needed.
1 Like
I will give Deepseek a test tomorrow
1 Like
I tested it. When I input the api key via the UI, it works (Iām experiencing another error but Iām not sure if itās Deepseek related).
When I only have the key in the .env file, I still get a 401 error.
1 Like
Seems like a bug fix.
1 Like
I think I might take some time on Docker today, Iāll make sure to include this as part of testing (Docker and non-Docker setups).
1 Like