chromadb-admin icon indicating copy to clipboard operation
chromadb-admin copied to clipboard

`TypeError: Failed to parse URL from 10.152.183.193/api/v2/tenants/khteh`

Open khteh opened this issue 9 months ago • 2 comments

 ⨯ Error: Could not connect to tenant khteh. Are you sure it exists? Underlying error:
TypeError: Failed to parse URL from 10.152.183.193/api/v2/tenants/khteh
    at validateTenantDatabase (webpack-internal:///(rsc)/./node_modules/chromadb/dist/chromadb.mjs:10687:11)
    at async ChromaClient.listCollections (webpack-internal:///(rsc)/./node_modules/chromadb/dist/chromadb.mjs:12130:5)
    at async fetchCollections (webpack-internal:///(rsc)/./src/lib/server/db.ts:41:25)
    at async GET (webpack-internal:///(rsc)/./src/app/api/collections/route.ts:17:22)
    at async /usr/src/Databases/chromadb-admin/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:53446
    at async e_.execute (/usr/src/Databases/chromadb-admin/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:44747)
    at async e_.handle (/usr/src/Databases/chromadb-admin/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:54700)
    at async doRender (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/base-server.js:1377:42)
    at async cacheEntry.responseCache.get.routeKind (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/base-server.js:1599:28)
    at async DevServer.renderToResponseWithComponentsImpl (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/base-server.js:1507:28)
    at async DevServer.renderPageComponent (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/base-server.js:1924:24)
    at async DevServer.renderToResponseImpl (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/base-server.js:1962:32)
    at async DevServer.pipeImpl (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/base-server.js:920:25)
    at async NextNodeServer.handleCatchallRenderRequest (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/next-server.js:272:17)
    at async DevServer.handleRequestImpl (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/base-server.js:816:17)
    at async /usr/src/Databases/chromadb-admin/node_modules/next/dist/server/dev/next-dev-server.js:339:20
    at async Span.traceAsyncFn (/usr/src/Databases/chromadb-admin/node_modules/next/dist/trace/trace.js:154:20)
    at async DevServer.handleRequest (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/dev/next-dev-server.js:336:24)
    at async invokeRender (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/lib/router-server.js:174:21)
    at async handleRequest (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/lib/router-server.js:353:24)
    at async requestHandlerImpl (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/lib/router-server.js:377:13)
    at async Server.requestListener (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/lib/start-server.js:141:13)
 GET /api/collections?connectionString=10.152.183.193&tenant=khteh&database=LLM-RAG-Agent 500 in 4ms

Image

khteh avatar Apr 08 '25 05:04 khteh

@khteh

The error occurred because the port number was missing in the connection string.

I've just committed a fix that automatically appends the default port number (8000).

Could you please verify if this resolves the issue?

flanker avatar Apr 12 '25 02:04 flanker

 ⨯ ChromaConnectionError: Failed to connect to chromadb. Make sure your server is running and try again. If you are running from a browser, make sure that your chromadb instance is configured to allow requests from the current origin using the CHROMA_SERVER_CORS_ALLOW_ORIGINS environment variable.
    at chromaFetch (webpack-internal:///(rsc)/./node_modules/chromadb/dist/chromadb.mjs:10897:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async AdminClient.getTenant (webpack-internal:///(rsc)/./node_modules/chromadb/dist/chromadb.mjs:11035:23)
    ... 21 lines matching cause stack trace ...
    at async Server.requestListener (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/lib/start-server.js:141:13) {
  cause: TypeError: fetch failed
      at node:internal/deps/undici/undici:13502:13
      at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
      at async chromaFetch (webpack-internal:///(rsc)/./node_modules/chromadb/dist/chromadb.mjs:10853:18)
      at async AdminClient.getTenant (webpack-internal:///(rsc)/./node_modules/chromadb/dist/chromadb.mjs:11035:23)
      at async validateTenantDatabase (webpack-internal:///(rsc)/./node_modules/chromadb/dist/chromadb.mjs:10682:5)
      at async ChromaClient.listCollections (webpack-internal:///(rsc)/./node_modules/chromadb/dist/chromadb.mjs:12130:5)
      at async fetchCollections (webpack-internal:///(rsc)/./src/lib/server/db.ts:41:25)
      at async GET (webpack-internal:///(rsc)/./src/app/api/collections/route.ts:17:22)
      at async /usr/src/Databases/chromadb-admin/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:53446
      at async e_.execute (/usr/src/Databases/chromadb-admin/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:44747)
      at async e_.handle (/usr/src/Databases/chromadb-admin/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:54700)
      at async doRender (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/base-server.js:1377:42)
      at async cacheEntry.responseCache.get.routeKind (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/base-server.js:1599:28)
      at async DevServer.renderToResponseWithComponentsImpl (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/base-server.js:1507:28)
      at async DevServer.renderPageComponent (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/base-server.js:1924:24)
      at async DevServer.renderToResponseImpl (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/base-server.js:1962:32)
      at async DevServer.pipeImpl (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/base-server.js:920:25)
      at async NextNodeServer.handleCatchallRenderRequest (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/next-server.js:272:17)
      at async DevServer.handleRequestImpl (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/base-server.js:816:17)
      at async /usr/src/Databases/chromadb-admin/node_modules/next/dist/server/dev/next-dev-server.js:339:20
      at async Span.traceAsyncFn (/usr/src/Databases/chromadb-admin/node_modules/next/dist/trace/trace.js:154:20)
      at async DevServer.handleRequest (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/dev/next-dev-server.js:336:24)
      at async invokeRender (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/lib/router-server.js:174:21)
      at async handleRequest (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/lib/router-server.js:353:24)
      at async requestHandlerImpl (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/lib/router-server.js:377:13)
      at async Server.requestListener (/usr/src/Databases/chromadb-admin/node_modules/next/dist/server/lib/start-server.js:141:13) {
    [cause]: ConnectTimeoutError: Connect Timeout Error (attempted address: 10.152.183.193:8000, timeout: 10000ms)
        at onConnectTimeout (node:internal/deps/undici/undici:2602:28)
        at Immediate._onImmediate (node:internal/deps/undici/undici:2583:11)
        at process.processImmediate (node:internal/timers:508:21)
        at process.callbackTrampoline (node:internal/async_hooks:130:17) {
      code: 'UND_ERR_CONNECT_TIMEOUT'
    }
  }
}
 GET /api/collections?connectionString=http://10.152.183.193:8000&tenant=khteh&database=LLM-RAG-Agent 500 in 10502ms

I have that ENV set.

khteh avatar Apr 12 '25 03:04 khteh