starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Bug]: notifications fail despite apprise setup and working. #2442

New Issue
Closed
opened 2026-04-25 00:07:10 +02:00 by adam · 2 comments
adam commented 2026-04-25 00:07:10 +02:00
Owner
Copy Link
Copy Source

Originally created by @Goldmaster on GitHub (Dec 28, 2024).

What happened?

I have set up both apprise and mailrise to convert notifications to be sent via pushover.

Apprise works correctly and I can send a test notification. But if follow the info adding local ip and port with /notify at the end. The test notification fails. But strangely, the mail rise notification works correctly.

What did you expect to happen?

Test notification via pushover should come though from audiobookshelf when using the notifications option in settings.

Steps to reproduce the issue

  1. Setup apprise and send a test notification in apprise web ui.
  2. take note of local ip address and port apprise is set up on. Then setup notifications in audiobook shelf adding /notify to the end
  3. an error shows up, saying failed internal server error.

Audiobookshelf version

v2.17.5 (2024-12-08)

How are you running audiobookshelf?

Docker

What OS is your Audiobookshelf server hosted from?

Linux

If the issue is being seen in the UI, what browsers are you seeing the problem on?

Firefox

Logs

text  error  warn  system  array  login  

      scheduling: 'lifo',
      maxTotalSockets: Infinity,
      totalSocketCount: 0,
      [Symbol(shapeMode)]: false,
      [Symbol(kCapture)]: false
    },
    socketPath: undefined,
    method: 'POST',
    maxHeaderSize: undefined,
    insecureHTTPParser: undefined,
    joinDuplicateHeaders: undefined,
    path: '/notify',
    _ended: false,
    res: IncomingMessage {
      _events: [Object],
      _readableState: [ReadableState],
      _maxListeners: undefined,
      socket: [Socket],
      httpVersionMajor: 1,
      httpVersionMinor: 1,
      httpVersion: '1.1',
      complete: false,
      rawHeaders: [Array],
      rawTrailers: [],
      joinDuplicateHeaders: undefined,
      aborted: true,
      upgrade: false,
      url: '',
      method: null,
      statusCode: 204,
      statusMessage: 'No Content',
      client: [Socket],
      _consuming: true,
      _dumped: false,
      req: [Circular *1],
      _eventsCount: 4,
      responseUrl: 'http://192.168.1.3:8230/notify',
      redirects: [],
      [Symbol(shapeMode)]: true,
      [Symbol(kCapture)]: false,
      [Symbol(kHeaders)]: [Object],
      [Symbol(kHeadersCount)]: 18,
      [Symbol(kTrailers)]: null,
      [Symbol(kTrailersCount)]: 0
    },
    aborted: false,
    timeoutCb: [Function: emitRequestTimeout],
    upgradeOrConnect: false,
    parser: null,
    maxHeadersCount: null,
    reusedSocket: false,
    host: '192.168.1.3',
    protocol: 'http:',
    _redirectable: Writable {
      _events: [Object],
      _writableState: [WritableState],
      _maxListeners: undefined,
      _options: [Object],
      _ended: true,
      _ending: true,
      _redirectCount: 0,
      _redirects: [],
      _requestBodyLength: 190,
      _requestBodyBuffers: [],
      _eventsCount: 3,
      _onNativeResponse: [Function (anonymous)],
      _currentRequest: [Circular *1],
      _currentUrl: 'http://192.168.1.3:8230/notify',
      _timeout: null,
      [Symbol(shapeMode)]: true,
      [Symbol(kCapture)]: false
    },
    [Symbol(shapeMode)]: false,
    [Symbol(kCapture)]: false,
    [Symbol(kBytesWritten)]: 0,
    [Symbol(kNeedDrain)]: false,
    [Symbol(corked)]: 0,
    [Symbol(kOutHeaders)]: [Object: null prototype] {
      accept: [Array],
      'content-type': [Array],
      'user-agent': [Array],
      'content-length': [Array],
      host: [Array]
    },
    [Symbol(errored)]: null,
    [Symbol(kHighWaterMark)]: 16384,
    [Symbol(kRejectNonStandardBodyWrites)]: false,
    [Symbol(kUniqueHeaders)]: null
  }
}

Additional Notes

Just found out that one has to put in a pushover url and not apprise like it suggests should be as

https://api.pushover.net/1/messages.json?user={USER_KEY}&token={TOKEN}&message=New

Any chance of the info being updated or proper support for apprise in the future, please?

