[BUG] Cannot add database

[piankma]

Preconditions

Steps to reproduce

• Add database connection
  

Actual behavior
Unclear message

Logs aren't useful

Expected behavior
Well, a successful connection.

Screenshots
Above

Additional context (Operating system, version of Redis Insight, Redis database version, Redis module version, database type, connection type, logs, or any other information)

• macOS connected via Remote-SSH plugin to RHEL 9.6
  • cannot be verified without the remote connection due to firewall
• Redis for VSCode v1.2.0, also occurred on previous versions
• Redis v7.4.1 with FalkorDB v4.8.5 extension (also happened before its installation)

[dantovska]

Hi @piankma,

Thanks for reporting the issue!

We suspect that it might be something due to installing Redis for VS Code in remote environment. We do not support remote development officially and we've recently added this statement to the README:
"If you encounter an error using Redis for VS Code with Visual Studio Code Remote Development, it may be due to an OS mismatch between your local and remote environments, which can lead to the wrong extension being installed remotely.
As an alternative, you can run Redis for VS Code locally and connect to your remote Redis database via SSH directly within the extension."

Since you cannot try it on your own machine because of the firewall, I suggest to try installing on different images...

We are currently working on a bunch of new features, improvements and enhancing logging on the extension, so we should be able to troubleshoot your case easier from the logs after the following release.

If you are curious and want to play around with the extension itself, you can either try running the extension locally using these steps - run Redis for VS Code locally, or use the appropriate latest build (not yet released and could be unstable) for your environment - latest builds installing the extension from VSIX instead from the marketplace:

The logs like "Something went wrong" will be visible in the console (Help -> Toggle Developer Tools):

[dempc6469]

same issue here. what a bummer ...

[ronal-vargas]

Something was wrong!

[huang1996]

Something was wrong!

可以看看这个，在连接远程服务器进行开发时会出现这个BUG，临时解决方案是在vscode添加5541的端口转发。

[Hyperclaw79]

The issue might not just be related to Remote server. My setup is inside a devcontainer where I've got Redis running in a kubernetes cluster. I have the port 6379 port-forwarded so it should practically be same as running Redis locally from the extension's pov.
I definitely remember it working a while ago. I had to reinstall Redis today from Bitnami Legacy Helm chart and the extension isn't connecting anymore. And pretty sure the issue is local to this extension because I got it working with another extension (which had a horrendous UI).
I can provide you whatever logs you need if it will help pinpoint the root cause for the vague error.

[piankma]

The issue might not just be related to Remote server. My setup is inside a devcontainer where I've got Redis running in a kubernetes cluster.

I think it's working the same way - through connecting to a remote vscode instance.

[Hyperclaw79]

The issue might not just be related to Remote server. My setup is inside a devcontainer where I've got Redis running in a kubernetes cluster.

I think it's working the same way - through connecting to a remote vscode instance.

I think there's a subtle nuance involved as there can be four possible setups:

1. Both Redis and the Extension are running locally.
2. Redis is running in a remote container while the Extension is installed locally. (Most of the setups mentioned here)
3. Both Redis and Extension are running as part of a devcontainer. (My setup. In this case, they're both in the same environment but the environment itself is remote from the host system)
4. Redis is running locally but the Extension is inside a remote container. (very rare case)

[nbrinks]

Also having problems with the devcontainer use case. I am launching redis from a docker compose file in my devcontainer and trying to use this extension to connect to it. I get the same "Something was wrong!" message. 😕

2025-11-03T21:30:34.620Z - [Core] Extension activated
2025-11-03T21:30:34.625Z - [Core] Current version: 1.4.0
2025-11-03T21:30:34.627Z - [Server] Starting at port: 5541
2025-11-03T21:30:36.747Z - [Service Auth] Initializing service auth
2025-11-03T21:30:36.747Z - [Service Auth] Service auth initialized
2025-11-03T21:30:36.747Z - [Server] BE started

Would love for this to work within a devcontainer.

[SpartanDigitalDotNet]

I'm having an issue with Azure Managed Redis -- they don't use a username and this extension will not allow empty usernames.
redis://:<access_key>@<your_redis_host>:<port> is all that's needed (seems odd to me, but that works for my app)

Any help will be greatly appreciated -- AI after hours of attempts failed.

[moisesbites]

Most of the Redis instances I manage are on remote servers, accessible only via SSH. I use VS Code with Remote-SSH to manage these systems, and Redis is only accessible from the remote server context (no direct access from my local machine).

Even using an Ubuntu workstation connected via Remote-SSH to an Ubuntu server (both with the same operating system), the same error occurs ("Something went wrong!" or similar). It seems the extension doesn't use the Redis installed locally in VS Code to establish the connection—it requires the extension to be installed and running on the remote server.

It would be extremely useful and valuable if the extension supported direct connection to Redis from the local server via an SSH tunnel (or proxy) managed by VS Code Remote-SSH, without the need for installation on the remote host. Or at least that the extension supported being installed on the server and working correctly via SSH like Mongodb extension or Postgres extension.

I would appreciate it if this limitation could be corrected or improved in a future version!