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.

Sign up for GitHub

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

Jump to bottom

Can't save the groq api key #937

Open
Howe829 opened this issue Jan 30, 2025 · 5 comments · May be fixed by #1082
Open

Can't save the groq api key #937

Howe829 opened this issue Jan 30, 2025 · 5 comments · May be fixed by #1082
Assignees
@alexhancock @yingjiehe-xyz
Labels
bug Something isn't working ui

Comments

@Howe829
Copy link

Howe829 commented Jan 30, 2025

Describe the bug
Get 403 error after configure the groq provider

Image Image
@salman1993 salman1993 added bug Something isn't working ui labels Jan 30, 2025
@yingjiehe-xyz
Copy link
Collaborator

could you check whether you have the invalid key?

@alexhancock
Copy link
Collaborator

Yes @Howe829 I have the same question. Do you know if this was a valid key entered? Could you try the reset provider option from the menu on the top right and re-attempt entry of the key?

Image

@sinjab
Copy link

sinjab commented Jan 31, 2025 •
edited
Loading

@alexhancock Using "reset provider" will just open the providers window. It will not reset them. How can I correct the previously entered wrong settings.

@yingjiehe-xyz
Copy link
Collaborator

I think you can go to Settings -> Models Browse -> Models configure and then you can change the API key. Remember to reload the window or reset provider

Image

@nickmimic
Copy link

Using Claude, mine says:

Ran into this error: Authentication error: Authentication failed. Please ensure your API keys are valid and have the required permissions. Status: 403 Forbidden. Response: Some(Object {"error": Object {"message": String("Request not allowed"), "type": String("forbidden")}}). Please retry if you think this is a transient or recoverable error.

API key is new anthropic console shows it's never been used. I have sufficient funds in the account too. My other API key is working fine for Cursor.

jasonkneen added a commit to jasonkneen/goose that referenced this issue Feb 5, 2025
@jasonkneen
Fix groq API key saving issue
1e1c110 
Fixes block#937

Update the `post` method in `crates/goose/src/providers/groq.rs` to handle the API request correctly and return a successful response if the API key is valid.

* Change the return type of the `post` method to `Result<Value, ProviderError>` and add error handling for invalid API key or insufficient permissions.
* Change the return type of the `send_message` method to `Result<(Message, ProviderUsage), ProviderError>`.

Update the `configure_provider_dialog` function in `crates/goose-cli/src/commands/configure.rs` to handle the provider configuration process correctly.

* Change the condition to check if the configuration exists using parentheses.

---

For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/block/goose/issues/937?shareId=XXXX-XXXX-XXXX-XXXX).
@jasonkneen jasonkneen linked a pull request Feb 5, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexhancock alexhancock

@yingjiehe-xyz yingjiehe-xyz

Labels
bug Something isn't working ui
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix groq API key saving issue jasonkneen/goose
6 participants
@alexhancock @sinjab @salman1993 @nickmimic @Howe829 @yingjiehe-xyz