-
-
Notifications
You must be signed in to change notification settings - Fork 1
Troubleshooting
This page collects common issues and first checks.
Check Node version:
node --versionCindr3D expects Node.js 22.12.0 or newer.
Refresh dependencies:
npm installIf Vite cache state appears stale:
npm run dev:freshRun the checks separately to narrow down the failure:
npm run typecheck
npm run lint
npm run test:run
npm run buildIf the failure mentions WASM artifacts, also run:
npm run verify:wasm-build
npm run check:wasm-budgetCindr3D is a single-page app. Static hosts must fall back unknown routes to index.html.
For Nginx, the important rule is:
try_files $uri $uri/ /index.html;Confirm the deployed directory includes:
index.html
assets/
If deploying a zip asset for the updater, the archive can also contain:
dist/index.html
dist/assets/
Check these first:
- The Cindr3D browser tab is open.
- The dev server is running.
- The MCP URL includes the current token from the AI MCP status badge.
- The client is connecting from localhost.
- The MCP port has not been changed by
CINDR3D_MCP_PORT.
Default URLs:
http://localhost:5173
http://localhost:5174/mcp?token=...
If the token might be stale, rotate it from the AI status badge and re-add the MCP server in the client.
Cindr3D adapts tabs and commands to the connected printer and detected firmware.
Check:
- Printer profile firmware type
- Connection status
- Firmware version
- Whether the feature is firmware-supported
- Whether the required plugin or service is enabled on the printer side
Examples:
- Klipper object cancellation depends on
EXCLUDE_OBJECT. - RRF object cancellation depends on
M486support. - Marlin object cancellation depends on a recent enough firmware and labeled G-code.
Object cancellation requires labeled G-code.
For Cindr3D-sliced jobs, labels are emitted automatically.
For other slicers:
- Enable object labels in PrusaSlicer, SuperSlicer, or OrcaSlicer.
- Use Cura's Label Objects post-processing script.
Check:
- Broker URL and credentials
- Topic names
- Network access from the browser or bridge
- Event rules enabled in Cindr3D
- Home Assistant discovery settings
- Whether the printer is actively publishing state
Start with a single event such as PRINT_START or DONE, confirm delivery, then expand automation coverage.
Check:
- The updater service is installed and running.
- Nginx routes
/api/update/statusand/api/update/applycorrectly. - The updater token matches the local browser configuration.
- The latest GitHub release includes a compatible
cindr3d-dist.zipasset. - The archive layout includes either root-level
index.htmlandassets/, or adist/directory containing them.
- Home
- Getting Started
- Operator Runbooks
- Guided Tutorials
- Feature Overview
- AI Assistant and MCP
- Self Hosting and Updates
- CAD and Modeling
- Design Box Walkthrough
- Sketching and Dimensions
- CAD Features and Timeline
- Drawing and Export Workflows
- Mesh Repair and Imports
- Slicing and Print Preview
- Slicer Settings Reference
- Prepare Object Walkthrough
- Prepare Profiles and Printer Creation
- G-code Preview Simulation and Breakpoints
- Calibration Workflows
- Printer Workflows
- Printer Connection Setup
- USB Connection (Web Serial)
- Camera Setup
- Printer Interface Gallery
- Print Farm Intelligence
- Filament Profiles
- Mid-print Object Cancellation
- Print Tuning and Utilities
- Safety Limits
- Dashboard Layout Editing