starred/bambuddy-maziggy-1

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 08:25:54 +02:00

[GH-ISSUE #83] [Bug]: Backup Data #37

New issue

Closed

opened 2026-05-07 00:05:33 +02:00 by BreizhHardware · 4 comments

BreizhHardware commented

2026-05-07 00:05:33 +02:00

Owner

Originally created by @MisterBeardy on GitHub (Jan 12, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/83

Originally assigned to: @maziggy on GitHub.

Bug Description

I was making a backup to move to my local machine and when selecting all, the backup was invalid. It appears that when you try to run a backup and include the Projects section the file that downloads is an invalid JSON with just the text "Internal Server Error" inside.

bambuddy-backup (7).json

Expected Behavior

Backup of the projects section

Steps to Reproduce

Open settings
Select Export Backup
Select any backup option and include the Projects (doesn't matter how many other options you select)
The resulting file will be the invalid JSON file attached.

bambuddy-support-20260112-092706.zip

Attached are debug logs from several attempts of trying all the backups until it failed.

Printer Model

X1 Carbon

Bambuddy Version

v0.1.6b7

Printer Firmware Version

latest

Installation Method

Docker

Operating System

Linux (Ubuntu/Debian)

Relevant Logs

See log file attached

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

Originally created by @MisterBeardy on GitHub (Jan 12, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/83 Originally assigned to: @maziggy on GitHub. ### Bug Description I was making a backup to move to my local machine and when selecting all, the backup was invalid. It appears that when you try to run a backup and include the Projects section the file that downloads is an invalid JSON with just the text "Internal Server Error" inside. [bambuddy-backup (7).json](https://github.com/user-attachments/files/24566654/bambuddy-backup.7.json) ### Expected Behavior Backup of the projects section ### Steps to Reproduce 1. Open settings 2. Select Export Backup 3. Select any backup option and include the Projects (doesn't matter how many other options you select) 4. The resulting file will be the invalid JSON file attached. [bambuddy-support-20260112-092706.zip](https://github.com/user-attachments/files/24566674/bambuddy-support-20260112-092706.zip) Attached are debug logs from several attempts of trying all the backups until it failed. ### Printer Model X1 Carbon ### Bambuddy Version v0.1.6b7 ### Printer Firmware Version latest ### Installation Method Docker ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs ```shell See log file attached ``` ### 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

BreizhHardware

2026-05-07 00:05:33 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-07 00:05:33 +02:00

Author

Owner

@maziggy commented on GitHub (Jan 12, 2026):

Mhhh....I'm using the backup function regulary and I'm quite sure it's fine. Also when looking at your logs, I cannot find any errors!

Just tested and it works for me.

@maziggy commented on GitHub (Jan 12, 2026): Mhhh....I'm using the backup function regulary and I'm quite sure it's fine. Also when looking at your logs, I cannot find any errors! Just tested and it works for me.

BreizhHardware commented

2026-05-07 00:05:33 +02:00

Author

Owner

@MisterBeardy commented on GitHub (Jan 12, 2026):

Well that's interesting. I just tested this again and one of my LXC containers creates the project backup file with the standard bambuddy-backup-20260112-124041.json based file name, yet the other gives me that error and the backup file name is bambuddy-backup (x).json

Edit- I went ahead and just backed up everything except for the project's and the restore worked. Tested it out on the new LXC container and it worked just fine. Probably something with my old VM.

@MisterBeardy commented on GitHub (Jan 12, 2026): Well that's interesting. I just tested this again and one of my LXC containers creates the project backup file with the standard bambuddy-backup-20260112-124041.json based file name, yet the other gives me that error and the backup file name is bambuddy-backup (x).json Edit- I went ahead and just backed up everything except for the project's and the restore worked. Tested it out on the new LXC container and it worked just fine. Probably something with my old VM.

BreizhHardware commented

2026-05-07 00:05:34 +02:00

Author

Owner

@kampfklecks commented on GitHub (Jan 12, 2026):

I wouldn't use LXC Containers for that. Better use dedicated hardware like a Raspberry Pi or use a VM. D,ocker can be buggy sometimes too, I personally switched from docker to direct install, runs so much smoother and a little bit faster

@kampfklecks commented on GitHub (Jan 12, 2026): I wouldn't use LXC Containers for that. Better use dedicated hardware like a Raspberry Pi or use a VM. D,ocker can be buggy sometimes too, I personally switched from docker to direct install, runs so much smoother and a little bit faster

BreizhHardware commented

2026-05-07 00:05:34 +02:00

Author

Owner

@MisterBeardy commented on GitHub (Jan 12, 2026):

I wouldn't use LXC Containers for that. Better use dedicated hardware like a Raspberry Pi or use a VM. D,ocker can be buggy sometimes too, I personally switched from docker to direct install, runs so much smoother and a little bit faster

Originally this was running in a VM so I tried a LXC just to make sure it wasn't something else going on. Host has enough resources that it shouldn't be an issue.

@MisterBeardy commented on GitHub (Jan 12, 2026): > I wouldn't use LXC Containers for that. Better use dedicated hardware like a Raspberry Pi or use a VM. D,ocker can be buggy sometimes too, I personally switched from docker to direct install, runs so much smoother and a little bit faster Originally this was running in a VM so I tried a LXC just to make sure it wasn't something else going on. Host has enough resources that it shouldn't be an issue.