Roo-Code: Codebase Indexing: TypeError: fetch failed during Qdrant connection despite successful external connectivity
App Version
3.18.5 (582a117a)
API Provider
OpenAI
Model Used
text-embedding-3-small
🔁 Steps to Reproduce
- Setup
VSCode: Version: 1.101.0-insider (system setup) Commit: b4912823f452c08e81283d8fd8dd9e758a00f5f4 Date: 2025-05-28T05:45:00.228Z Electron: 35.4.0 ElectronBuildId: 11602177 Chromium: 134.0.6998.205 Node.js: 22.15.0 V8: 13.4.114.21-electron.0 OS: Windows_NT x64 10.0.22635
Qdrant Deployment: Qdrant is deployed using the official qdrant/qdrant:latest Docker image (from Docker Hub) via Coolify, which handles container orchestration and uses Traefik as a reverse proxy for external access.
Roo Code Settings: “Enable Codebase Indexing” is enabled. Qdrant URL: https://[YOUR_QDRANT_DOMAIN] (e.g., https://qdrant.example.com) Qdrant API Key: [YOUR_QDRANT_API_KEY_VALUE] Embedding Provider: OpenAI OpenAI Model: text-embedding-3-small
-
Exact Actions After configuring and saving the settings, the extension attempts to initialize the codebase indexing.
-
What happened after each step Immediately upon attempting to start indexing, the VS Code Dev Tool panel (specifically “Roo Code” and “Log (Extension Host)”) displays a series of TypeError: fetch failed errors related to Qdrant collection initialization and cleanup.
💥 Outcome Summary
Expected indexing to start but got an error instead in the dev console.
📄 Relevant Logs or Errors (Optional)
console.ts:137 [Extension Host] [QdrantVectorStore] Warning during getCollectionInfo for "ws-f5009f6ef98f9736". Collection may not exist or another error occurred: fetch failed
[Extension Host] [QdrantVectorStore] Failed to initialize Qdrant collection "ws-f5009f6ef98f9736": fetch failed
[QdrantVectorStore] Failed to initialize Qdrant collection "ws-f5009f6ef98f9736": fetch failed
[Extension Host] [CodeIndexOrchestrator] Error during indexing: TypeError: fetch failed
at node:internal/deps/undici/undici:13510:13
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at runNextTicks (node:internal/process/task_queues:69:3)
at listOnTimeout (node:internal/timers:549:9)
at processTimers (node:internal/timers:523:7)
at AJ.globalThis.fetch
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 7
- Comments: 40
i cant get it to conenct to local or cloud qdrant
This issue is scoped already and it’s basically waiting for someone to take it: https://github.com/RooCodeInc/Roo-Code/issues/4092#issuecomment-2935680896
If anyone is interested on tackling this please let me know.
@fev4 thank you
Your curl test confirms that the Qdrant server is externally reachable, the API key is valid, and SSL is working as expected. However, Roo Code’s codebase indexing still fails with a
TypeError: fetch failedduring Qdrant collection initialization.Based on the available documentation, there are no specific troubleshooting steps for this error or for setups involving Docker and Traefik as a reverse proxy. The docs only confirm that Qdrant must be accessible at the URL you provide, and that the API key (if used) must be correct, but do not address this scenario directly [source].
Given your setup and the fact that curl works but Roo Code does not, the issue is likely related to how the extension (running in VS Code/Electron/Node.js) handles HTTPS requests, headers, or proxying. Here are the most actionable next steps:
api-key) and not stripping or altering them for requests coming from VS Code.--ignore-certificate-errorsflag (for testing only) to rule out certificate trust issues.The Roo Code documentation does not currently provide further guidance on this error or on reverse proxy setups with Traefik and Docker. If the above steps do not resolve the issue, you may need to review your Traefik configuration or consult Qdrant’s own documentation/community for reverse proxy best practices.
To reply, just mention my name @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

@dosu
result was:
this confirms the qdrant server works, the api key works (and using the correct protocol)