mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #1140] [Bug]: Linux BambuStudio AppImage breaks with new certificate #818
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#818
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 @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.cerand that isn't there. I ran a bunch of long runningfinds 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.
It led me to believe maybe it's now using the system certificate store. So I added the ca cert to
/etc/ssl/certsand ranupdate-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
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
@maziggy commented on GitHub (Apr 27, 2026):
~/.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.
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).
@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.