Topic: 404 Error with Pinecone Index in Next.js Project

Support
1

Hello Pinecone community,

I’m working on a Next.js application with the Hugging Face transformers library to generate embeddings for PDF/text files, which I then upsert into a Pinecone index. However, I’m encountering a 404 error that indicates Pinecone can’t locate my index. The error is similar to:

[Error [PineconeNotFoundError]: A call to https://index-two-jjor2qo.svc.aped-4627-b74a.pinecone.io/indexes returned HTTP status 404.]

Below are the details:

• Project & Index Setup :

• My Pinecone project is named “Default.”

• The index is called index-two, with 1024 dimensions, cosine metric.

• In the Pinecone dashboard, the environment/region is shown as us-east-1, but the subdomain has aped-4627-b74a.

• API Key & Code :

• In my .env, I have:
PINECONE_API_KEY=pcsk_****************************************

(copied from the Pinecone “API Keys” tab for the Default project). I’ve confirmed that the API key I’m using belongs to the same Pinecone “Default” project where my indexes reside, yet I still receive a 404 for both index-one and index-two.

My code (simplified) is:

const client = new Pinecone({
  apiKey: process.env.PINECONE_API_KEY!,
  controllerHostUrl: "https://index-two-jjor2qo.svc.aped-4627-b74a.pinecone.io",
});

const indexes = await client.listIndexes();
console.log("Indexes I see:", indexes);

const index = client.index("index-two");
await index.namespace("testspace").upsert([...]);

• Troubleshooting Steps :

  1. Confirmed spelling of index-two matches the dashboard.

  2. Verified @pinecone-database/pinecone is updated in my Next.js project.

  3. Created a new API key in the same Default project, replaced the old one, still 404.

  4. Tried logging all indexes (listIndexes()) — the 404 triggers before it prints anything.

  5. Double-checked no leftover references to a different index name.

  6. Encounter the same 404 if I try index-one or index-two.

• Request for Guidance :

• Am I using the correct environment/subdomain for these indexes?

• Are there any known region mismatches with aped-4627-b74a vs. us-east-1?

• Is there any other reason Pinecone would return 404 on /indexes for indexes that appear in the dashboard?

I am not posting my actual API key here, but it starts with pcsk_ and is directly from the Default project containing my indexes. Any guidance on how to resolve the “not found” error and ensure Pinecone recognizes my indexes would be greatly appreciated.

Thank you!

2

Hi @wlf32,

Welcome to the Pinecone Forum and thanks for posting!

I ran your code and got an error as well. Looking at our reference docs for list indexes, I think you can omit the controllerHostUrl. Your API key is tied to a specific project and listIndexes will pull up a list of all of the indexes in the corresponding project. The following code works for me:

const client = new Pinecone({ apiKey: 'PINECONE_API_KEY' })

const indexes = await client.listIndexes();
console.log("Indexes I see:", indexes);

Let me know if that helps. If not, I can help further troubleshoot.

Best,
Lauren

1 Like
3

Thank you so much for the suggestion to remove controllerHostUrl and let Pinecone infer the environment from my API key. That fixed my 404 error right away! Now I can see my indexes, and the code processes my documents without any issues. Thanks again for taking the time to walk me through this—your solution was exactly what I needed!

1 Like