Skip to content

docs: Add a troubleshooting entry for the 'forbidden' (HTTP 403) error in#22657

Draft
nedi-app[bot] wants to merge 1 commit into
masterfrom
docs/netdata-configuration-manager-forbidden-nodes-access
Draft

docs: Add a troubleshooting entry for the 'forbidden' (HTTP 403) error in#22657
nedi-app[bot] wants to merge 1 commit into
masterfrom
docs/netdata-configuration-manager-forbidden-nodes-access

Conversation

@nedi-app
Copy link
Copy Markdown
Contributor

@nedi-app nedi-app Bot commented Jun 8, 2026

Summary

Add a troubleshooting entry for the 'forbidden' (HTTP 403) error in. Files changed: docs/netdata-agent/configuration/dynamic-configuration.md, .nedi-audit/.

User Request

when creating a configuration iam not able to see the nodes it says -forbidden

Prompt (English)

Why the Configuration Manager shows 'forbidden' for nodes

Reason for Change

This change applies the specific user request using repository-truth evidence from the audit execution workspace.


Summary by cubic

Added a troubleshooting entry for "forbidden" (HTTP 403) in the Dynamic Configuration Manager docs, addressing cases where users can’t see nodes or create configurations. It explains role and plan limits (Admin/Manager only, paid plans), Room membership requirements, and provides steps to fix with a link to the RBAC permissions table.

Written for commit f3fb525. Summary will update on new commits.

Review in cubic

@nedi-app nedi-app Bot added the nedi-audit PRs created by the nedi-audit pipeline label Jun 8, 2026
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Jun 8, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/docs nedi-audit PRs created by the nedi-audit pipeline

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants