Summary
User cj (Discord exuberant_moose_10593) cannot print over the network on Cosmos: OrcaSlicer's Upload and Print appears to succeed, Mainsail switches to the printer tab, but the file never appears in jobs and the Mainsail console shows error: Unable to open file. Manually saving gcode and uploading through Mainsail works fine. The same workflow works on OC patched firmware, so this appears Cosmos-specific.
Discord support thread: https://discord.com/channels/1367538416539013122/1530412347250966559 ("steps to revert to stock" — discussion starts in #general 2026-07-24)
Environment
- Printer: Elegoo Centauri Carbon (CC1)
- Firmware: Cosmos (OC patched works fine)
- Slicer: OrcaSlicer — host type
octo/klipper, printer agent orca, hostname = printer IP
- Printer was unused for a few weeks before the failure appeared; settings unchanged
Observed behavior
- Slice in Orca, click Upload and Print.
- Upload window shows, Mainsail switches to printer tab.
- File never shows in print jobs.
- Mainsail console:
error: Unable to open file.
- Manual gcode upload via Mainsail prints normally.
Diagnostic findings so far (from Discord, with @suchmememanyskill)
ls /user-resource/.tmp → only x/y calibration CSVs; no staged uploads.
[virtual_sdcard] path: /etc/klipper/gcodes
- Orca upload destination reported by user:
/etc/klipper/gcodes
- Uploads claim to land in the same directory klipper reads, yet klipper cannot open the file — suggesting a path/mount mismatch (e.g.
/etc/klipper/gcodes on read-only or overlay rootfs) vs the expected /user-resource/gcodes flow.
Still needed from reporter
moonraker.log captured immediately after a failed upload (requested, not yet provided)
ls -la /etc/klipper/gcodes after an upload attempt
- Screenshot of the Orca upload dialog (requested, not yet provided)
User's other outstanding questions
- Step-by-step revert-to-stock guide for both OC patched and Cosmos (pointed at docs-site uninstall instructions)
- How to reset moonraker/klipper state via SSH
- Why the same slicer config works on patched but not Cosmos (different stacks — SDCP/Elegoo Link vs moonraker)
Summary
User
cj(Discordexuberant_moose_10593) cannot print over the network on Cosmos: OrcaSlicer's Upload and Print appears to succeed, Mainsail switches to the printer tab, but the file never appears in jobs and the Mainsail console showserror: Unable to open file. Manually saving gcode and uploading through Mainsail works fine. The same workflow works on OC patched firmware, so this appears Cosmos-specific.Discord support thread: https://discord.com/channels/1367538416539013122/1530412347250966559 ("steps to revert to stock" — discussion starts in #general 2026-07-24)
Environment
octo/klipper, printer agentorca, hostname = printer IPObserved behavior
error: Unable to open file.Diagnostic findings so far (from Discord, with @suchmememanyskill)
ls /user-resource/.tmp→ only x/y calibration CSVs; no staged uploads.[virtual_sdcard]path:/etc/klipper/gcodes/etc/klipper/gcodes/etc/klipper/gcodeson read-only or overlay rootfs) vs the expected/user-resource/gcodesflow.Still needed from reporter
moonraker.logcaptured immediately after a failed upload (requested, not yet provided)ls -la /etc/klipper/gcodesafter an upload attemptUser's other outstanding questions