qishibo/AnotherRedisDesktopManager · warning

this.$t('message.info_disabled')

Error message

this.$t('message.info_disabled')

What it means

Shown when the INFO command fails with 'unknown command'. That string means the server (or a proxy in front of it) does not offer INFO at all — typically because it was disabled with rename-command INFO "" in redis.conf, a common hardening step, or the endpoint is a proxy (twemproxy-style) implementing only a subset of commands. Redis 6+ ACL users without the info permission (NOPERM) can also disable the status panel. The app degrades gracefully with a localized notice.

Source

Thrown at src/components/Status.vue:259

    initShow() {
      // set global info dict
      this.client.ardmInfo = {};

      this.client.info().then((reply) => {
        this.connectionStatus = this.initStatus(reply);
        this.client.ardmInfo = this.connectionStatus;

        // init db keys info
        if (this.isCluster) {
          this.initClusterKeys();
        }
        else {
          this.DBKeys = this.initDbKeys(this.connectionStatus);
        }
      }).catch((e) => {
        // info command may be disabled
        if (e.message.includes('unknown command')) {
          this.$message.error({
            message: this.$t('message.info_disabled'),
            duration: 3000,
          });
        }
        // no auth not show
        else if (e.message.includes('NOAUTH')) {} else {
          this.$message.error(e.message);
        }
      });
    },
    refreshInit() {
      this.refreshTimer && clearInterval(this.refreshTimer);

      if (this.autoRefresh) {
        this.initShow();

        this.refreshTimer = setInterval(() => {
          this.initShow();

View on GitHub (pinned to c149855106)

Solutions

1. If this tooling must show stats, re-enable INFO: remove rename-command INFO "" and restart, or grant +info to the ACL user
2. If INFO must stay disabled, accept the degraded status view and rely on redis-cli/monitoring
3. Verify you are connecting directly to Redis, not through a command-filtering proxy
4. For ACL setups, connect with a user that has +info

Example fix

# server side, redis.conf
# disabled:
rename-command INFO ""
# re-enable: delete the rename-command line, restart redis

# Redis 6+ ACL alternative (no restart of tooling needed)
ACL SETUSER gui_user >password ~* +@connection +@keyspace +info

.catch((e) => {
  const m = String(e.message);
  if (/unknown command/i.test(m)) {
    this.infoDisabled = true; // INFO disabled via rename-command: degrade
  } else if (/NOAUTH/.test(m)) {
    // auth required: connection layer handles it
  } else if (/NOPERM/.test(m)) {
    this.infoDisabled = true; // Redis 6+ ACL denial
  } else {
    this.$message.error(m);
  }
})

When it happens

Trigger: Connecting to a hardened Redis where INFO was renamed to the empty string; a Redis 6+ ACL user lacking +info; a proxy or managed endpoint that does not implement INFO.

Common situations: Production servers hardened per security guides, Docker images disabling INFO, teams behind twemproxy/predixy, ACL-restricted app users reused for GUI tools.

Related errors

• e.message
• e.message
• Type Error: ${e.message}
• Exists Error: ${e.message}
• Expire Error: ${e.message}

AI-assisted analysis of qishibo/AnotherRedisDesktopManager@c149855106 (2026-08-22). Data as JSON: /api/errors/eb86b93fd0b53aa3. Report an issue: GitHub.