Skip to content

BUG: Redis Connect failed #1401

@tenbeh5

Description

@tenbeh5

Please keep communication in ENGLISH to reach more contributors.

Describe the bug
Unable to connect AWS Elasticache with NOPERM for INFO cmd

To Reproduce
Steps to reproduce the behavior:

  1. Setup redis cluster with user auth that has no permission to INFO cmd
  2. Create new connection in dbgate, select redis and provide all necessary information
  3. See error
ReplyError: NOPERM User USERNAME has no permissions to run the 'info' command
    at parseError (/Applications/DbGate.app/Contents/Resources/app.asar/node_modules/redis-parser/lib/parser.js:179:12)
    at parseType (/Applications/DbGate.app/Contents/Resources/app.asar/node_modules/redis-parser/lib/parser.js:302:14)

Error JSON: {
  "command": {
    "name": "info",
    "args": []
  }
}

Connection: {
  "server": "***",
  "engine": "redis@dbgate-plugin-redis",
  "useSsl": true,
  "user": "***",
  "password": "***",
  "sslRejectUnauthorized": false,
  "skipSetName": false,
  "isReadOnly": false,
  "requestDbList": false
}

Platform: darwin

Expected behavior
dbgate should allow connectivity as regular redis-cli CMD should work as is without the getting the AWS Elasticache cluster's information. I have used Redis Insight with no issue connecting to the same AWS Elasticache cluster but would love to continue using dbgate if this issue is unblocked and consider getting premium.

Screenshots
If applicable, add screenshots to help explain your problem.

Version Information (please complete the following information):

  • OS: MacOS Tahoe
  • App Version: 7.1.4
  • Install source: brew install --cask dbgate
  • Type: Application
  • Database engine: ClickHouse, MongoDB, MySQL, Postgres, Redis

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions