patrikx3/redis-ui

Unable to connect to AWS ElasticCache Instance

andyast opened this issue · 4 comments

andyast commented

Getting the following error when running docker image in K8S using the manifests files. For what's it worth "Test Connection" says successful.

Config

{
      "list": [
        {
          "name": "Prod",
          "host": "master.<redacted>.cache.amazonaws.com",
          "port": 6379,
          "password": "<redacted>",
          "awsElastiCache": true
        }
      ]
}

Error

[P3XRS] [PID: 000007]  ParserError: Protocol error, got "\u0015" as reply type byte. Please report this.
    at handleError (/usr/local/lib/node_modules/p3x-redis-ui/node_modules/redis-parser/lib/parser.js:190:15)
    at parseType (/usr/local/lib/node_modules/p3x-redis-ui/node_modules/redis-parser/lib/parser.js:304:14) {
  offset: 1,
  buffer: '{"type":"Buffer","data":[21,0,0,0,2,1,0]}'
}

[P3XRS] [PID: 000007]  socket.io connection-connect added new socket.id NOa5AkPFyewyOQkvAAAB to undefined name with Prod

[P3XRS] [PID: 000007]  socket.io connection-connect undefined Prod connected
andyast commented

And Yes it is most likely an issue with redis-parser but I was wondering if anyone has successfully used AWS ElasticCache

p3x-robot commented

no idea, i am not following the changes in aws/azure/google. i only implemented for the original redis instances.

p3x-robot commented

And Yes it is most likely an issue with redis-parser but I was wondering if anyone has successfully used AWS ElasticCache

i think a few people are using it via google/azure/amazon.

esdee-git commented

worked for me after enabling Aws ElastiCache as pointed out in #12

  • 👍1