401 Unauthorized exception calling the API

All our requests to Pinecone started failing today with a 401 Unauthorized exception. The stacktrace is unhelpful:

Failed to retrieve response: PineconeAuthorizationError: The API key you provided was rejected while calling https://xxx-yyy.svc.gcp-starter.pinecone.io/query. Please check your configuration values and try again. You can find the configuration values for your project in the Pinecone developer console at [https://app.pinecone.io](https://app.pinecone.io/)
at mapHttpStatusError (webpack-internal:///(rsc)/./node_modules/@pinecone-database/pinecone/dist/errors/http.js:181:20)
at eval (webpack-internal:///(rsc)/./node_modules/@pinecone-database/pinecone/dist/errors/handling.js:170:55)
at step (webpack-internal:///(rsc)/./node_modules/@pinecone-database/pinecone/dist/errors/handling.js:107:23)
at Object.eval [as next] (webpack-internal:///(rsc)/./node_modules/@pinecone-database/pinecone/dist/errors/handling.js:48:20)
at fulfilled (webpack-internal:///(rsc)/./node_modules/@pinecone-database/pinecone/dist/errors/handling.js:11:32)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
cause: undefined

We repeated the query with a new API key, and also tried calling the index from Python. Both failed. The Pinecone console also fails to load the index via the ‘Browse’ tab. The describe_index_stats API call on the console fails with a 401 Unauthorized error with the following response headers:

Access-Control-Allow-Origin: [https://app.pinecone.io](https://app.pinecone.io/)
Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
Content-Length: 12
Content-Type: text/plain
Date: Thu, 04 Apr 2024 20:35:17 GMT
Server: envoy
Via: 1.1 google
Www-Authenticate: Malformed domain
X-Pinecone-Auth-Rejected-Reason: Malformed domain

I can understand if the server is down, but that’s not the exception message I would expect in that case. How can we fix this error?

I have started to get a similar error suddenly. I am not sure if I did something wrong or is it a pinecone server related issue.

UnauthorizedException: (401)

Reason: Unauthorized
HTTP response headers: HTTPHeaderDict({'x-pinecone-auth-rejected-reason': 'Malformed domain', 'www-authenticate': 'Malformed domain', 'Content-Length': '12', 'content-type': 'text/plain', 'date': 'Thu, 04 Apr 2024 21:13:28 GMT', 'server': 'envoy', 'Via': '1.1 google', 'Alt-Svc': 'h3=":443"; ma=2592000,h3-29=":443"; ma=2592000'})
HTTP response body: Unauthorized
1 Like

We are on a starter index, what about you? It might be an issue impacting only starter indexes, although I don’t see incidents on the status page https://status.pinecone.io/

I created a support ticket, but was basically told they couldn’t help us because we aren’t a paying customer. Well, if the status page or exception message were helpful, I could figure something out, but at the moment we’re pretty stuck!

I’m experiencing the same issue on the starter plan, was working fine a few hours ago

Starter index too, and yes it was working a while ago.

Hi folks, let me look into this for you. I’ll update as soon as I know more.

Hello, I am facing the same problem.

The API doesn’t work and the platform keeps loading forever

Hello @connect,

I moved your post as I suspect it might be related to this thread. Can you please tell us what error message you’re getting?

Good news, this is resolved, and the free indexes should be working again.

1 Like

Give environment =“gcp-starter”

Hi - This is occuring again by the looks of it. Any workarounds available?

pinecone.core.client.exceptions.UnauthorizedException: (401)
Reason: Unauthorized
HTTP response headers: HTTPHeaderDict({‘Date’: ‘Thu, 11 Apr 2024 06:39:53 GMT’, ‘Content-Type’: ‘text/plain’, ‘Content-Length’: ‘12’, ‘Connection’: ‘keep-alive’, ‘x-pinecone-auth-rejected-reason’: ‘Malformed domain’, ‘www-authenticate’: ‘Malformed domain’, ‘server’: ‘envoy’})
HTTP response body: Unauthorized

Hello @rayking99,

We are aware of an issue affecting some of the Serverless and Starter indexes. We are currently investigating and will update our status with the progress.

This issue has been resolved.

A post was split to a new topic: Getting 401 Errors