Error: Failed to ingest your data - 401 but credentials are valid about gpt4-pdf-chatbot-langchain HOT 5 CLOSED

you can add in advance system settings under User Variable to match the Authorization but now my error code is 429. Too Many request

response: {
ok: false,
status: 429,
statusText: 'Too Many Requests',

from gpt4-pdf-chatbot-langchain.

Hey, I think this is a 401 unauthorized error, so there's an issue with your API key not the repo. Have you used up your 'usage' for the api key or violated any moderation terms or exceeded rate limits? Does the api key work through direct calls i.e. postman

from gpt4-pdf-chatbot-langchain.

Thanks mayooear - I checked with postman and using the same api key I can successfully get embeddings from https://api.openai.com/v1/embeddings

from gpt4-pdf-chatbot-langchain.

Strange - I noticed the Bearer in the error message is not the API key from my .env file.

Guess I need to figure out where that's coming from - it doesn't match any OpenAI api I have. 👎

]
error [Error: Request failed with status code 401] {
config: {
transitional: {
silentJSONParsing: true,
forcedJSONParsing: true,
clarifyTimeoutError: false
},
adapter: [AsyncFunction: fetchAdapter],
transformRequest: [ [Function: transformRequest] ],
transformResponse: [ [Function: transformResponse] ],
timeout: 0,
xsrfCookieName: 'XSRF-TOKEN',
xsrfHeaderName: 'X-XSRF-TOKEN',
maxContentLength: -1,
maxBodyLength: -1,
validateStatus: [Function: validateStatus],
headers: {
Accept: 'application/json, text/plain, /',
'Content-Type': 'application/json',
'User-Agent': 'OpenAI/NodeJS/3.2.1',
Authorization: 'Bearer sk-NOT_MY_API_KEY'
},

from gpt4-pdf-chatbot-langchain.

@hakimhaniff YOU ROCK.

Not sure how I missed that but I had an OLD env variable that had that key... saved my life. 👍

from gpt4-pdf-chatbot-langchain.