Fix: Cannot reach this Meilisearch server

You're seeing "Cannot reach this Meilisearch server" on the instance page, the connectivity check on the new-instance form, or any of the management tabs. This article walks through the most common causes and the fix for each.

What this means

AdminDex's backend made an HTTP request to the URL you saved for this instance and either got a network error (TCP refused, DNS failure, timeout) or a non-2xx response. The instance row in our database is fine — only the live connection failed.

Common causes

• The Meilisearch server is down or restarting.
• The URL is wrong (typo, missing protocol, wrong port).
• The server is on a private network and not reachable from AdminDex.
• A firewall or security group is blocking incoming HTTP traffic on the Meilisearch port.
• The admin key was rotated on the Meilisearch side but not updated in AdminDex.
• The server's TLS certificate expired or doesn't match the hostname.

How to fix it

1. Verify the server is running

From your own machine (or any machine that can reach the server), run:

curl -i https://your-meilisearch-url/health

You should see HTTP/1.1 200 OK and a JSON body like {"status":"available"}. If this fails, the issue is with your Meilisearch server itself, not AdminDex. Restart it and try again.

2. Check the URL exactly

Open the instance edit page in AdminDex and compare the URL you saved against the one in your Meilisearch deployment. Common mistakes:

• Missing protocol — should be https:// or http://
• Wrong port — Meilisearch defaults to :7700
• Trailing slash — AdminDex strips trailing slashes on save, but other URL fragments will break
• Using a docker service name (e.g. meilisearch:7700) when AdminDex is running outside that docker network

3. Verify the server is reachable from the public internet

AdminDex's backend lives in a different network from your Meilisearch server. If your server is on a private VPC or behind a corporate firewall, AdminDex literally can't reach it. Options:

• Expose the server publicly with proper firewall rules and HTTPS
• Put it behind a reverse proxy with allowlisted IPs (ours are documented in the contact response if you ask)
• Wait for self-hosted AdminDex, which is on the roadmap

4. Test the admin key

From your machine, try:

curl -i -H "Authorization: Bearer YOUR_ADMIN_KEY" https://your-meilisearch-url/keys

If this returns HTTP/1.1 401 Unauthorized, your admin key is wrong or has been rotated. Update it on the AdminDex instance edit page.

5. Check the TLS certificate

If your URL starts with https:// and the server has an expired or mismatched cert, the connection will fail with a TLS error. Renew the cert (Let's Encrypt is free) or temporarily switch to http:// if the server is on a trusted private network.

Still stuck?

If none of these fixes work, send us the URL (with the key redacted), the exact error message you're seeing in AdminDex, and the output of curl -i your-url/health. Get in touch and we'll dig in.