Mintplex-Labs/anything-llm · error · Error

response.error || "Failed to update settings"

Error message

response.error || "Failed to update settings"

What it means

Frontend guard in CommunityHub.updateSettings: the settings update POST returned a non-ok status, so the hub settings (e.g. API key) were not persisted; the server-supplied error is surfaced, falling back to 'Failed to update settings' when the body lacks detail.

Solutions

1. Verify the settings payload matches the expected schema.
2. Check the Community Hub connection key.
3. Review server logs for the failure.

When it happens

Trigger: Thrown when updating Community Hub settings fails.

Common situations: Invalid settings values or hub connection issue.

AI-assisted analysis of Mintplex-Labs/anything-llm@3aec848f28 (2026-08-18). Data as JSON: /api/errors/e277c4c859262752. Report an issue: GitHub.

Appendix: source

Thrown at frontend/src/models/communityHub.js:86

        };
      });
  },

  /**
   * Update the hub settings (API key, etc.)
   * @param {Object} data - The data to update.
   * @returns {Promise<{success: boolean, error: string | null}>}
   */
  updateSettings: async (data) => {
    return await fetch(`${API_BASE}/community-hub/settings`, {
      method: "POST",
      headers: baseHeaders(),
      body: JSON.stringify(data),
    })
      .then(async (res) => {
        const response = await res.json();
        if (!res.ok)
          throw new Error(response.error || "Failed to update settings");
        return { success: true, error: null };
      })
      .catch((e) => ({
        success: false,
        error: e.message,
      }));
  },

  /**
   * Get the hub settings (API key, etc.)
   * @returns {Promise<{connectionKey: string | null, error: string | null}>}
   */
  getSettings: async () => {
    return await fetch(`${API_BASE}/community-hub/settings`, {
      method: "GET",
      headers: baseHeaders(),
    })
      .then(async (res) => {

View on GitHub (pinned to 3aec848f28)