[GH-ISSUE #448] Message correct sent, but got internal server error 50001 #344

Closed
opened 2026-05-07 00:23:17 +02:00 by BreizhHardware · 4 comments

Originally created by @Microwave-WYB on GitHub (Oct 21, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/448

$ curl -d "test" example.com:8000/ntfy
{"code":50001,"http":500,"error":"internal server error"}

However the message is successfully sent.

Originally created by @Microwave-WYB on GitHub (Oct 21, 2022). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/448 ``` $ curl -d "test" example.com:8000/ntfy {"code":50001,"http":500,"error":"internal server error"} ``` However the message is successfully sent.
BreizhHardware 2026-05-07 00:23:17 +02:00
Author
Owner

@Microwave-WYB commented on GitHub (Oct 21, 2022):

Screenshot_20221021-142216~2

<!-- gh-comment-id:1287448907 --> @Microwave-WYB commented on GitHub (Oct 21, 2022): ![Screenshot_20221021-142216~2](https://user-images.githubusercontent.com/68882116/197290859-a4fd6d5a-621f-4454-8284-30aa8dcf6a3a.png)
Author
Owner

@binwiederhier commented on GitHub (Oct 21, 2022):

The ntfy server logs are insanely detailed if you turn on debugging/tracing, see https://ntfy.sh/docs/config/#debuggingtracing

Without it, it's quite impossible to help with this generic error.

<!-- gh-comment-id:1287465363 --> @binwiederhier commented on GitHub (Oct 21, 2022): The ntfy server logs are insanely detailed if you turn on debugging/tracing, see https://ntfy.sh/docs/config/#debuggingtracing Without it, it's quite impossible to help with this generic error.
Author
Owner

@binwiederhier commented on GitHub (Nov 7, 2022):

Closed for inactivity. I'm happy to reopen if there is more info.

<!-- gh-comment-id:1305719563 --> @binwiederhier commented on GitHub (Nov 7, 2022): Closed for inactivity. I'm happy to reopen if there is more info.
Author
Owner

@arichiardi commented on GitHub (Nov 11, 2024):

For posterity, in my case it was a permission issue on the attachment dir:

{"time":"2024-11-10T18:27:01.22-06:00","level":"INFO","message":"Connection closed with HTTP 500 (ntfy error 50001)","error":"open /var/cache/ntfy/attachments/wmjZWfhjFd1d: permission denied"...
<!-- gh-comment-id:2467015731 --> @arichiardi commented on GitHub (Nov 11, 2024): For posterity, in my case it was a permission issue on the attachment dir: ``` {"time":"2024-11-10T18:27:01.22-06:00","level":"INFO","message":"Connection closed with HTTP 500 (ntfy error 50001)","error":"open /var/cache/ntfy/attachments/wmjZWfhjFd1d: permission denied"... ```
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/ntfy#344
No description provided.