What causes "${this.$t('message.update_error')}: ${error}" in qishibo/AnotherRedisDesktopManager?

Restore connectivity and retry the update check

qishibo/AnotherRedisDesktopManager · warning

${this.$t('message.update_error')}: ${error}

Error message

${this.$t('message.update_error')}: ${error}

What it means

A generic electron-updater failure toast: the update check could not reach the update provider. The matched strings are Chromium network error codes — err_internet_disconnected, err_name_not_resolved (DNS), err_connection_refused — surfaced by the autoUpdater when GitHub Releases (or the configured generic provider) is unreachable.

Source

Thrown at src/components/UpdateCheck.vue:94

      ipcRenderer.on('update-error', (event, arg) => {
        this.resetDownloadProcess();

        let message = '';
        const error = (arg.code ? arg.code : arg.message).toLowerCase();

        // auto update check at app init
        if (!this.manual || !error) {
          return;
        }

        // mac not support auto update
        if (error.includes('zip') && error.includes('file')) {
          message = this.$t('message.mac_not_support_auto_update');
        }

        // err_internet_disconnected err_name_not_resolved err_connection_refused
        else {
          message = `${this.$t('message.update_error')}: ${error}`;
        }

        this.$notify.error({
          message,
          duration: 0,
          dangerouslyUseHTMLString: true,
        });
      });

      ipcRenderer.on('download-progress', (event, arg) => {
        if (!this.downloadProcessShow) {
          const h = this.$createElement;

          this.$notify({
            message: h('el-progress', {
              props: {
                percentage: 0,
              },

View on GitHub (pinned to c149855106)

Solutions

Restore connectivity and retry the update check
Allow the update hosts (api.github.com / github.com / your provider) through firewall and proxy
Configure electron-updater proxy settings if the network requires one
If you self-host updates, verify the feed URL serves latest.yml

Defensive patterns

Strategy: retry

Validate before calling

// cheap pre-check before invoking the updater
if (!navigator.onLine) {
  this.$message.info(this.$t('message.offline_retry_later'));
  return;
}

Try / catch

try {
  await autoUpdater.checkForUpdates();
} catch (e) {
  const transient = /err_internet_disconnected|err_name_not_resolved|err_connection_refused|ETIMEDOUT/i.test(String(e));
  if (transient) setTimeout(() => autoUpdater.checkForUpdates().catch(() => {}), 30000);
}

Prevention

Check navigator.onLine before manual update checks
Allow-list update hosts in firewalls and proxies
Ship a proxy configuration for enterprise users
Rate-limit the check button to avoid toast spam

When it happens

Trigger: Manual update check while offline; DNS failure resolving the update host; corporate firewall/proxy blocking api.github.com or the download host; self-hosted update feed server down.

Common situations: Air-gapped or proxied corporate networks, VPN routes blocking GitHub, transient ISP DNS outages, release artifacts not yet propagated on CDN.

Related errors

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