starred/bambuddy

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 05:35:30 +02:00

[GH-ISSUE #1140] [Bug]: Linux BambuStudio AppImage breaks with new certificate #817

New issue

Closed

opened 2026-05-06 12:33:08 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

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

Owner

Originally created by @tfili on GitHub (Apr 27, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1140

Originally assigned to: @maziggy on GitHub.

Component

Bambuddy

Bug Description

I upgraded to the latest Bambuddy, which caused a new certificate to be generated. I did add a local OIDC provider. Don't think that matters as I can log in fine to BamBuddy. It is installed via the Proxmox community script.

I went to go update it in BambuStudio and the files that were there before seem to be gone. I'm on the latest Bambu Studio 2.6. I probably have updated versions of this, but I don't really know as this was the first issue I had.

I've had it working for a little while, so I don't recall the install process, but I don't remember it being hard to add the certificate before. The docs say ~/.local/share/BambuStudio/resources/cert/printer.cer and that isn't there. I ran a bunch of long running finds searching for the file or certificates in general in my entire home directory. I can't find anything. Studio seems to be acting a little weird with even connecting to the printer directly but it does work. Sometimes I need to reenter the access code. The connection error to the virtual printer is -1, which from what I can tell is TLS related.

I'm just having trouble tracking down where the problem is. Bambuddy seems to be reachable and the ports 990 and 8883 seem to be available. I did notice the following in BambuStudio.conf.

        "tls_accepted_cert_store_location": "/etc/ssl/certs/ca-certificates.crt",
        "tls_cert_store_accepted": "yes",

It led me to believe maybe it's now using the system certificate store. So I added the ca cert to /etc/ssl/certs and ran update-ca-certificates. I connected to the Bambuddy's MQTT port and validated the ca cert is correct for the certificate it's using and the connection is valid.

I'm at a loss. I'm not sure where the disconnect between Studio and Bambuddy is. If it is on the Studio side caused by an update, maybe the doc here needs updating and thats it. I'd be happy to do that if I can just figure out where the disconnect happened. Had to switch back to Cloud printing for the time being.

Expected Behavior

Go to the certificate file, add the new CA from the Bambuddy server and print.

Steps to Reproduce

In Bambu Studio, add the printer
Get the connection error

Printer Model

P1S

Bambuddy Version

0.2.3.2

SpoolBuddy Version

No response

Printer Firmware Version

01.10.00.00

Installation Method

Other

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

No response

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 @tfili on GitHub (Apr 27, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1140 Originally assigned to: @maziggy on GitHub. ### Component Bambuddy ### Bug Description I upgraded to the latest Bambuddy, which caused a new certificate to be generated. I did add a local OIDC provider. Don't think that matters as I can log in fine to BamBuddy. It is installed via the Proxmox community script. I went to go update it in BambuStudio and the files that were there before seem to be gone. I'm on the latest Bambu Studio 2.6. I probably have updated versions of this, but I don't really know as this was the first issue I had. I've had it working for a little while, so I don't recall the install process, but I don't remember it being hard to add the certificate before. The docs say `~/.local/share/BambuStudio/resources/cert/printer.cer` and that isn't there. I ran a bunch of long running `find`s searching for the file or certificates in general in my entire home directory. I can't find anything. Studio seems to be acting a little weird with even connecting to the printer directly but it does work. Sometimes I need to reenter the access code. The connection error to the virtual printer is `-1`, which from what I can tell is TLS related. I'm just having trouble tracking down where the problem is. Bambuddy seems to be reachable and the ports 990 and 8883 seem to be available. I did notice the following in BambuStudio.conf. ``` "tls_accepted_cert_store_location": "/etc/ssl/certs/ca-certificates.crt", "tls_cert_store_accepted": "yes", ``` It led me to believe maybe it's now using the system certificate store. So I added the ca cert to `/etc/ssl/certs` and ran `update-ca-certificates`. I connected to the Bambuddy's MQTT port and validated the ca cert is correct for the certificate it's using and the connection is valid. I'm at a loss. I'm not sure where the disconnect between Studio and Bambuddy is. If it is on the Studio side caused by an update, maybe the doc here needs updating and thats it. I'd be happy to do that if I can just figure out where the disconnect happened. Had to switch back to Cloud printing for the time being. ### Expected Behavior Go to the certificate file, add the new CA from the Bambuddy server and print. ### Steps to Reproduce 1. In Bambu Studio, add the printer 2. Get the connection error ### Printer Model P1S ### Bambuddy Version 0.2.3.2 ### SpoolBuddy Version _No response_ ### Printer Firmware Version 01.10.00.00 ### Installation Method Other ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package _No response_ ### 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-06 12:33:08 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

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

Author

Owner

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

AppImage path in the wiki is wrong.
~/.local/share/BambuStudio/resources/cert/printer.cer is the Flatpak-style path. AppImages don't extract there; printer.cer is bundled inside the squashfs. To edit it inside an AppImage:

./Bambu_Studio_linux_*.AppImage --appimage-extract
-> edit squashfs-root/usr/share/Bambu Studio/resources/cert/printer.cer
./squashfs-root/AppRun

I'll fix this in the wiki.

The cleaner option on Linux is the system CA store (which your BambuStudio.conf is already configured to use — tls_cert_store_accepted: yes). Your update-ca-certificates run was a no-op because that command only picks up *.crt files placed under /usr/local/share/ca-certificates/, not files dropped into /etc/ssl/certs/. Try:

sudo cp bbl_ca.crt /usr/local/share/ca-certificates/bambuddy-ca.crt
sudo update-ca-certificates
grep -c "BEGIN CERTIFICATE" /etc/ssl/certs/ca-certificates.crt # should increase by 1

Then fully quit and restart BambuStudio (not just close the window).

@maziggy commented on GitHub (Apr 27, 2026): 1. AppImage path in the wiki is wrong. ~/.local/share/BambuStudio/resources/cert/printer.cer is the Flatpak-style path. AppImages don't extract there; printer.cer is bundled inside the squashfs. To edit it inside an AppImage: ./Bambu_Studio_linux_*.AppImage --appimage-extract -> edit squashfs-root/usr/share/Bambu Studio/resources/cert/printer.cer ./squashfs-root/AppRun I'll fix this in the wiki. 2. The cleaner option on Linux is the system CA store (which your BambuStudio.conf is already configured to use — tls_cert_store_accepted: yes). Your update-ca-certificates run was a no-op because that command only picks up *.crt files placed under /usr/local/share/ca-certificates/, not files dropped into /etc/ssl/certs/. Try: sudo cp bbl_ca.crt /usr/local/share/ca-certificates/bambuddy-ca.crt sudo update-ca-certificates grep -c "BEGIN CERTIFICATE" /etc/ssl/certs/ca-certificates.crt # should increase by 1 Then fully quit and restart BambuStudio (not just close the window).

BreizhHardware commented

2026-05-06 12:33:09 +02:00

Author

Owner

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

@maziggy Sorry, I had an error on my original post. I have the certificate in the correct spot (/usr/local/share/ca-certificates/). Still no luck. Thanks for the explanation about the FlatPak vs AppImage and that my assumption that it should use the system store is correct.

Unfortunately still no luck connecting using the system store. Extracting the app image and updating printers.cer does work though. Thats workable for now. I'll write a script to handle that all.

Thanks again for your help.

@tfili commented on GitHub (Apr 27, 2026): @maziggy Sorry, I had an error on my original post. I have the certificate in the correct spot (`/usr/local/share/ca-certificates/`). Still no luck. Thanks for the explanation about the FlatPak vs AppImage and that my assumption that it should use the system store is correct. Unfortunately still no luck connecting using the system store. Extracting the app image and updating printers.cer does work though. Thats workable for now. I'll write a script to handle that all. Thanks again for your help.