Dokploy/dokploy · error · Error

Error : . Please verify that the application " " is running…

Error message

Error ${response.status}: ${response.statusText}. Please verify that the application "${input.appName}" is running and this service is included in the monitoring configuration.

What it means

Thrown by Dokploy's monitoring query when the fetch to the monitoring service (Dockyard/monitoring endpoint with a Bearer token) returns a non-2xx status. The message embeds the HTTP status/statusText and asks you to verify the app is running and monitored. It indicates the monitoring side rejected the request, not Dokploy itself.

Solutions

Verify the application container is actually running (docker ps / Dokploy UI status)
Confirm the service is included in the monitoring configuration and the agent has had time to scrape it
Check that input.token is a valid, current monitoring token
Inspect the embedded HTTP status: 401/403 → token issue, 404 → service not in monitoring config, 5xx → monitoring backend issue

Defensive patterns

Strategy: try-catch

Validate before calling

// Pre-check container state via Dokploy API if available before fetching metrics

Try / catch

try { const pts = await query(...); } catch (e) { if (/^Error \d+/.test(e.message)) { const status = Number(e.message.match(/\d+/)[0]); handleByStatus(status); } else throw e; }

Prevention

Confirm container is running before opening monitoring
Keep monitoring token fresh; rotate via the app settings
Parse the embedded HTTP status to branch remediation

When it happens

Trigger: Calling the monitoring data-points query for an appName whose container is stopped, not scraped by the monitoring stack, or when the Bearer token is invalid/expired causing 401/403 from the monitoring service.

Common situations: App container just redeployed or stopped; monitoring agent (Prometheus/Dockyard) not covering the service; wrong or expired token passed in input.token; monitoring service URL misconfigured or unreachable behind a proxy that returns 502.

Related errors

AI-assisted analysis of Dokploy/dokploy@546686ea35 (2026-08-27). Data as JSON: /api/errors/590c9cc60715019b. Report an issue: GitHub.

Appendix: source

Thrown at apps/dokploy/server/api/routers/user.ts:554

				if (!input.appName) {
					throw new Error(
						[
							"No Application Selected:",
							"",
							"Make Sure to select an application to monitor.",
						].join("\n"),
					);
				}
				const url = new URL(`${input.url}/metrics/containers`);
				url.searchParams.append("limit", input.dataPoints);
				url.searchParams.append("appName", input.appName);
				const response = await fetch(url.toString(), {
					headers: {
						Authorization: `Bearer ${input.token}`,
					},
				});
				if (!response.ok) {
					throw new Error(
						`Error ${response.status}: ${response.statusText}. Please verify that the application "${input.appName}" is running and this service is included in the monitoring configuration.`,
					);
				}

				const data = await response.json();
				if (!Array.isArray(data) || data.length === 0) {
					throw new Error(
						[
							`No monitoring data available for "${input.appName}". This could be because:`,
							"",
							"1. The container was recently started - wait a few minutes for data to be collected",
							"2. The container is not running - verify its status",
							"3. The service is not included in your monitoring configuration",
						].join("\n"),
					);
				}
				return data as {
					containerId: string;

View on GitHub (pinned to 546686ea35)