mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #231] [Bug]: Can't download Support Bundle "Authentication required" #146
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#146
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 @bambuman on GitHub (Feb 2, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/231
Originally assigned to: @maziggy on GitHub.
Bug Description
When trying to download support bundle I get "Authentication required", looking into docker logs I see:
INFO: 172.21.1.2:34184 - "GET /api/v1/support/bundle HTTP/1.1" 401 UnauthorizedWhen I looked into Group rights there were some unselected for Administrators but I didn't take a picture before selecting them. This did not fix the problem.
Expected Behavior
Able to download support bundle.
Steps to Reproduce
Printer Model
P1S
Bambuddy Version
0.1.6.2
Printer Firmware Version
01.09.01.00
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
Screenshots
Additional Context
No response
Checklist
@bambuman commented on GitHub (Feb 2, 2026):
Downgraded to 0.1.6.1 and got the support bundle.
bambuddy-support-20260202-185930.zip
@deathly1987 commented on GitHub (Feb 2, 2026):
Same here:
And Spoolman:
@maziggy commented on GitHub (Feb 2, 2026):
Are you guys logged in as admin?
@deathly1987 commented on GitHub (Feb 2, 2026):
Yes,I also deactivated it and then I can pull the logs, but when I turn it back on, the same error occurs.
@bambuman commented on GitHub (Feb 2, 2026):
Yes. I tried with a clean install. Same error:
@mildlyokay commented on GitHub (Feb 2, 2026):
Second this, Spoolman integration is broken. /api/v1/spoolman/status always reports enabled: false and /spoolman/connect fails, even after restarts. I'm using the latest Docker image. This looks like a bug in how the enable flag is initialized or evaluated.
@Blackilli commented on GitHub (Feb 2, 2026):
Can confirm something broke with the last update. I just set up a fresh install and it wouldn't let me enable Spoolman integration. Enabling/Disabling the "Enable Spoolman" option in the settings wouldn't even trigger a request to the backend. Downgrading to 0.1.6.1 fixed this issue for me, but upgrading to latest again results in "{"detail":"Authentication required"}" from /api/v1/settings/spoolman even though I'm logged in.
@deathly1987 commented on GitHub (Feb 2, 2026):
INVALID! DON'T USE!
Should solve the problem: https://github.com/maziggy/bambuddy/pull/235
@maziggy commented on GitHub (Feb 3, 2026):
Please don't use the patch @deathly1987 provided!!!
This is fixed in branch 0.1.7b. Please let me know if it works again.
@deathly1987 commented on GitHub (Feb 3, 2026):
Sorry, my fault...
Support Bundle seems to be working.
Spoolman only half:
after load:
after enable:
after reloading:
after reactivation:
@maziggy commented on GitHub (Feb 3, 2026):
Fixed in branch 0.1.7b. Please double check.
@deathly1987 commented on GitHub (Feb 3, 2026):
Works !!!