Skip to content
New issue

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

[Bug]: Unable to connect to AWS MemoryDB cluster through ssh tunnel #1547

Closed
esigma5 opened this issue Dec 29, 2022 · 3 comments
Closed

[Bug]: Unable to connect to AWS MemoryDB cluster through ssh tunnel #1547

esigma5 opened this issue Dec 29, 2022 · 3 comments
Labels
issue Something isn't working

Comments

@esigma5
Copy link

esigma5 commented Dec 29, 2022

Preconditions (Any important steps we need to know)
RedisInsightV2 installed on MacOS desktop. MemoryDB cluster recenly created. Start an ssh tunnel to an instance on the same vpc with conectivity to the cluster.

Steps to reproduce (How to reproduce what you found step by step)

  1. Create a memory DB cluster
  2. Start an ssh tunnel targetting the cluster's endpoint/port
  3. Attempt to create a connection using RedisInsight

Actual behavior (A short description of what you found)

  • Connection fails with a timeout error

Expected behavior (A short description of what you expected to find)

  • Should connect

Screenshots (Paste or drag-and-drop a screenshot or a link to a recording)

Standard logs

12/29/2022, 5:15:15 PM | INFO | ServerService | Getting server info. | {"stack":[]}
12/29/2022, 5:15:15 PM | INFO | SettingsService | Getting application settings. | {"stack":[]}
12/29/2022, 5:15:15 PM | INFO | SettingsService | Succeed to get application settings. | {"stack":[]}
12/29/2022, 5:15:15 PM | INFO | ServerService | Succeed to get server info. | {"stack":[]}
12/29/2022, 5:15:16 PM | INFO | DatabaseService | Getting databases list | {"stack":[]}
12/29/2022, 5:15:16 PM | INFO | SettingsService | Getting application settings. | {"stack":[]}
12/29/2022, 5:15:16 PM | INFO | SettingsService | Succeed to get application settings. | {"stack":[]}
12/29/2022, 5:15:16 PM | INFO | NotificationGateway | Client connected: cvsjEfNnp_DB3BuJAAAD | {"stack":[]}
12/29/2022, 5:15:21 PM | INFO | CaCertificateService | Getting CA certificate list. | {"stack":[]}
12/29/2022, 5:15:21 PM | INFO | ClientCertificateService | Getting client certificates list. | {"stack":[]}
12/29/2022, 5:15:43 PM | INFO | DatabaseService | Creating new database. | {"stack":[]}
12/29/2022, 5:15:43 PM | INFO | RedisService | Successfully connected to the redis database | {"stack":[]}
12/29/2022, 5:16:13 PM | ERROR |  | Request Timeout. POST /api/databases | {"stack":[{}]}

Error logs

12/29/2022, 5:16:13 PM | ERROR |  | Request Timeout. POST /api/databases | {"stack":[{}]}

Desktop screenshot:
Screenshot 2022-12-29 at 17 25 30

Using redis-cli client works just fine (so, connectivity from ec2 proxy instance to memorydb is not an issue):

redis-cli -c -h localhost  -p 11112 keys \*
(empty array)

Tried extending the request timeout, but although the timeout was effectively extended, it failed anyway:

REQUEST_TIMEOUT=30000 /Applications/RedisInsight-v2.app/Contents/MacOS/RedisInsight-v2

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

  • MacOS Ventura 13.0.1
  • RedisInsightV2 Version 2.16.0 (2.16.0.70400)
  • SSH tunnel command: ssh -i ~/.ssh/mykey -L 11112:cluster-dns:6379 ec2-user@ec2-instance-acting-as-jump-server-dns
  • No TLS was used
  • Tried connecting to a local redis server and it worked fine
@esigma5 esigma5 added the issue Something isn't working label Dec 29, 2022
@ArtemHoruzhenko
Copy link
Collaborator

@esigma5 Could you try on test build from this message? #1339 (comment)

@esigma5
Copy link
Author

esigma5 commented Jan 2, 2023

Hi @arthosofteq , thanks for the response.
I just tried your test build (mac flavor, Version 2.16.1-dev-70466 (2.16.1-dev-70466.70469)), but sadly the same error arised.

For the record, I tried using the web server version running inside the same VPC where the MemoryDB was located, using this guide as inspiration, and it worked fine (using the option "Connect to Redis database", because the "Elasticache Database" option did not work).

I will stick with the web version for now, since it seems to have the same if not more features, but of you would like me to try any other build, let me know.

@ViktarStarastsenka
Copy link
Collaborator

please try the Docker container - https://hub.docker.com/r/redis/redisinsight
re-open the ticket if the issue persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants