mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #254] [Bug]: Unable to start application with printer proxy #154
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
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#154
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 @karaktaka on GitHub (Feb 3, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/254
Originally assigned to: @maziggy on GitHub.
Bug Description
I enabled the new printer proxy functionality and now bambuddy is unable to start.
Expected Behavior
Restart of Bambuddy is possible with printer proxy enabled.
Steps to Reproduce
Printer Model
P1S
Bambuddy Version
0.1.7
Printer Firmware Version
01.09.01.00
Installation Method
Docker
Operating System
Linux (Other)
Relevant Logs / Support Package
Screenshots
No response
Additional Context
No response
Checklist
@maziggy commented on GitHub (Feb 3, 2026):
Just tested and cannot reproduce the error. Please do a "docker compose build --no-cache && docker compose up -d".
@karaktaka commented on GitHub (Feb 3, 2026):
That was the first thing I tried. Removing the image and re-pulling. Also 'compose down' and 'up'. Still the same error.
@karaktaka commented on GitHub (Feb 3, 2026):
Restoring a Backup without the printer proxy enabled brings back Bambuddy, but enabling it again and then restarting the container brings back the error message and prevents bambuddy from starting.
@maziggy commented on GitHub (Feb 4, 2026):
Please check if the user running Bambuddy has full access to virtual_printer/ folder.
ls -al virtual_printer/ virtual_printer/certs/
@karaktaka commented on GitHub (Feb 4, 2026):
The container is running as root and the permissions are fine:
@maziggy commented on GitHub (Feb 4, 2026):
Just pushed an proxy update. If you wanna try use branch 0.1.8b.
@karaktaka commented on GitHub (Feb 4, 2026):
Looks like it did not solve the problem. Enabling the virtual printer and then restarting the container will result in a crashloop:
@karaktaka commented on GitHub (Feb 4, 2026):
This is the same log, but with DEBUG enabled:
@karaktaka commented on GitHub (Feb 4, 2026):
I just rebuild the image with the latest merge to branch 0.1.8b and my changes. Looks good now.
@maziggy commented on GitHub (Feb 4, 2026):
Thanks!!!
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!