error [ErrorWithoutStackTrace: PineconeClient: Error calling upsert: ErrorWithoutStackTrace: PineconeClient: Error calling upsertRaw: FetchError: The request failed and the interceptors did not return an alternative response]

[usbleb26]

I am running into an error with pinecone. I have confirmed I am running on the latest node, my pinecone index dimensions are 1536 and my API keys and index name has been confirmed correct. My PDF is only 429KB. the error I am receiving is:

error [ErrorWithoutStackTrace: PineconeClient: Error calling upsert: ErrorWithoutStackTrace: PineconeClient: Error calling upsertRaw: FetchError: The request failed and the interceptors did not return an alternative response]

any thoughts on what could be wrong? Thanks in advance!

[PrimeObjects]

got same error.

[theesfeld]

same.

[ana-lam]

Me as well

[Kriswilkinson]

Me 5

[LeVuMinhHuy]

me 6

// update refer to this issue, i tried again with short pinecone index version, and it worked

[zhuweiji]

me 6

// update refer to this issue, i tried again with short pinecone index version, and it worked

to elaborate more on this:

for the PINECONE_INDEX_NAME value in the .env file, use my-index instead of my-index-f134567....gcp.pinecone.io

[kevin-huff]

Had this issue looks like you just gotta wait a while after creating an index. Patience is a virtue.

[OdinM13]

bump, still have the same error and did not see any solution that worked

[crsepulv]

in my case the name of the index was wrong.

[ronen770]

I removed the "-" from my index name and this solved the problem. index-1 -> index

[chiencarlos11]

wrong index name for me too... I thought index name means the url of the index like "https://testing-.svc.asia-southeast1-gcp-free.pinecone.io" but it is just "testing"

[dosubot[bot]]

Hi, @usbleb26! I'm Dosu, and I'm helping the gpt4-pdf-chatbot-langchain team manage their backlog. I wanted to let you know that we are marking this issue as stale.

Based on my understanding, you encountered an error with Pinecone while performing an upsert operation. Other users have reported similar issues, and there have been some suggestions provided by other users that seem to resolve the problem. One user, "LeVuMinhHuy", found a workaround by using a shorter Pinecone index version. Another user, "zhuweiji", suggested using a different value for the PINECONE_INDEX_NAME in the .env file. Additionally, some users mentioned that waiting for a while after creating an index or ensuring the correct index name resolved the issue.

Before we close this issue, we wanted to check with you if it is still relevant to the latest version of the gpt4-pdf-chatbot-langchain repository. If it is, please let us know by commenting on the issue. Otherwise, feel free to close the issue yourself, or the issue will be automatically closed in 7 days.

Thank you for your understanding and contribution to the gpt4-pdf-chatbot-langchain project!