mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #475] [Bug]: FTP download failed - Even with permissions set correctly #297
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy-maziggy-1#297
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wreuel on GitHub (Feb 20, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/475
Originally assigned to: @maziggy on GitHub.
Bug Description
The permissions on /data/* are correct:
drwxr-sr-x 5 [myuser] [mygroup] 4096 Feb 20 21:26 bambubuddy
drwxr-sr-x 4 [myuser] [mygroup] 4096 Feb 20 21:26 bambubuddy/data/archive/
But the file is not correctly downloaded to the folder, showing error 550.
Expected Behavior
It should save correctly
Steps to Reproduce
Send a print from bambu studio, wait to finish and try to open the file or download.
Printer Model
P2S
Bambuddy Version
v0.2.1b
Printer Firmware Version
01.01.03.00
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
bambuddy-support-20260220-213553-REMOVEDSERIAL.zip
Screenshots
No response
Additional Context
No response
Checklist
@maziggy commented on GitHub (Feb 21, 2026):
Debug logs are not attached. Please re-upload.
@wreuel commented on GitHub (Feb 21, 2026):
@maziggy commented on GitHub (Feb 21, 2026):
P2S is processing print files different than older printer models. Should be fixed in branch 0.2.1b2. Please let me know how it goes.
@wreuel commented on GitHub (Feb 21, 2026):
@maziggy just installed the newest and still, I couldn't get the file over.
@maziggy commented on GitHub (Feb 21, 2026):
Without logs i cannot do anything ;)
@maziggy commented on GitHub (Feb 21, 2026):
Also did you pull the latest image re-build the container locally?
@wreuel commented on GitHub (Feb 21, 2026):
@maziggy logs, sorry I didn't sent earlier!
I have pulled from the registry and updated my container correctly.
bambuddy.log
support-info.json
@maziggy commented on GitHub (Feb 21, 2026):
Good news: the "Is a directory" error from before is gone on 0.2.1b2.
However, I can see that your archive (id 3, "ButtonTwo") was created but without a file_path — meaning the 3MF source file wasn't downloaded from the printer's SD card.
The log also shows Failed to delete /ButtonTwo.3mf: 550 Delete operation failed and Failed to delete /ButtonTwo.gcode: 550 Delete operation failed during SD card cleanup.
Could you clarify what exactly is failing for you? Specifically:
Also — debug logging was only enabled at 15:42 and the print was already running by then. If the issue happens at print start (sending the file), could you enable debug logging before starting the print and share the logs again? That way we can capture the full FTP upload/download sequence.
@wreuel commented on GitHub (Feb 21, 2026):
bambuddy.log
Newest log as you asked!
I'm printing from bambu studio. The print is finished good, but doesn't show up on the archive.
@maziggy commented on GitHub (Feb 21, 2026):
Do you know what's funny?
All your tickets are related to "The print is finished good, but doesn't show up on the archive.". So if you would have opened your first ticket for this, it would have resolved all other issues. So you tested it from the end to the beginning :)
Hahaha...never had that before.
Anyway, let me check....that's for sure the FTP session.
@maziggy commented on GitHub (Feb 21, 2026):
Unfortunately the debug logging was enabled after the print had already finished — the log starts with FINISH -> FINISH. The 3MF download from the printer happens when the print starts (RUNNING state detected), not when it finishes.
Could you try this:
This will capture the full FTP download sequence so we can see exactly which paths are tried and why they all fail on your P2S.
@wreuel commented on GitHub (Feb 22, 2026):
Well, I went to check everything here again!
And after a reset on everything it worked! I have Timelapse, Gcode file and Image! :)