Hi everyone,
After upgrading to n8n 1.123.0 , I noticed that the /rest/settings endpoint no longer returns detailed instance statistics, including the current n8n version .
Previous behavior (before 1.123.0)
The endpoint returned a comprehensive payload including:
Current behavior (1.123.0+)
These fields appear to have been removed or restricted from the response.
Impact
If you rely on this endpoint to:
Monitor your n8n version programmatically
Build dashboards or health checks
Automate upgrade notifications
…you may need to find an alternative approach.
Questions for the community / team
Is there an alternative endpoint to retrieve the instance version?
Best regards
Environment:
n8n version: 1.123.0
Database (default: SQLite): Postgres
n8n EXECUTIONS_PROCESS setting (default: own, main): queue
Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
Operating system: Ubuntu
Hi @zlebandit
Yes, I’m actually affected by this as well since I rely on it for auto-updating.
I believe this is the PR related to it:
master ← pay-3939-reduce-unauthentication-information-in-settings-endpoint-further
opened 04:07PM - 20 Nov 25 UTC
## Summary
Change the public setting to only contains properties that are abs… olutely needed by the non-authenticated pages
## Related Linear tickets, Github issues, and Community forum posts
resolves PAY-3939
## Review / Merge checklist
- [x] PR title and summary are descriptive. ([conventions](../blob/master/.github/pull_request_title_conventions.md))
- [ ] [Docs updated](https://github.com/n8n-io/n8n-docs) or follow-up ticket created.
- [x] Tests included.
- [ ] PR Labeled with `release/backport` (if the PR is an urgent fix that needs to be backported)
---
> [!NOTE]
> Reduces unauthenticated settings to essentials, updates frontend to skip side effects in public mode, moves user/banners init to authenticated flow, and makes logo release channel optional with safer favicon handling.
>
> - **Backend (CLI)**:
> - **Public settings**: Redefines `PublicFrontendSettings` to a minimal schema and updates `getPublicSettings()` to return only `settingsMode`, `previewMode`, `authCookie.secure`, `userManagement` auth/setup fields, minimal `sso` flags/URLs, and `enterprise` SSO flags.
> - **Frontend**:
> - **Settings store**: On `settingsMode: 'public'`, only `setSettings()` is applied; skips root store/telemetry side effects; removes dedicated `setPublicSettings()`.
> - **App init**: `initializeCore()` no longer initializes users or static banners; `initializeAuthenticatedFeatures()` now initializes `usersStore` (if not preview) and pushes static banners (`NON_PRODUCTION_LICENSE`, `V1`).
> - **Logo**: `releaseChannel` prop is optional; only customizes logo/favicon for non-`stable` channels; guards favicon with `URL.createObjectURL` check.
> - **Tests**:
> - Updated unit tests across CLI and editor UI to match minimal public settings and the new initialization/banners flow; router test ensures `usersStore.initialize()` runs during authenticated feature init.
>
> <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 1a7b332b7bfa540e085f9f79fe76ba1c330e8cf2. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>
For now, I’m considering two possible solutions:
1- Using the /metrics endpoint:
by parsing the relevant info.
2- Using an Execute node:
If you find an easier solution, I’d love to hear it..
system
Closed
March 2, 2026, 11:53am
3
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.