[GH-ISSUE #731] [Bug]: Cannot update native install v0.2.1.1

BreizhHardware commented

2026-05-06 12:30:06 +02:00

Owner

Originally created by @Teolhyn on GitHub (Mar 17, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/731

Originally assigned to: @maziggy on GitHub.

Bug Description

Documentation states:

Installing Updates

(https://wiki.bambuddy.cool/features/system-info/?h=update#installing-updates)
When an update is available:

Review the release notes

Click Update to begin

Progress is shown during download and installation

Bambuddy restarts automatically after the update

But if I click update on the web UI it jumps to general settings, where I can only see:

However, I have done the native installation so I cannot use docker to update and I do not see any other way to update. Also, I find it odd that it shows me daily beta build while I have the Include beat versions toggled off.

Expected Behavior

I expected clicking update to start updating the current version to next stable.

Steps to Reproduce

Install using the native install script
Login as admin
click update from the bottom of the left navigation panel next to current version number.

Printer Model

X1 Carbon

Bambuddy Version

0.2.1.1

Printer Firmware Version

Installation Method

Manual (git clone)

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

No response

Screenshots

No response

Additional Context

I have to check the "I am using the latest version of Bambuddy" to create the issue but due to it being an issue with updating I feel like this should be sent without this.

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 @Teolhyn on GitHub (Mar 17, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/731 Originally assigned to: @maziggy on GitHub. ### Bug Description Documentation states: > ### Installing Updates > (https://wiki.bambuddy.cool/features/system-info/?h=update#installing-updates) > When an update is available: > > 1. Review the release notes > 2. Click Update to begin > 3. Progress is shown during download and installation > 4. Bambuddy restarts automatically after the update But if I click update on the web UI it jumps to general settings, where I can only see: <img width="200" alt="Image" src="https://github.com/user-attachments/assets/d62ef646-71a8-4149-b50e-86c669d4595d" /> However, I have done the native installation so I cannot use docker to update and I do not see any other way to update. Also, I find it odd that it shows me daily beta build while I have the `Include beat versions` toggled off. ### Expected Behavior I expected clicking update to start updating the current version to next stable. ### Steps to Reproduce 1. Install using the native install script 2. Login as admin 3. click update from the bottom of the left navigation panel next to current version number. ### Printer Model X1 Carbon ### Bambuddy Version 0.2.1.1 ### Printer Firmware Version - ### Installation Method Manual (git clone) ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package _No response_ ### Screenshots _No response_ ### Additional Context I have to check the "I am using the latest version of Bambuddy" to create the issue but due to it being an issue with updating I feel like this should be sent without this. ### 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-06 12:30:06 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-06 12:30:07 +02:00

Author

Owner

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

However, I have done the native installation so I cannot use docker to update and I do not see any other way to update

Wait....the screenshot shows a Docker installation and not a native one?!

@maziggy commented on GitHub (Mar 17, 2026): >However, I have done the native installation so I cannot use docker to update and I do not see any other way to update Wait....the screenshot shows a Docker installation and not a native one?!

BreizhHardware commented

2026-05-06 12:30:07 +02:00

Author

Owner

@Teolhyn commented on GitHub (Mar 17, 2026):

However, I have done the native installation so I cannot use docker to update and I do not see any other way to update

Wait....the screenshot shows a Docker installation and not a native one?!

Which seems odd to me also, but I ensured that I have no containers running. It's running on a fresh server where I've done a native installation using the script provided in the docs

curl -fsSL https://raw.githubusercontent.com/maziggy/bambuddy/main/install/install.sh -o install.sh && chmod +x install.sh && ./install.sh

Then I am accessing it on my own computer by routing it through an ssh tunnel like:

ssh -N -L 8080:localhost:8000 username@host

And then accessing localhost:8080 on my own computer.

@Teolhyn commented on GitHub (Mar 17, 2026): > > However, I have done the native installation so I cannot use docker to update and I do not see any other way to update > > Wait....the screenshot shows a Docker installation and not a native one?! Which seems odd to me also, but I ensured that I have no containers running. It's running on a fresh server where I've done a native installation using the script provided in the docs ``` curl -fsSL https://raw.githubusercontent.com/maziggy/bambuddy/main/install/install.sh -o install.sh && chmod +x install.sh && ./install.sh ``` Then I am accessing it on my own computer by routing it through an ssh tunnel like: ``` ssh -N -L 8080:localhost:8000 username@host ``` And then accessing localhost:8080 on my own computer.

BreizhHardware commented

2026-05-06 12:30:07 +02:00

Author

Owner

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

No, that cannot be. Either you are still running Bambuddy on Docker, or there's a cache problem. Did you forced a page reload?

@maziggy commented on GitHub (Mar 17, 2026): No, that cannot be. Either you are still running Bambuddy on Docker, or there's a cache problem. Did you forced a page reload?

BreizhHardware commented

2026-05-06 12:30:07 +02:00

Author

Owner

@Teolhyn commented on GitHub (Mar 17, 2026):

No, that cannot be. Either you are still running Bambuddy on Docker, or there's a cache problem. Did you forced a page reload?

My windows PC which I use to access the server does not have docker installed. I shut down the ssh connection to see that also my browser could not show the UI anymore. Here's screenshots from my server:

I restarted the service, closed and opened the tunnel again, hard reloaded the page, even tried different browser, but still the UI shows what I originally posted.

Edit: if there's some specific info I can give you that would help to debug let me know. But as for now I am 99.9% sure this is a bug rather than an error on my side.

@Teolhyn commented on GitHub (Mar 17, 2026): > No, that cannot be. Either you are still running Bambuddy on Docker, or there's a cache problem. Did you forced a page reload? My windows PC which I use to access the server does not have docker installed. I shut down the ssh connection to see that also my browser could not show the UI anymore. Here's screenshots from my server: <img width="400" alt="Image" src="https://github.com/user-attachments/assets/d20ab4ef-6e97-42e3-857d-21aeb874f492" /> I restarted the service, closed and opened the tunnel again, hard reloaded the page, even tried different browser, but still the UI shows what I originally posted. Edit: if there's some specific info I can give you that would help to debug let me know. But as for now I am 99.9% sure this is a bug rather than an error on my side.

BreizhHardware commented

2026-05-06 12:30:07 +02:00

Author

Owner

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

Cannot reproduce, sorry.

Need a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

Best would be:

enable debug logging
restart Bambuddy
Let it run for 1-2 minutes to collect logs.

@maziggy commented on GitHub (Mar 17, 2026): Cannot reproduce, sorry. Need a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging Best would be: 1. enable debug logging 2. restart Bambuddy 3. Let it run for 1-2 minutes to collect logs.

BreizhHardware commented

2026-05-06 12:30:07 +02:00

Author

Owner

@Teolhyn commented on GitHub (Mar 17, 2026):

Here are the files, hope they help!

bambuddy.log

support-info.json

I noticed that also the support-info has "docker": false in environment.

@Teolhyn commented on GitHub (Mar 17, 2026): Here are the files, hope they help! [bambuddy.log](https://github.com/user-attachments/files/26054306/bambuddy.log) [support-info.json](https://github.com/user-attachments/files/26054311/support-info.json) I noticed that also the support-info has `"docker": false` in environment.

BreizhHardware commented

2026-05-06 12:30:08 +02:00

Author

Owner

@Keybored02 commented on GitHub (Mar 17, 2026):

I think I found it:

The Settings update panel shows Docker instructions based only on updateCheck.is_docker in SettingsPage.tsx:1765.
That value comes from /updates/check, which uses _is_docker_environment() in updates.py:35 and returns Docker if .git is missing via updates.py:47.
The support package docker flag uses a different function, is_running_in_docker(), in support.py:424, implemented in discovery.py:26, and it does not use the “missing .git means Docker” heuristic.

So a native install without a .git directory can show Docker update instructions in Settings, while support package reports docker=false.

@Keybored02 commented on GitHub (Mar 17, 2026): I think I found it: 1. The Settings update panel shows Docker instructions based only on `updateCheck.is_docker` in SettingsPage.tsx:1765. 2. That value comes from /updates/check, which uses `_is_docker_environment()` in updates.py:35 and returns Docker if .git is missing via updates.py:47. 3. The support package docker flag uses a different function,` is_running_in_docker()`, in support.py:424, implemented in discovery.py:26, and it does not use the “missing .git means Docker” heuristic. So a native install without a .git directory can show Docker update instructions in Settings, while support package reports docker=false.

BreizhHardware commented

2026-05-06 12:30:08 +02:00

Author

Owner

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

Yes, I just fixed it.

Problem is, that we changed the complete update function after verion 0.2.2.1.

I would suggest the following:

Save your data
Copy the following folder to a backup location

bambuddy.db — the SQLite database (after WAL checkpoint)
archive/ — print archives
virtual_printer/ — virtual printer data (SSL certs, etc.)
plate_calibration/ — plate detection reference images
icons/ — custom icons
projects/ — project files

Delete your complete bambuddy folder
Install latest 0.2.2 version of Bambuddy by using https://raw.githubusercontent.com/maziggy/bambuddy/refs/heads/main/install/install.sh and DON'T start Bambuddy at the end of installation script.
Move your backed up folder back to the Bambuddy folder
sudo systemctl start bambuddy

On first start you database is auto-migrated to new version and Bambuddy should run on latest version with your data.

@maziggy commented on GitHub (Mar 17, 2026): Yes, I just fixed it. Problem is, that we changed the complete update function after verion 0.2.2.1. I would suggest the following: 1. Save your data Copy the following folder to a backup location - bambuddy.db — the SQLite database (after WAL checkpoint) - archive/ — print archives - virtual_printer/ — virtual printer data (SSL certs, etc.) - plate_calibration/ — plate detection reference images - icons/ — custom icons - projects/ — project files 2. Delete your complete bambuddy folder 3. Install latest 0.2.2 version of Bambuddy by using https://raw.githubusercontent.com/maziggy/bambuddy/refs/heads/main/install/install.sh **_and DON'T start Bambuddy at the end of installation script._** 4. Move your backed up folder back to the Bambuddy folder 5. sudo systemctl start bambuddy On first start you database is auto-migrated to new version and Bambuddy should run on latest version with your data.

Rows
Columns

[GH-ISSUE #731] [Bug]: Cannot update native install v0.2.1.1 #488

Bug Description

Installing Updates

Expected Behavior

Steps to Reproduce

Printer Model

Bambuddy Version

Printer Firmware Version

Installation Method

Operating System

Relevant Logs / Support Package

Screenshots

Additional Context

Checklist