-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[Bug] Inputting OpenAI API key throws weird error #1900
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
Comments
I was running into this issue myself but believe to have found the root cause: OpenAI is replacing user API keys with project API keys: User API keys follow the format My guess is that the validator for the input field does not accept that new format. When I paste a user API key into that field, it works as expected. I expect the form validation to fail, because the regex check fails in /dashboard/settings/_sections |
this is occurring on the publicly hosted version as well |
Confirmed that this is only happening with the new I generated a legacy key and I no longer get the |
A quick visual guide for users trying to solve this issue:
|
…api-key-throws-weird-error #1900 - bug inputting openai api key throws weird error
I think this may need to be reopened, as OpenAI no longer allows the creation of user API Keys. |
Uh oh!
There was an error while loading. Please reload this page.
Is there an existing issue for this?
Product Variant
Self-Hosted
Current Behavior
Inputting the API key into the relevant field throws an error, I assume, as API Key turns red and random red character appear below the input field "WtwH+r" (???) . This then triggers another error, I've never seen before triggers, saying chrome is unreachable (screenshotted). App behaves as expected beyond this. Took a long time to get RxV4 working so bummer to now deal with this when I get access to OpenAI.
Expected Behavior
Entering the OpenAI API key works as suggested by the app.
Steps To Reproduce
No response
What browsers are you seeing the problem on?
Firefox
What template are you using?
Azurill
Anything else?
Chrome log:
The text was updated successfully, but these errors were encountered: