mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: #962
Assignees
adam (Adam Melkus)
Clear assignees
adam (Adam Melkus)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/audiobookshelf#962
Reference in New Issue
Block a user
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?
Originally created by @ghost on GitHub (Feb 17, 2023).
Describe the issue
Issue with notify. I tried a bunch of combos on Apprise URL(s). The one that works and will send me notifications is
apprise://192.168.1.10:14396/apprise?tags=allbut it also gives me an error. If Max failed attempts is set to a low number it will turn off all my notifications.The error I get in logs
'[NotificationManager] sendNotification: onPodcastEpisodeDownloaded/noti_8f7uja15lvfuc413u6 error= AxiosError: Request failed with status code 424`
Apprise API Url is set to
http://192.168.1.10:14396/notifyURL set up in my notification for Apprise URL(s) isapprise://192.168.1.10:14396/apprise?tags=allApprise-API and Audiobookshelf both running on docker.
Steps to reproduce the issue
http://192.168.1.10:14396/notifyapprise://192.168.1.10:14396/apprise?tags=all[NotificationManager] sendNotification: onPodcastEpisodeDownloaded/noti_8f7uja15lvfuc413u6 error= AxiosError: Request failed with status code 424Audiobookshelf version
v2.2.15
How are you running audiobookshelf?
Docker
@advplyr commented on GitHub (Feb 17, 2023):
This appears to be an issue with your server making requests to get a podcast RSS feed and not an issue with apprise.
I don't know what would cause that 424 status code. Are there specific RSS feeds that are causing this? Are you able to download podcast episodes normally?
@ghost commented on GitHub (Feb 17, 2023):
is the
apprise://192.168.1.10:14396/apprise?tags=allthe correct Apprise URL(s) for the onPodcastEpisodeDownloaded setting? I only have a small handful of podcasts, and they are all downloading correctly. The two that are active are NPR up first and stuff you should know. Both are giving me the 424 status code when the notification fires off.I will remove all my podcasts and test them one by one and see if I still get errors. I am getting my notifications on podcast downloads
@advplyr commented on GitHub (Feb 17, 2023):
Oh I see, it does look like that error is from the apprise request and not the podcast requests.
I'm not sure if that is a valid apprise url. First you would make sure the URL to your apprise server is correct
Then when setting up a notification an example apprise URL might be
mailto://<your gmail username>:blrvaurfctadvtdt@gmail.comFor setting up a mail apprise url see the docs https://github.com/caronc/apprise/wiki/Notify_email#using-built-in-email-services
Note for Gmail you might need to follow the instructions in that doc to create a password if you have 2-factor auth setup.
@advplyr commented on GitHub (Feb 17, 2023):
I see you used this apprise url https://github.com/caronc/apprise/wiki/Notify_apprise_api
I'm not sure what that is for. I just use the mail apprise urls.
@ghost commented on GitHub (Feb 17, 2023):
I'm using bark server to send notifications to my phone.
Here are the settings in audiobook shelf and a screenshot of apprise api telling me what setting to use. The only one that worked with audioshelfbook was the apprise:// url
Even though Audiobookshelf is saying it failed, they are going through to my phone just fine.
There is a bark:// url at the bottom of the apprise api page I am going to try and see if that works with no errors
@ghost commented on GitHub (Feb 17, 2023):
Using the bark:// URL in audiobookshelf onPodcastEpisodeDownloaded api URL is working with zero errors. From what I am gathering the
apprise://192.168.1.10:14396/apprise?tags=allwill send out notifications to all you have set up in Apprise API if you are using more than one.@advplyr commented on GitHub (Feb 17, 2023):
Okay, I'm not sure about that. I don't think this is anything to do with Abs since we are just sending a request to your Apprise server with the URL you provided.
Maybe put in a bug report with Apprise?
If you think there is a specific bug with Abs though let me know.