We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The client can't connect when QDrant behind a NGINX reverse proxy.
Dashboard and curl connections to qdrant work when behind reverse proxy. @qdrant/js-client-rest can't connect when QDrant behind reverse proxy.
const { QdrantClient } = require("@qdrant/js-client-rest"); const dotenv = require("dotenv"); dotenv.config(); async function testQdrant() { try { const qdrant = new QdrantClient({ url: process.env.QDRANT_URL, // e.g., "http://your-qdrant-server:6333" apiKey: process.env.QDRANT_API_KEY, // Optional, if authentication is needed checkCompatibility: false }); const collections = await qdrant.getCollections(); console.log("Collections:", collections); } catch (error) { console.error("Error fetching collections:", error); } } testQdrant();
when connecting directly to QDrant though firewall it work without problem using either http or https when connecting via reverse proxy it times out.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The client can't connect when QDrant behind a NGINX reverse proxy.
Dashboard and curl connections to qdrant work when behind reverse proxy.
@qdrant/js-client-rest can't connect when QDrant behind reverse proxy.
when connecting directly to QDrant though firewall it work without problem using either http or https
when connecting via reverse proxy it times out.
The text was updated successfully, but these errors were encountered: