Dokploy/dokploy · critical · TRPCError

INTERNAL_SERVER_ERROR

INTERNAL_SERVER_ERROR

Error message

Error on deploy mongo${error}

What it means

Thrown by deployMongo when the deployment pipeline throws: it streams the error via onData, marks the mongo applicationStatus as 'error', then rethrows INTERNAL_SERVER_ERROR with the raw cause appended to the message.

Source

Thrown at packages/server/src/services/mongo.ts:182

				`docker pull ${quote([mongo.dockerImage])}`,
				onData,
			);
		} else {
			await pullImage(mongo.dockerImage, onData);
		}

		await buildMongo(mongo);
		await updateMongoById(mongoId, {
			applicationStatus: "done",
		});
		onData?.("Deployment completed successfully!");
	} catch (error) {
		onData?.(`Error: ${error}`);
		await updateMongoById(mongoId, {
			applicationStatus: "error",
		});

		throw new TRPCError({
			code: "INTERNAL_SERVER_ERROR",
			message: `Error on deploy mongo${error}`,
		});
	}
	return mongo;
};

View on GitHub (pinned to 546686ea35)

Solutions

  1. Read the appended error text and streamed deployment logs
  2. Check Docker daemon health, disk, and memory on the destination server
  3. Verify image pull access and tag validity
  4. Fix the root cause and redeploy to clear the 'error' status

Example fix

// before
await deployMongo(mongoId);

// after
await deployMongo(mongoId, (chunk) => console.log(chunk)); // stream logs to find the failing step
Defensive patterns

Strategy: try-catch

Validate before calling

const m = await findMongoById(mongoId);
if (m.applicationStatus === 'error') throw new Error('Resolve prior error before redeploy');

Try / catch

try { await deployMongo(mongoId, onLog); } catch (e) { notify(String(e.message)); await updateMongoById(mongoId, { applicationStatus: 'error' }); }

Prevention

When it happens

Trigger: Calling deployMongo when remote deployment fails — Docker unreachable on the destination server, mongo image pull failure, bad server config, or deploy script crash.

Common situations: Destination host offline, no registry egress, disk/memory exhaustion, or an invalid/unavailable MongoDB image tag.

Related errors

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