Originally created by @Goldmaster on GitHub (Dec 28, 2024). ### What happened? I have set up both apprise and mailrise to convert notifications to be sent via pushover. Apprise works correctly and I can send a test notification. But if follow the info adding local ip and port with /notify at the end. The test notification fails. But strangely, the mail rise notification works correctly. ### What did you expect to happen? Test notification via pushover should come though from audiobookshelf when using the notifications option in settings. ### Steps to reproduce the issue 1. Setup apprise and send a test notification in apprise web ui. 2. take note of local ip address and port apprise is set up on. Then setup notifications in audiobook shelf adding /notify to the end 3. an error shows up, saying failed internal server error. ### Audiobookshelf version v2.17.5 (2024-12-08) ### How are you running audiobookshelf? Docker ### What OS is your Audiobookshelf server hosted from? Linux ### If the issue is being seen in the UI, what browsers are you seeing the problem on? Firefox ### Logs ```shell text error warn system array login scheduling: 'lifo', maxTotalSockets: Infinity, totalSocketCount: 0, [Symbol(shapeMode)]: false, [Symbol(kCapture)]: false }, socketPath: undefined, method: 'POST', maxHeaderSize: undefined, insecureHTTPParser: undefined, joinDuplicateHeaders: undefined, path: '/notify', _ended: false, res: IncomingMessage { _events: [Object], _readableState: [ReadableState], _maxListeners: undefined, socket: [Socket], httpVersionMajor: 1, httpVersionMinor: 1, httpVersion: '1.1', complete: false, rawHeaders: [Array], rawTrailers: [], joinDuplicateHeaders: undefined, aborted: true, upgrade: false, url: '', method: null, statusCode: 204, statusMessage: 'No Content', client: [Socket], _consuming: true, _dumped: false, req: [Circular *1], _eventsCount: 4, responseUrl: 'http://192.168.1.3:8230/notify', redirects: [], [Symbol(shapeMode)]: true, [Symbol(kCapture)]: false, [Symbol(kHeaders)]: [Object], [Symbol(kHeadersCount)]: 18, [Symbol(kTrailers)]: null, [Symbol(kTrailersCount)]: 0 }, aborted: false, timeoutCb: [Function: emitRequestTimeout], upgradeOrConnect: false, parser: null, maxHeadersCount: null, reusedSocket: false, host: '192.168.1.3', protocol: 'http:', _redirectable: Writable { _events: [Object], _writableState: [WritableState], _maxListeners: undefined, _options: [Object], _ended: true, _ending: true, _redirectCount: 0, _redirects: [], _requestBodyLength: 190, _requestBodyBuffers: [], _eventsCount: 3, _onNativeResponse: [Function (anonymous)], _currentRequest: [Circular *1], _currentUrl: 'http://192.168.1.3:8230/notify', _timeout: null, [Symbol(shapeMode)]: true, [Symbol(kCapture)]: false }, [Symbol(shapeMode)]: false, [Symbol(kCapture)]: false, [Symbol(kBytesWritten)]: 0, [Symbol(kNeedDrain)]: false, [Symbol(corked)]: 0, [Symbol(kOutHeaders)]: [Object: null prototype] { accept: [Array], 'content-type': [Array], 'user-agent': [Array], 'content-length': [Array], host: [Array] }, [Symbol(errored)]: null, [Symbol(kHighWaterMark)]: 16384, [Symbol(kRejectNonStandardBodyWrites)]: false, [Symbol(kUniqueHeaders)]: null } } ``` ### Additional Notes Just found out that one has to put in a pushover url and not apprise like it suggests should be as https://api.pushover.net/1/messages.json?user={USER_KEY}&token={TOKEN}&message=New Any chance of the info being updated or proper support for apprise in the future, please?
adam added the bug label 2026-04-25 00:07:10 +02:00
adam closed this issue 2026-04-25 00:07:11 +02:00
adam commented 2026-04-25 00:07:11 +02:00
Author
Owner
Copy Link
Copy Source

@advplyr commented on GitHub (Dec 28, 2024):

I never used pushover before but I setup an account and was able to send a notification to my device without using a pushover URL.

I followed the Apprise wiki: https://github.com/caronc/apprise/wiki/Notify_pushover

image

If you put that pushover URL in the Apprise API Url input in Abs then it is only a coincidence that it worked.
The pushover API is a POST request that accepts a title parameter the same as Apprise API.
body is not listed for the pushover API so I think you'll get a notification with the title only.

@advplyr commented on GitHub (Dec 28, 2024): I never used pushover before but I setup an account and was able to send a notification to my device without using a pushover URL. I followed the Apprise wiki: https://github.com/caronc/apprise/wiki/Notify_pushover ![image](https://github.com/user-attachments/assets/91d2fe96-0896-49b3-9cbc-cbf6b6169d5e) If you put that pushover URL in the `Apprise API Url` input in Abs then it is only a coincidence that it worked. The [pushover API](https://pushover.net/api) is a POST request that accepts a `title` parameter the same as Apprise API. `body` is not listed for the pushover API so I think you'll get a notification with the title only.
adam commented 2026-04-25 00:07:11 +02:00
Author
Owner
Copy Link
Copy Source

@advplyr commented on GitHub (Jan 9, 2025):

Closing as user error

@advplyr commented on GitHub (Jan 9, 2025): Closing as user error
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2442
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?