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

Webinterface Notification panel report "Bad Attachment" when none as been chosed #168

Open
federicofortini opened this issue Jan 29, 2024 · 7 comments
Labels
bug Something isn't working

Comments

@federicofortini
Copy link

federicofortini commented Jan 29, 2024

🪲 Describe the bug
In version 0.9.8 the "notification" panel used to test configuration report an error: "Failed to send the notification(s).Bad attachment" even if did not chose anything at all. Notification invoked from CURL works fine.

💡 Screenshots and Logs
2024-01-29T17:06:08.741289391Z 2024-01-29 11:06:08,740 [WARNING] django: NOTIFY - 172.18.0.15 - Bad attachment specified
2024-01-29T17:06:08.742333386Z 2024-01-29 11:06:08,741 [WARNING] django.request: Bad Request: /notify/apprise
2024-01-29T17:06:08.743187507Z [pid: 147|app: 0|req: 52/72] 172.18.0.15 () {94 vars in 3559 bytes} [Mon Jan 29 11:06:08 2024] POST /notify/apprise => generated 14 bytes in 6 msecs (HTTP/1.1 400) 5 headers in 290 bytes (1 switches on core 0)

Here the screenshot from UI:
Apprise

💻 Your System Details:
Docker container by Linuxserver:
https://github.com/linuxserver/docker-apprise-api/releases/tag/v0.9.8-ls113

🔮 Additional context
Create a telegram configuration, mine is:
me=tgram://bot:key/chatid/?silent=yes
go to "notification" tab and subit a test notification

@federicofortini federicofortini added the bug Something isn't working label Jan 29, 2024
@caronc
Copy link
Owner

caronc commented Jan 29, 2024

That's really interesting, i can't reproduce that here. What browser (and version) are you using?

@federicofortini
Copy link
Author

federicofortini commented Jan 30, 2024

Goodmorning, I tested:

  • BRAVE v1.62.153 - Windows 10
  • Chrome 120.0.6099.231 - Android 14
  • Chrome 106.0.5249.119 - Windows 10
  • Firefox 120.0 - Windows 10

Let me know if i can do some additional test.

Federico

@federicofortini
Copy link
Author

I tried also with caronc/apprise-api docker image, nothing changed.

Federico

@caronc
Copy link
Owner

caronc commented Feb 1, 2024

I think i fixed this 🚀

@federicofortini
Copy link
Author

With latest version it works.

Thanks,
Federico

@fpatrick
Copy link

fpatrick commented Sep 15, 2024

I have the same error with v1.1.6-ls151 of linuxserver build. I've been hours trying to make it work.

Log:

2024-09-15 09:14:15,395 [WARNING] django: NOTIFY - 10.0.0.14 - Bad attachment using KEY: - Attachment support has been disabled
2024-09-15 09:14:15,395 [WARNING] django.request: Bad Request: /notify/
[pid: 144|app: 0|req: 5/5] 10.0.0.14 () {48 vars in 1423 bytes} [Sun Sep 15 09:14:15 2024] POST /notify/ => generated 14 bytes in 2 msecs (HTTP/1.1 400) 6 headers in 424 bytes (1 switches on core 0)

@caronc caronc reopened this Sep 15, 2024
@caronc
Copy link
Owner

caronc commented Sep 15, 2024

Related to: caronc/apprise#1200 (comment)

For now please use the Apprise Docker container that i maintain: https://hub.docker.com/r/caronc/apprise

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants