uptimekuma api error

[aryanrajseo]

Description

Have the status configured http://10.0.0.105:3001/status/overview

fix given, i was using url: http://10.0.0.105:3001/status/overview which was causing this. the below code is working.

- uptime:
    icon: uptime-kuma.png
    href: http://10.0.0.105:3001/status/overview
    widget:
      type: uptimekuma
      url: http://10.0.0.105:3001
      slug: overview

API Error: Invalid data
URL: 10.0.0.105 (see logs for details)
Response Data:
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0, viewport-fit=cover" />
    <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
    <link rel="icon" type="image/svg+xml" href="/icon.svg" />
    <link rel="manifest" href="/manifest.json" />
    <meta name="theme-color" id="theme-color" content="" />
    <meta name="description" content="Uptime Kuma monitoring tool" />
    <title>Uptime Kuma</title>
    <style>        .noscript-message {
            font-size: 20px;
            text-align: center;
            padding: 10px;
            max-width: 500px;
            margin: 0 auto;
        }
    </style>
  <script type="module" crossorigin src="/assets/index-DemVIFWP.js"></script>
  <link rel="stylesheet" crossorigin href="/assets/index-3GNdRraX.css">
</head>
<body>
<noscript>
<div class="noscript-message">
    Sorry, you don't seem to have JavaScript enabled or your browser
    doesn't support it.<br />This website requires JavaScript to function.
    Please enable JavaScript in your browser settings to continue.
</div>
</noscript>
<div id="app"></div>
</body>
</html>

homepage version

v2.7.0 (2e5f101, Oct 23, 2026)

Installation method

Docker

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

not there for uptimekuma

[github-actions[bot]]

Dear homepage user, thanks for opening this discussion! Please ensure you add the output from the troubleshooting guide steps, the support template asks for those details because they usually make it possible to understand the problem without guessing. Please update the discussion with the relevant troubleshooting output, configuration, logs, and browser console details where applicable: https://gethomepage.dev/troubleshooting/. Thank you!

[Ultroncn]

The response you pasted is Uptime Kuma's HTML application shell, while the widget expects JSON. The <noscript> message is part of that HTML; enabling JavaScript won't make it a valid widget API response.

Your shown widget.url + slug shape matches Homepage 2.7.0. In that version the widget requests both of these paths:

http://KUMA_HOST:3001/api/status-page/overview
http://KUMA_HOST:3001/api/status-page/heartbeat/overview

Replace KUMA_HOST with the address in your config. Test both from the same container/network as Homepage, for example with an available HTTP client:

curl -i http://KUMA_HOST:3001/api/status-page/overview
curl -i http://KUMA_HOST:3001/api/status-page/heartbeat/overview

Inspect the status, any Location redirect, content type and response body. The heartbeat response should contain heartbeatList and uptimeList; loading the browser page at /status/overview successfully does not check either API request. The card's href is only the link you open, not the API base URL.

If either API path returns this HTML, check which upstream/path it actually reaches, including any proxy rewrite or redirect. If both return JSON from inside Homepage's network, compare that with the exact failed URL in Homepage's logs and the config actually loaded by the running container. That separates an upstream route problem from a stale/wrong widget configuration without guessing which one you have.

The exact route template and two endpoints are in the v2.7.0 widget source. I checked that tagged source and the fields used by the component; I cannot access your Kuma instance, so this identifies what to test rather than confirming a cause in your deployment.

[aryanrajseo]

hi, i fixed it already, i was using same link in url which was causing this. i had it updated the same. the above one is working perfectly.