[GH-ISSUE #629] unifiedpush: Some servers send invalid "Authorization" header, which leads to 401 responses #469

Closed
opened 2026-05-07 00:24:31 +02:00 by BreizhHardware · 6 comments

Originally created by @Boebbele on GitHub (Feb 22, 2023).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/629

Unifiedpush dont works on iodeos with microg.
Ntfy Github fdroid Version.
Push messages with curl from terminal works great.

But unifiedpush dont works. Tested with fedilab, tusky and fluffychat.

If I use unifiedpush with conversations an its integrated pushserver it works perfekt.

Originally created by @Boebbele on GitHub (Feb 22, 2023). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/629 Unifiedpush dont works on iodeos with microg. Ntfy Github fdroid Version. Push messages with curl from terminal works great. But unifiedpush dont works. Tested with fedilab, tusky and fluffychat. If I use unifiedpush with conversations an its integrated pushserver it works perfekt.
Author
Owner

@ghost commented on GitHub (Feb 22, 2023):

Additional information:
ntfy also stopped working on Samsung devices after the latest firmware update (Android 13).
Tested with Tusky and Fedilab on a Samsung Galaxy Tab S7 and a Samsung Galaxy S22 Ultra.

<!-- gh-comment-id:1440506302 --> @ghost commented on GitHub (Feb 22, 2023): Additional information: ntfy also stopped working on Samsung devices after the latest firmware update (Android 13). Tested with Tusky and Fedilab on a Samsung Galaxy Tab S7 and a Samsung Galaxy S22 Ultra.
Author
Owner

@binwiederhier commented on GitHub (Feb 22, 2023):

This is not enough information.

Both ntfy on Android and the ntfy server have significant logging capabilities. Please post some logs or investigate further:

  • ntfy Android: Settings -> Record logs
  • ntfy server: Turn "log-level: DEBUG or TRACE"
<!-- gh-comment-id:1440566626 --> @binwiederhier commented on GitHub (Feb 22, 2023): This is not enough information. Both ntfy on Android and the ntfy server have significant logging capabilities. Please post some logs or investigate further: - ntfy Android: Settings -> Record logs - ntfy server: Turn "log-level: DEBUG or TRACE"
Author
Owner

@ghost commented on GitHub (Feb 22, 2023):

Well the log file doesn't show anything except for the NtfySubscriberConn entries telling "Connection is active" which show up every 30 seconds.
I received some notifications in the meanwhile, but none of the show up in the log in any way.

It worked perfectly fine until I guess last week when I received the latest Samsung firmware updates.
After that update ntfy stopped working.

Edot: In the meanwhile some additional entries showed up.

So here is the link to the log
https://nopaste.net/11KT9vDa0m

<!-- gh-comment-id:1440619093 --> @ghost commented on GitHub (Feb 22, 2023): Well the log file doesn't show anything except for the NtfySubscriberConn entries telling "Connection is active" which show up every 30 seconds. I received some notifications in the meanwhile, but none of the show up in the log in any way. It worked perfectly fine until I guess last week when I received the latest Samsung firmware updates. After that update ntfy stopped working. Edot: In the meanwhile some additional entries showed up. So here is the link to the log https://nopaste.net/11KT9vDa0m
Author
Owner

@Boebbele commented on GitHub (Feb 23, 2023):

survey on problems with UnifiedPush on Mastodon: https://blueplanet.social/@nichu42/109908840871096554
Perhaps it helps...

<!-- gh-comment-id:1441397728 --> @Boebbele commented on GitHub (Feb 23, 2023): survey on problems with UnifiedPush on Mastodon: https://blueplanet.social/@nichu42/109908840871096554 Perhaps it helps...
Author
Owner

@binwiederhier commented on GitHub (Feb 23, 2023):

@S1m approached me and explained the actual problem. It seems that some app servers send an Authorization header to ntfy, even though they do not need or should. As of 2.0, ntfy treats the existence of that header as an attempt to authenticate.

In order to support these faulty servers, I'll make a change to treat any headers that are not Basic or Bearer as if they did not exist.

<!-- gh-comment-id:1441931979 --> @binwiederhier commented on GitHub (Feb 23, 2023): @S1m approached me and explained the actual problem. It seems that some app servers send an `Authorization` header to ntfy, even though they do not need or should. As of 2.0, ntfy treats the existence of that header as an attempt to authenticate. In order to support these faulty servers, I'll make a change to treat any headers that are not `Basic` or `Bearer` as if they did not exist.
Author
Owner

@binwiederhier commented on GitHub (Feb 23, 2023):

Fixed in github.com/binwiederhier/ntfy@422ad0cc5d

<!-- gh-comment-id:1441962138 --> @binwiederhier commented on GitHub (Feb 23, 2023): Fixed in https://github.com/binwiederhier/ntfy/commit/422ad0cc5dd7b6bdf69fde1b4fc8d143271e2958
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#469
No description provided.