A modern and easy to use dashboard. 80+ integrations. 20K+ icons built in. Authentication out of the box. No YAML, drag and drop configuration.
docs: clarify request limits, Kuma API checks, and JSX icons (#7205)
Thomasdc1020d82276
diff --git a/apps/docs/docs/integrations/uptime-kuma/index.mdx b/apps/docs/docs/integrations/uptime-kuma/index.mdxindex cd38551b3..cea0dbe87 100644--- a/apps/docs/docs/integrations/uptime-kuma/index.mdx+++ b/apps/docs/docs/integrations/uptime-kuma/index.mdx@@ -23,6 +23,40 @@ Uptime Kuma monitors the availability of your services and provides uptime stati<AddingIntegration />+### Status page URL and monitors++Use the Uptime Kuma instance root as the integration URL, and enter only the status page slug in the slug field.+For a status page at `https://kuma.example.com/status/services`, use:++| Field | Value |+| --------------- | -------------------------- |+| Integration URL | `https://kuma.example.com` |+| Slug | `services` |++Homarr reads `/api/status-page/services` and `/api/status-page/heartbeat/services` from that instance. Both must return+JSON reachable from the Homarr server without an interactive sign-in. Do not use `/status/services` or an API endpoint+as the integration URL. Preserve any reverse-proxy base path in the instance URL.++Only monitors in the selected status page's public groups are included. If a monitor is missing, check that it belongs+to that status page. A successful connection does not mean every monitor in Uptime Kuma is included.++### Troubleshoot authorization errors++Test both JSON endpoints from inside the Homarr container or pod. A `200` response from `/status/services` only checks+the HTML page; it does not confirm that the API paths are accessible:++```sh+wget -S -O - 'https://kuma.example.com/api/status-page/services'+wget -S -O - 'https://kuma.example.com/api/status-page/heartbeat/services'+```++An `authorization` connection error means an HTTP `401` or `403` response. It does not identify whether Uptime Kuma,+a reverse proxy, or an access-control service returned it. Check the response and the relevant proxy logs before+changing the slug or credentials. An HTML login page or challenge is not a valid JSON API response.++Certificate errors are a separate failure type. Add a trusted certificate only when the connection reports a certificate+validation error; an HTTP authorization error alone is not a reason to add one. See [Certificates](/docs/management/certificates).+### Secrets<IntegrationSecretsdiff --git a/apps/docs/docs/management/custom-widgets/custom-jsx.mdx b/apps/docs/docs/management/custom-widgets/custom-jsx.mdxindex 7e3424858..4b160a837 100644--- a/apps/docs/docs/management/custom-widgets/custom-jsx.mdx+++ b/apps/docs/docs/management/custom-widgets/custom-jsx.mdx@@ -71,6 +71,15 @@ than one variable quantifier are rejected.queries can refetch. Set `requestId` inside a successful manual `SubFetch` result to rerun only that named query with thesame parameters. A targeted rerun respects an explicit request `cacheSeconds`; an untargeted button also clears thewidget's server cache. It is disabled when there is no active item/preview or while the board is in edit mode.-- `Icon`/`TablerIcon` resolves installed safe icons.+- `Icon`/`TablerIcon` uses icon names from Homarr's installed Tabler package. Use kebab-case names such as+ `brand-github`, not React component names such as `IconBrandGithub`. Filled icons use the `-filled` suffix, such as+ `star-filled`. Since **v2.6.0**, the full installed icon set is available; earlier v2 releases expose a smaller subset.++```jsx+<Group>+ <Icon name="brand-github" size={24} />+ <TablerIcon name="star-filled" size={24} />+</Group>+```Always include responsive loading, empty, error, and success states. Runtime failures remain inside the widget tile.diff --git a/apps/docs/docs/management/custom-widgets/requests-and-security.mdx b/apps/docs/docs/management/custom-widgets/requests-and-security.mdxindex ce71e1a25..59f6c45e7 100644--- a/apps/docs/docs/management/custom-widgets/requests-and-security.mdx+++ b/apps/docs/docs/management/custom-widgets/requests-and-security.mdx@@ -68,6 +68,24 @@ also use structured `json` and `multiSelect` option values, for example `{ "enti## Protection+### Request count and concurrency++A definition can contain up to **64 named requests**, including load queries, manual queries, and actions. This is+separate from the runtime limit of **four active requests per viewer/item** and **eight per definition**. For example,+eight load queries fit in one definition; they do not need to run at the same time.+For a single placed widget, the four-request viewer/item limit applies before the eight-request definition limit.+Multiple placements of the same definition still share its definition limit.++Since Homarr **v2.5.0**, load queries wait up to 60 seconds for concurrency capacity. Manual requests fail immediately+when capacity is unavailable. The per-minute limits still apply; waiting for capacity does not bypass them.+Callers without an attributable identity share a four-active-request and 60-query-per-minute budget across items and+definitions.++If a widget works in preview but fails on a board, check the running Homarr version and the failed request's diagnostics.+Check the viewer's integration access as well as request limits; preview success does not establish board access.++### Network and permission limits+Every request uses Homarr's existing server executor: same-origin source enforcement, network scope, DNS and redirect validation, SSRF protection, board permissions, rate and request limits, body and response limits, timeouts, and encrypted credential injection. Static headers cannot override credentials, cookies, routing, proxy, forwarding, or hop-by-hop headers.The executor caps request bodies at 10 KiB and response bodies at 1 MiB. Parsed JSON is limited to depth 32 and 50,000 nodes;