Upload to Moonraker returns 403, file still uploads, and printer may auto‑start print #56

Open
opened 2026-04-05 16:18:17 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @twanskys on 3/31/2026

Is there an existing issue for this problem?

  • I have searched the existing issues

OrcaSlicer Version

2.3.1

Operating System (OS)

Windows

OS Version

windows 11

Additional system information

cpu 9900k 32g ram. 4080 super asus
mobo hero 11 wifi

Printer

modified makergear m3-id btt octopus pro

How to reproduce

Steps to Reproduce

  1. Slice any model in Orca Slicer.
  2. Use Upload & Print or have auto‑start enabled.
  3. Orca begins uploading to Moonraker.
  4. Moonraker returns a 403 Forbidden during .
  5. Orca shows an error popup indicating the upload failed.
  6. The file still appears in on the printer.
  7. The printer UI (Mainsail) may automatically start printing the file

Actual results

Actual Behavior
• Upload partially succeeds.
• Operation check fails (403).
• Orca still sends a start‑print request.
• Printer UI may auto‑start the newly uploaded file.
• User sees an error popup but the printer begins printing anyway.

Expected results

Expected Behavior
• If the upload fails, Orca should not send a start‑print command.
• Orca should verify whether the file exists on the host before assuming the upload failed.
• Orca should not leave the printer in a state where a job can auto‑start unexpectedly.
• A failed operation check should not be treated as a failed upload.

Project file & Debug log uploads

HTTP 403: {"error":{"code":403,"message":"Forbidden","traceback":"Traceback (most recent call last):
File "/home/.../moonraker/components/file_manager/file_manager.py", line 903, in _finish_gcode_upload
can_start = self._handle_operation_check(check_path)
...

alpine_knob.zip

Image

Checklist of files to include

  • Log file
  • Project file

Anything else?

No response

*Originally created by @twanskys on 3/31/2026* ### Is there an existing issue for this problem? - [x] I have searched the existing issues ### OrcaSlicer Version 2.3.1 ### Operating System (OS) Windows ### OS Version windows 11 ### Additional system information cpu 9900k 32g ram. 4080 super asus mobo hero 11 wifi ### Printer modified makergear m3-id btt octopus pro ### How to reproduce Steps to Reproduce 1. Slice any model in Orca Slicer. 2. Use Upload & Print or have auto‑start enabled. 3. Orca begins uploading to Moonraker. 4. Moonraker returns a 403 Forbidden during . 5. Orca shows an error popup indicating the upload failed. 6. The file still appears in on the printer. 7. The printer UI (Mainsail) may automatically start printing the file ### Actual results Actual Behavior • Upload partially succeeds. • Operation check fails (403). • Orca still sends a start‑print request. • Printer UI may auto‑start the newly uploaded file. • User sees an error popup but the printer begins printing anyway. ### Expected results Expected Behavior • If the upload fails, Orca should not send a start‑print command. • Orca should verify whether the file exists on the host before assuming the upload failed. • Orca should not leave the printer in a state where a job can auto‑start unexpectedly. • A failed operation check should not be treated as a failed upload. ### Project file & Debug log uploads HTTP 403: {"error":{"code":403,"message":"Forbidden","traceback":"Traceback (most recent call last): File "/home/.../moonraker/components/file_manager/file_manager.py", line 903, in _finish_gcode_upload can_start = self._handle_operation_check(check_path) ... [alpine_knob.zip](https://github.com/user-attachments/files/26367943/alpine_knob.zip) <img width="1612" height="554" alt="Image" src="https://github.com/user-attachments/assets/fe7a7ffe-d798-4e62-9b2f-128251a14463" /> ### Checklist of files to include - [ ] Log file - [ ] Project file ### Anything else? _No response_
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/OrcaSlicer#56