Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API KEY error processing #793

Open
contabilulistet2 opened this issue Dec 17, 2024 · 6 comments
Open

API KEY error processing #793

contabilulistet2 opened this issue Dec 17, 2024 · 6 comments

Comments

@contabilulistet2
Copy link

contabilulistet2 commented Dec 17, 2024

Describe the bug

Hello,
No matter the Provider selected, I m getting the same error.
Providers selected in settings, API KEY set in .env.local and /or UI.
WIN 11/Docker
Release v0.0.2
Chrome, Edge, Chrome Canary

Link to the Bolt URL that caused the error

http://localhost:5173/

Steps to reproduce

  1. GoTo http://localhost:5173/
  2. Select Provider
  3. Insert API KEY
  4. Create a TODO app
  5. there was an error processing your request: an error occurred

Expected behavior

Expected to start the LLM selected and create project files

Screen Recording / Screenshot

image

Platform

  • OS: Windows, 11
  • Browser: [Chrome, Edge, Chrome Canary
  • Version: Release v0.0.2

Provider Used

Any from the list

Model Used

No response

Additional context

No response

@dustinwloring1988
Copy link
Collaborator

3 quick questions:

  1. please ensure you have the latest version (check for update in the debug tab)
  2. Are there any errors in the terminal
  3. When getting the api keys did you add money to the account

@contabilulistet2
Copy link
Author

contabilulistet2 commented Dec 17, 2024

Thank you Dustin for the quick response.

  • I have the latest version
  • ERR_CONNECTION_REFUSED
  • getting the same error for Ollama as well
    2 days ago it worked, before the pull origin

@dustinwloring1988
Copy link
Collaborator

try to add the api keys and base url in the settings menu and see if this helps

@biratrai
Copy link

biratrai commented Dec 17, 2024

Seeing the same error. Do we need to do anything after putting the api keys in env.local life just save the file?

Google api worked only after putting the api keys from the WebWindow

@contabilulistet2
Copy link
Author

Seeing the same error. Do we need to do anything after putting the api keys in env.local life just save the file?

Google api worked only after putting the api keys from the WebWindow

yes, did the same and it is now the only one working

@megaman5
Copy link

For me, instead of running it with docker-compose --profile development up
I used
docker run -p 5173:5173 --env-file .env.local bolt-ai:development
which apparently caused it to properly load the env file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants