Derek Coleman & Associates Inc logoDerek Coleman & Associates Inc

Home / Support / Qdrant Vector Database on Ubuntu 24.04 LTS

Qdrant Vector Database on Ubuntu 24.04 LTS — Support & Quick Start

Qdrant Vector Database on Ubuntu 24.04 LTS — Qdrant is a high-performance vector database and similarity search engine for embeddings — the retrieval layer for RAG, semantic search and recommendations. Published by Derek Coleman & Associates Inc on the Azure Marketplace, deployed in your own Azur…

Email support Product page Azure Marketplace listing

At a glance

Application ports6333 (REST API), 6334 (gRPC) — API key required on both
Admin credential filesudo cat /root/qdrant-admin-credentials.txt
Sign in asAPI key (send it as the `api-key` header)
Service(s)qdrant
Configuration/etc/qdrant/config.yaml; API key in /etc/default/qdrant (QDRANT__SERVICE__API_KEY, root-only); data in /var/lib/qdrant/
Logsjournalctl -u qdrant -f
VersionQdrant 1.18.2
PlatformUbuntu 24.04 LTS

Quick start

  1. Deploy from the Azure Marketplace (Get It Now → Create), choosing your SSH key at the Administration step.
  2. Allow inbound SSH (22) for yourself plus the application port(s): 6333 (REST) and 6334 (gRPC) — to your application clients only — restrict to your own IP where possible. The in-image firewall already allows them; only the Network Security Group (NSG) keeps them closed.
  3. Read the API key (see First login below) and create your first collection with a PUT to /collections/<name>.
  4. Point your embedding pipeline or client library at http://<VM-IP>:6333 with the api-key header.

First login / credentials

This image generates its admin credential on the VM at first boot — nothing is pre-set. SSH into the VM with the username + key you chose at deploy, then print the generated credential:

ssh <your-username>@<VM-IP>
sudo cat /root/qdrant-admin-credentials.txt

Sign in as API key (send it as the `api-key` header).

  1. Print the credential file: the API key generated at first boot.
  2. Verify: curl -H 'api-key: <key>' http://<VM-IP>:6333/collections (health without auth: curl http://<VM-IP>:6333/healthz).
  3. Rotate the key by editing QDRANT__SERVICE__API_KEY in /etc/default/qdrant and restarting; put TLS in front before sending real data over the internet.

Authentication is an API key (api-key header), not a username/password. The web dashboard at http://<VM-IP>:6333/dashboard also asks for it.

Still stuck?

Email support@dcassociatesgroup.com (response within 1 business day) or send a message via the contact form. Include the offer name, VM size, region, and any log output — sudo journalctl -u <service> -n 100 usually tells the story.