[GH-ISSUE #808] [Bug]: Upload of the source .3mf file fails on 0.2.2.1 #540

New issue

Closed

opened 2026-05-07 00:11:24 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-07 00:11:24 +02:00

Owner

Originally created by @janmalec on GitHub (Mar 25, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/808

Originally assigned to: @maziggy on GitHub.

Bug Description

My latest archive entry after upgrade did not process. I noticed that the .3mf file is missing from the archive entry so I tried uploading it myself by clicking on the 3 dots in the upper left corner of the broken archive entry, selecting "Upload Source 3MF" and uploading the file. This failed too with error 500 so I inspected the log which revealed a permissions issue which I fixed but immediately stumbled on another issue. The initial debugging is documented here: https://github.com/maziggy/bambuddy/issues/754#issuecomment-4124212184.

I'm opening a new issue after Issue #754 was closed because users didn't immediately provide the "support" package, which I am attaching to this new issue.

Expected Behavior

I expected the source 3mf file to be added to the archive entry.

Steps to Reproduce

Click on the 3 dots on the top left corner on the archive entry, click "Upload Source 3MF" as indicated on the screenshot, be greeted by a 500 error.

Printer Model

A1 Mini

Bambuddy Version

v0.2.2.1

Printer Firmware Version

01.07.02.00

Installation Method

Docker

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

bambuddy-support-20260325-092241.zip

Screenshots

No response

Additional Context

No response

Checklist

I have searched existing issues to ensure this bug hasn't already been reported
I am using the latest version of Bambuddy
My printer is set to LAN Only mode
My printer has Developer Mode enabled

Originally created by @janmalec on GitHub (Mar 25, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/808 Originally assigned to: @maziggy on GitHub. ### Bug Description My latest archive entry after upgrade did not process. I noticed that the .3mf file is missing from the archive entry so I tried uploading it myself by clicking on the 3 dots in the upper left corner of the broken archive entry, selecting "Upload Source 3MF" and uploading the file. This failed too with error 500 so I inspected the log which revealed a permissions issue which I fixed but immediately stumbled on another issue. The initial debugging is documented here: https://github.com/maziggy/bambuddy/issues/754#issuecomment-4124212184. I'm opening a new issue after Issue #754 was closed because users didn't immediately provide the "support" package, which I am attaching to this new issue. ### Expected Behavior I expected the source 3mf file to be added to the archive entry. ### Steps to Reproduce <img width="338" height="771" alt="Image" src="https://github.com/user-attachments/assets/bb05d5e2-a2b3-4814-aa00-c90525a7fcea" /> Click on the 3 dots on the top left corner on the archive entry, click "Upload Source 3MF" as indicated on the screenshot, be greeted by a 500 error. ### Printer Model A1 Mini ### Bambuddy Version v0.2.2.1 ### Printer Firmware Version 01.07.02.00 ### Installation Method Docker ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package [bambuddy-support-20260325-092241.zip](https://github.com/user-attachments/files/26239163/bambuddy-support-20260325-092241.zip) ### Screenshots _No response_ ### Additional Context _No response_ ### Checklist - [x] I have searched existing issues to ensure this bug hasn't already been reported - [x] I am using the latest version of Bambuddy - [x] My printer is set to LAN Only mode - [x] My printer has Developer Mode enabled

BreizhHardware

2026-05-07 00:11:24 +02:00

closed this issue
added the
invalid
label

BreizhHardware commented

2026-05-07 00:11:25 +02:00

Author

Owner

@maziggy commented on GitHub (Mar 25, 2026):

Source file doesn't mean Gcode file.

Source file -> saved from slicer without slicing
Gcode file -> sliced file saved from slicer

@maziggy commented on GitHub (Mar 25, 2026): Source file doesn't mean Gcode file. Source file -> saved from slicer without slicing Gcode file -> sliced file saved from slicer