Skip to main content
0 reactions

How to Connect Valkey Admin to a Valkey Server

Featured card titled Connect Valkey Admin to Valkey, with a form showing Host localhost, Port 6379, an unticked Use TLS box and a Connect button.
Connect Valkey Admin to Valkey.

Valkey® Admin works with a server only after you add a connection to it. The Add Connection form has a dozen fields, but the Valkey on your own computer needs only a few of them.

By the end, Valkey Admin is connected to your Valkey and shows its Dashboard.

Note: Every command and screen on this page is real, from Valkey Admin 1.3.0 connected to Valkey 9.1 on an Apple silicon Mac with macOS 26.

Prerequisites

  • Valkey running on your computer, on port 6379.
  • Valkey Admin open: the desktop app or the web version in Docker.

Step 1: Open the Add Connection Form

Open Valkey Admin (the desktop app or the Docker version) and click + Add Connection on the Connections page. The form opens with these defaults:

The Valkey Admin Add Connection form in the macOS desktop app with its defaults: Endpoint Type Node, an empty Alias, Host showing localhost as a hint, Port 6379, Auth Type Password, Database 0, and Use TLS and Verify TLS Certificate both ticked.
The form’s defaults. Use TLS starts ticked.
  • Endpoint Type: Node for a single server. Discovery is for a cluster, where Valkey Admin finds the other nodes itself.
  • Alias: a name for the connection.
  • Host and Port: where the server is. Valkey’s usual port is 6379.
  • Auth Type, Username and Password: for a server that asks for a password. Leave them empty for a local Valkey without one. AWS IAM and GCP IAM are for Valkey on those clouds.
  • Database: the numbered database to open, 0 by default.
  • Use TLS and Verify TLS Certificate: for servers that encrypt their connections. Both start ticked.

Step 2: Fill In the Fields for Your Valkey

  1. Alias: Local Valkey.
  2. Host: localhost in the desktop app. In the Docker version, host.docker.internal, because localhost inside the container is the container itself.
  3. Port: leave 6379.
  4. Untick Use TLS: the Valkey on your computer doesn’t use TLS. Valkey Admin then warns that the connection won’t be encrypted, which is expected here.
The Add Connection form filled in with Alias Local Valkey, Host localhost, Port 6379, Use TLS unticked, Verify TLS Certificate ticked, and a warning that disabling TLS means the connection will not be encrypted.
For the Valkey on your computer: localhost, port 6379, Use TLS unticked.

Step 3: Connect

Click Connect. Valkey Admin opens the Dashboard of the server, named after its host, port and database: localhost-6379-db0.

The Valkey Admin desktop app Dashboard for instance localhost-6379-db0, with cards showing Total Memory infinity, Used Memory 1.49 MB, Operations 480 and Hit Ratio 97.62 percent.
Connected: the Dashboard of localhost-6379-db0.

Common Mistakes

MistakeWhat happensDo this instead
Typing localhost in the Docker versionValkey Admin looks for Valkey inside its own containerType host.docker.internal
Planning to switch databases later with SELECTSend Command blocks SELECTSet Database in this form

Troubleshooting

ProblemCauseFix
failed to lookup address information: Name or service not knownThe Docker container can’t find host.docker.internalFixed: failed to lookup address information: Name or service not known (Valkey Admin in Docker)

FAQ

Can I connect to more than one server?

Yes. Add one connection for each server.

Does Valkey Admin remember my password?

Not in the web version: its known limitations (opens in a new tab) say it asks for the password again after a page reload or in a new tab.

Conclusion

For the Valkey on your computer, type the host, keep port 6379, untick Use TLS and click Connect. Use localhost in the desktop app and host.docker.internal in Docker.

Additional Resources

Valkey® is a registered trademark of LF Projects, LLC. Redis® is a registered trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd. Other names mentioned are trademarks of their respective owners. JD Bots isn’t affiliated with the Valkey project, LF Projects or Redis Ltd., and isn’t endorsed, supported or certified by them.

0 comments