FAQ

The times that the Uptime Kuma backend sends to the frontend carry no time zone information. To make development easier, Kuma Mieru shows all times in UTC+0.

In the Uptime Kuma settings, set Display Timezone to a UTC+0 time zone.

Kuma Mieru was designed to fix the shortcomings of Uptime Kuma. Thus v1 does not plan to support other monitoring data sources. v2 may add support for the APIs of other monitoring tools, such as Uptime Robot and Better Stack.

The generate script stops with an error in these cases. The platform build then fails. In Docker, the start command of the container stops. With the docker-compose.yml of the repository, the container restarts again and again because of restart: unless-stopped.

• Neither UPTIME_KUMA_URLS nor UPTIME_KUMA_BASE_URL with PAGE_ID is set. The log shows UPTIME_KUMA_BASE_URL is required (or set UPTIME_KUMA_URLS) or PAGE_ID is required (or set UPTIME_KUMA_URLS).
• A URL in UPTIME_KUMA_URLS does not contain /status/<page ID>. The error in the log starts with Expected status page URL like.
• Two status pages from different instances use the same page ID. See the next item.

If you start the container with docker run and do not set UPTIME_KUMA_URLS, the container connects to the built-in demo status page of the image. See Docker. For the format of the status page addresses, see Connect Uptime Kuma.

Two status pages from different Uptime Kuma instances in UPTIME_KUMA_URLS use the same page ID. Each page ID must be unique across all instances. Give the status page in one of the instances a different page ID.

The configuration is generated during the build or when the container starts. After you change a variable on Vercel, Netlify or EdgeOne Pages, redeploy. For Docker Compose, run docker compose up -d --force-recreate. For more information, see Environment Variables.

No. All configuration is in the environment variables of the deployment platform, not in the repository. Keep your fork public. A private fork can prevent a quick sync of upstream updates.

The Netlify Next.js adapter @netlify/plugin-nextjs 5.16.4 can show this error while it packages the Node.js Proxy (proxy.ts). Wait until the adapter publishes a fixed version, then redeploy.

In a trusted environment, set ALLOW_INSECURE_TLS=true. The server then skips the HTTPS certificate validation of Uptime Kuma at runtime. This is a security risk.

This variable does not affect the requests of the generate script that read the status page metadata. These requests still validate the certificate, so the title, description and icon come from the environment variables or the defaults. Set the title and the description with KUMA_MIERU_TITLE and KUMA_MIERU_DESCRIPTION, and point KUMA_MIERU_ICON to the icon on Uptime Kuma. For more information, see ALLOW_INSECURE_TLS.

Yes. Embedding is blocked by default. List the allowed origins in ALLOW_EMBEDDING, for example ALLOW_EMBEDDING=example.com. For more information, see ALLOW_EMBEDDING.

The default STRICT_IMAGE_REMOTE_PATTERNS=false allows all remote image domains. With true, the allowlist contains only the domains of the Uptime Kuma base URLs and of KUMA_MIERU_ICON. Images from other domains do not load. For more information, see STRICT_IMAGE_REMOTE_PATTERNS.

Not yet. Use Vercel or Netlify instead. For the Cloudflare configuration in the repository, see Cloudflare Workers.