1
0
Fork 0
mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 08:25:54 +02:00

[GH-ISSUE #466] [Bug]: ntfy not sending notifications #289

Closed
opened 2026-05-07 00:08:31 +02:00 by BreizhHardware · 7 comments

Originally created by @pyroco on GitHub (Feb 20, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/466

Originally assigned to: @maziggy on GitHub.

Bug Description

No notifications are being sent through ntfy.
Notifications end in error "Illegal header value" (see screenshot)

I've tried re-adding the printer multiple times, changing access code, changing the whole ntfy configuration.

Expected Behavior

No problem shoud be to send notifications through ntfy as test notifications go through without an issue.

Steps to Reproduce

  1. Trigger any notification (e.g. start the print)

Printer Model

X1 Carbon

Bambuddy Version

0.2.0 (with latest tag)

Printer Firmware Version

01.11.02.00

Installation Method

Docker

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package


Screenshots

Image Image

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
Originally created by @pyroco on GitHub (Feb 20, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/466 Originally assigned to: @maziggy on GitHub. ### Bug Description No notifications are being sent through ntfy. Notifications end in error "Illegal header value" (see screenshot) I've tried re-adding the printer multiple times, changing access code, changing the whole ntfy configuration. ### Expected Behavior No problem shoud be to send notifications through ntfy as test notifications go through without an issue. ### Steps to Reproduce 1. Trigger any notification (e.g. start the print) ### Printer Model X1 Carbon ### Bambuddy Version 0.2.0 (with latest tag) ### Printer Firmware Version 01.11.02.00 ### Installation Method Docker ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package ```shell ``` ### Screenshots <img width="782" height="498" alt="Image" src="https://github.com/user-attachments/assets/5acca4c6-bd75-4e70-b0a6-7e47579735b7" /> <img width="965" height="168" alt="Image" src="https://github.com/user-attachments/assets/bc66dfb2-d26f-4dfd-824f-c55f61eaf5f2" /> ### 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
BreizhHardware 2026-05-07 00:08:31 +02:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@maziggy commented on GitHub (Feb 20, 2026):

Should be fixed in branch 0.2.1b2. Please let me know how it goes.


If you find Bambuddy useful, please consider giving it a on GitHub — it helps others discover the project!

<!-- gh-comment-id:3936444946 --> @maziggy commented on GitHub (Feb 20, 2026): Should be fixed in branch 0.2.1b2. Please let me know how it goes. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/bambuman/bambuddy) — it helps others discover the project!
Author
Owner

@pyroco commented on GitHub (Feb 20, 2026):

I can only install 0.2.1b as that is the latest in https://github.com/maziggy/bambuddy/pkgs/container/bambuddy/versions?filters%5Bversion_type%5D=tagged and that behaves the same.

Am I doing something wrong?

<!-- gh-comment-id:3936571786 --> @pyroco commented on GitHub (Feb 20, 2026): I can only install 0.2.1b as that is the latest in https://github.com/maziggy/bambuddy/pkgs/container/bambuddy/versions?filters%5Bversion_type%5D=tagged and that behaves the same. Am I doing something wrong?
Author
Owner

@maziggy commented on GitHub (Feb 20, 2026):

You need to use branch 0.2.1b2 and rebuild the image locally.

cd to your bambuddy folder and do a

git checkout 0.2.1b2 && git pull && docker compose down && docker compose build --no-cache && docker compose up -d

<!-- gh-comment-id:3936608456 --> @maziggy commented on GitHub (Feb 20, 2026): You need to use branch 0.2.1b2 and rebuild the image locally. cd to your bambuddy folder and do a git checkout 0.2.1b2 && git pull && docker compose down && docker compose build --no-cache && docker compose up -d
Author
Owner

@pyroco commented on GitHub (Feb 20, 2026):

I had to use AI to set up git as I was using standard docker-compose only. However now it ends i different error

Image

.

<!-- gh-comment-id:3936925867 --> @pyroco commented on GitHub (Feb 20, 2026): I had to use AI to set up git as I was using standard docker-compose only. However now it ends i different error ![Image](https://github.com/user-attachments/assets/9cdd8297-2701-4db1-a3ee-22ae77cce37e) .
Author
Owner

@maziggy commented on GitHub (Feb 21, 2026):

The error you're seeing now is a different issue — your ntfy server has attachments disabled, so when Bambuddy tries to send the print thumbnail image, the server rejects it with "attachments not allowed" (error code 40014). This caused the entire notification to fail.

I've added a fallback: when the server returns "attachments not allowed", Bambuddy now automatically retries without the image so the notification still gets delivered (just without the thumbnail). Please rebuild from the 0.2.1b2 branch and try again.

<!-- gh-comment-id:3938392202 --> @maziggy commented on GitHub (Feb 21, 2026): The error you're seeing now is a different issue — your ntfy server has attachments disabled, so when Bambuddy tries to send the print thumbnail image, the server rejects it with "attachments not allowed" (error code 40014). This caused the entire notification to fail. I've added a fallback: when the server returns "attachments not allowed", Bambuddy now automatically retries without the image so the notification still gets delivered (just without the thumbnail). Please rebuild from the 0.2.1b2 branch and try again.
Author
Owner

@pyroco commented on GitHub (Feb 21, 2026):

Everything seems to be working just fine. I've enabled also attachments on my ntfy so that works fine too.

Thanks for your quick actions ✌🏻 will you publish it also to docker?

<!-- gh-comment-id:3938503655 --> @pyroco commented on GitHub (Feb 21, 2026): Everything seems to be working just fine. I've enabled also attachments on my ntfy so that works fine too. Thanks for your quick actions ✌🏻 will you publish it also to docker?
Author
Owner

@maziggy commented on GitHub (Feb 21, 2026):

Thanks for the feedback. Maybe later as 0.2.1b2.

<!-- gh-comment-id:3938508674 --> @maziggy commented on GitHub (Feb 21, 2026): Thanks for the feedback. Maybe later as 0.2.1b2.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/bambuddy-maziggy-1#289
No description provided.