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

Bad Request: /notify/apprise in Docker #169

Closed
jotka opened this issue Jan 31, 2024 · 2 comments
Closed

Bad Request: /notify/apprise in Docker #169

jotka opened this issue Jan 31, 2024 · 2 comments
Labels
question Further information is requested

Comments

@jotka
Copy link

jotka commented Jan 31, 2024

Question

I've started apprise with docker:

docker run --name=apprise volume=/docker/apprise:/config --restart=unless-stopped --detach=true caronc/apprise:latest

When I click the send Send Notification in the UI, I get Failed to send the notification(s).Bad attachment", no matter what services I have configured. I'm not adding any attachment to the test notification.

In the logs:

[pid: 148|app: 0|req: 4/4] 172.18.0.6 () {46 vars in 846 bytes} [Tue Jan 30 22:43:26 2024] GET /json/urls/apprise/?privacy=1 => generated 190 bytes in 120 msecs (HTTP/1.1 200) 5 headers in 274 bytes (1 switches on core 0)

[pid: 148|app: 0|req: 5/5] 172.18.0.6 () {52 vars in 917 bytes} [Tue Jan 30 22:43:27 2024] POST /get/apprise => generated 94 bytes in 1 msecs (HTTP/1.1 200) 5 headers in 273 bytes (1 switches on core 0)

2024-01-30 22:43:38,843 [WARNING] django: NOTIFY - 172.18.0.6 - Bad attachment specified

2024-01-30 22:43:38,844 [WARNING] django.request: Bad Request: /notify/apprise
[pid: 148|app: 0|req: 6/6] 172.18.0.6 () {54 vars in 1002 bytes} [Tue Jan 30 22:43:38 2024] POST /notify/apprise => generated 14 bytes in 4 msecs (HTTP/1.1 400) 5 headers in 290 bytes (1 switches on core 0)
@jotka jotka added the question Further information is requested label Jan 31, 2024
@caronc caronc transferred this issue from caronc/apprise Feb 1, 2024
@caronc
Copy link
Owner

caronc commented Feb 1, 2024

This is a duplicate of #168 and has been rectified now. Make sure you pull the :latest branch just pushed (v0.9.9)

@caronc
Copy link
Owner

caronc commented Feb 4, 2024

Closing issue off as it has been resolved now.

@caronc caronc closed this as completed Feb 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants