[GH-ISSUE #1112] [Bug]: Where are External Folder files stored?

BreizhHardware commented

2026-05-07 00:13:51 +02:00

Owner

Originally created by @Carter3DP on GitHub (Apr 24, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1112

Originally assigned to: @maziggy on GitHub.

Component

Bambuddy

Bug Description

Where are files stored when using an external folder in file manager? For example say you have an external folder that links to a NAS, and you upload a file through the file manager in Bambuddy. You won't be able to see that file if you access that NAS through another computer.

Expected Behavior

Files uploaded through the file manager to an external folder should show up in that external folder if you bring it up on another computer.

Steps to Reproduce

Create an external folder that links to a SMB server.
Through Bambuddy, upload a .gcode.3mf file to the external folder.
Access the external folder outside of Bambuddy, the file will not be there.

Printer Model

None

Bambuddy Version

0.2.3.2

SpoolBuddy Version

No response

Printer Firmware Version

No response

Installation Method

Docker

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

bambuddy-support-20260424-094242.zip

Screenshots

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 @Carter3DP on GitHub (Apr 24, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1112 Originally assigned to: @maziggy on GitHub. ### Component Bambuddy ### Bug Description Where are files stored when using an external folder in file manager? For example say you have an external folder that links to a NAS, and you upload a file through the file manager in Bambuddy. You won't be able to see that file if you access that NAS through another computer. ### Expected Behavior Files uploaded through the file manager to an external folder should show up in that external folder if you bring it up on another computer. ### Steps to Reproduce 1. Create an external folder that links to a SMB server. 2. Through Bambuddy, upload a .gcode.3mf file to the external folder. 3. Access the external folder outside of Bambuddy, the file will not be there. ### Printer Model None ### Bambuddy Version 0.2.3.2 ### SpoolBuddy Version _No response_ ### Printer Firmware Version _No response_ ### Installation Method Docker ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package [bambuddy-support-20260424-094242.zip](https://github.com/user-attachments/files/27054232/bambuddy-support-20260424-094242.zip) ### Screenshots <img width="1920" height="1004" alt="Image" src="https://github.com/user-attachments/assets/f787328a-b17c-47ba-9323-596e790b0f5d" /> <img width="1920" height="1031" alt="Image" src="https://github.com/user-attachments/assets/68783b65-7a79-4924-abb5-a3f0a54a9670" /> ### 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:13:51 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-07 00:13:52 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 24, 2026):

Yup, found a small issue.

Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you now.

If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!

@maziggy commented on GitHub (Apr 24, 2026): Yup, found a small issue. Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you now. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!

BreizhHardware commented

2026-05-07 00:13:52 +02:00

Author

Owner

@Carter3DP commented on GitHub (Apr 27, 2026):

It does not appear to working still, now files no longer appear if uploaded to an external folder. You can still upload a file to a folder that exists on Bambuddy and then move it to the external folder, and it will appear on Bambuddy but not physically on the external folder.

This is on version 0.2.4b1

bambuddy-support-20260427-095013.zip

@Carter3DP commented on GitHub (Apr 27, 2026): It does not appear to working still, now files no longer appear if uploaded to an external folder. You can still upload a file to a folder that exists on Bambuddy and then move it to the external folder, and it will appear on Bambuddy but not physically on the external folder. This is on version 0.2.4b1 [bambuddy-support-20260427-095013.zip](https://github.com/user-attachments/files/27128129/bambuddy-support-20260427-095013.zip)

BreizhHardware commented

2026-05-07 00:13:52 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 27, 2026):

The 0.2.4b1 change covered direct upload to a writable external folder but missed the move path. move_files was only flipping folder_id in the database; the bytes never left library_files_dir/, so Bambuddy and the NAS disagreed about what was actually there. Same root cause for "files don't appear if uploaded to an external folder" too in some cases — explained below.

What's fixed:

Move from a managed folder to an external folder now writes the bytes to the mount and removes the internal copy. The DB row, the file on the NAS, and what you see in the File Manager all agree.
The reverse (external → managed) also works: the file is copied into Bambuddy's internal storage and removed from the mount.
Same-folder-class moves (managed → managed) are unchanged.
A few safety guards: source on a read-only external mount is skipped (move = delete on source, which RO can't do), filename collisions on the target NAS are skipped instead of overwriting your existing file, and target write-permission is checked before the copy starts.
Skipped files now come back with structured reasons (name_collision, source_readonly, target_unwritable, etc.) so the UI can tell you why something didn't move instead of just showing a number.

For the original "files don't appear if uploaded to an external folder" symptom: looking at your support package, those direct uploads were returning HTTP 400 — most likely the Docker container can't write to the SMB mount with its current UID. The error message itself is explicit ("External path is not writable: …") but it's possible the toast disappeared before you noticed it. Check the user/group ownership on the host side of the volume mount — the container needs write access. If it persistently fails, post the response body from the failing upload and I'll dig further.

Available/Fixed in branch dev and available with the next release or daily build.

If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!

@maziggy commented on GitHub (Apr 27, 2026): The 0.2.4b1 change covered direct upload to a writable external folder but missed the move path. move_files was only flipping folder_id in the database; the bytes never left library_files_dir/, so Bambuddy and the NAS disagreed about what was actually there. Same root cause for "files don't appear if uploaded to an external folder" too in some cases — explained below. What's fixed: - Move from a managed folder to an external folder now writes the bytes to the mount and removes the internal copy. The DB row, the file on the NAS, and what you see in the File Manager all agree. - The reverse (external → managed) also works: the file is copied into Bambuddy's internal storage and removed from the mount. - Same-folder-class moves (managed → managed) are unchanged. - A few safety guards: source on a read-only external mount is skipped (move = delete on source, which RO can't do), filename collisions on the target NAS are skipped instead of overwriting your existing file, and target write-permission is checked before the copy starts. - Skipped files now come back with structured reasons (name_collision, source_readonly, target_unwritable, etc.) so the UI can tell you why something didn't move instead of just showing a number. For the original "files don't appear if uploaded to an external folder" symptom: looking at your support package, those direct uploads were returning HTTP 400 — most likely the Docker container can't write to the SMB mount with its current UID. The error message itself is explicit ("External path is not writable: …") but it's possible the toast disappeared before you noticed it. Check the user/group ownership on the host side of the volume mount — the container needs write access. If it persistently fails, post the response body from the failing upload and I'll dig further. Available/Fixed in branch dev and available with the next release or daily build. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!

BreizhHardware commented

2026-05-07 00:13:52 +02:00

Author

Owner

@Carter3DP commented on GitHub (Apr 27, 2026):

For the original "files don't appear if uploaded to an external folder" symptom: looking at your support package, those direct uploads were returning HTTP 400 — most likely the Docker container can't write to the SMB mount with its current UID. The error message itself is explicit ("External path is not writable: …") but it's possible the toast disappeared before you noticed it. Check the user/group ownership on the host side of the volume mount — the container needs write access.

Welp, that part would absolutely be my fault, just changed how the server is mounted and now when uploading files through the interface the files show up for other computers. Sorry for that.
I will give an update as to whether moving files work once I update to the next available daily build.
Thank you.

@Carter3DP commented on GitHub (Apr 27, 2026): > For the original "files don't appear if uploaded to an external folder" symptom: looking at your support package, those direct uploads were returning HTTP 400 — most likely the Docker container can't write to the SMB mount with its current UID. The error message itself is explicit ("External path is not writable: …") but it's possible the toast disappeared before you noticed it. Check the user/group ownership on the host side of the volume mount — the container needs write access. Welp, that part would absolutely be my fault, just changed how the server is mounted and now when uploading files through the interface the files show up for other computers. Sorry for that. I will give an update as to whether moving files work once I update to the next available daily build. Thank you.

BreizhHardware commented

2026-05-07 00:13:52 +02:00

Author

Owner

@Carter3DP commented on GitHub (Apr 27, 2026):

Confirmed moving files works now. One last thing, I am uncertain if I should make a new issue for this and I am uncertain if this is even a bug at all or if it is intended, but if you upload a .gcode.3mf file externally, NOT through the Bambuddy interface, the file displays as a gcode.3mf and information such as print time and the thumbnail does not display. This isn't exactly breaking anything for me as I can upload through the interface perfectly fine now, but thought I should bring it up if it wasn't intended.

@Carter3DP commented on GitHub (Apr 27, 2026): Confirmed moving files works now. One last thing, I am uncertain if I should make a new issue for this and I am uncertain if this is even a bug at all or if it is intended, but if you upload a .gcode.3mf file externally, NOT through the Bambuddy interface, the file displays as a gcode.3mf and information such as print time and the thumbnail does not display. This isn't exactly breaking anything for me as I can upload through the interface perfectly fine now, but thought I should bring it up if it wasn't intended. <img width="1552" height="628" alt="Image" src="https://github.com/user-attachments/assets/33e700e4-eab3-40ad-9475-01eb62eb270f" /> <img width="1599" height="880" alt="Image" src="https://github.com/user-attachments/assets/5d1ffc6e-9b3d-43fa-a981-2dc490b2ff3a" />

BreizhHardware commented

2026-05-07 00:13:52 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 28, 2026):

Yes, that's correct. If you copy the files directly to the share, they are not being parsed by Bambuddy. Expected behaviour.

@maziggy commented on GitHub (Apr 28, 2026): Yes, that's correct. If you copy the files directly to the share, they are not being parsed by Bambuddy. Expected behaviour.

BreizhHardware referenced this issue

2026-05-07 00:16:21 +02:00

[PR #1029] [MERGED] v0.2.3 final #1155

Rows
Columns

[GH-ISSUE #1112] [Bug]: Where are External Folder files stored? #794

Component

Bug Description

Expected Behavior

Steps to Reproduce

Printer Model

Bambuddy Version

SpoolBuddy Version

Printer Firmware Version

Installation Method

Operating System

Relevant Logs / Support Package

Screenshots

Additional Context

Checklist