Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Notification Failed to send the notification(s).Bad Attachment #14

Closed
1 task done
burjuyz opened this issue Nov 5, 2024 · 5 comments
Closed
1 task done

Comments

@burjuyz
Copy link

burjuyz commented Nov 5, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When i send i get error: Notification Failed to send the notification(s).Bad Attachment

Expected Behavior

Send notifications without error

Steps To Reproduce

1 open http://192.168.10.200:8024/cfg
2 try to send test message
3 error
image

Environment

- OS: Debian 12
- How docker service was installed: 
ii  docker-buildx-plugin               0.17.1-1~debian.11~bullseye         
ii  docker-ce                          5:27.3.1-1~debian.11~bullseye        
ii  docker-ce-cli                      5:27.3.1-1~debian.11~bullseye        
ii  docker-compose-plugin              2.29.7-1~debian.11~bullseye         
ii  python3-docker                     4.1.0-1.2

CPU architecture

x86-64

Docker creation

---
version: "2.1"
services:
  Apprise-api:
    image: lscr.io/linuxserver/apprise-api:latest
    container_name: apprise-api
    environment:
      - PUID=1000
      - PGID=100
      - TZ=Europe/Moscow
      - APPRISE_ATTACH_SIZE=0
    volumes:
      - /SSD/appdata/apprise/config:/config
      - /SSD/appdata/apprise/attachments:/attachments
    ports:
      - 8024:8000
    restart: unless-stopped

Container logs

2024-11-05 06:36:59,487 [WARNING] django: NOTIFY - 10.147.20.50 - Bad attachment using KEY: 9b05c3c6cb4ffea511da9c2dfdc9f4bdd85479f0561406fd5dc50042bf2bcbfa - Attachment support has been disabled

2024-11-05 06:36:59,491 [WARNING] django.request: Bad Request: /notify/9b05c3c6cb4ffea511da9c2dfdc9f4bdd85479f0561406fd5dc50042bf2bcbfa

[pid: 141|app: 0|req: 6/6] 10.147.20.50 () {44 vars in 1782 bytes} [Tue Nov  5 06:36:59 2024] POST /notify/9b05c3c6cb4ffea511da9c2dfdc9f4bdd85479f0561406fd5dc50042bf2bcbfa => generated 14 bytes in 11 msecs (HTTP/1.1 400) 6 headers in 425 bytes (1 switches on core 0)
Copy link

github-actions bot commented Nov 5, 2024

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@burjuyz burjuyz changed the title [BUG] <title> [BUG] Notification Failed to send the notification(s).Bad Attachment Nov 5, 2024
@r0m1CH
Copy link

r0m1CH commented Nov 6, 2024

Same here...

@Runnerblade84
Copy link

same here

@podkilla
Copy link

podkilla commented Dec 3, 2024

APPRISE_ATTACH_SIZE=0 disables the attachments, try setting this value to 20, restart your container and it will work.

@burjuyz
Copy link
Author

burjuyz commented Dec 4, 2024

I've changed APPRISE_ATTACH_SIZE=20 and it works now.
I tried it before and it didn't work for me. Is the team fixed it?

@burjuyz burjuyz closed this as completed Dec 4, 2024
@LinuxServer-CI LinuxServer-CI moved this from Issues to Done in Issue & PR Tracker Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

4 participants