mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: Failed to get podcast feed #2568
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#2568
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 @gadinbot on GitHub (Feb 12, 2025).
What happened?
when trying to add certain podcasts I get the "Failed to get podcast feed" error. I can confirm they are not blocked on my end and can access the xml feeds with a browser.
In the case of Midst, this was working up until October last year.
examples of podcasts that don't work
Midst
Critical Role
The Party Room
Democracy Sausage with Mark Kenny
What did you expect to happen?
I expect the popup to appear that allows me to edit the metadata and confirm the save.
Steps to reproduce the issue
Audiobookshelf version
v2.19.1
How are you running audiobookshelf?
Debian/PPA
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?
None
Logs
Additional Notes
No response
@nichwall commented on GitHub (Feb 12, 2025):
Is there anything in the crash logs?
@gadinbot commented on GitHub (Feb 12, 2025):
This is all i have in the crash log, i replicated the issue and checked the log but nothing changed or was added.
"timestamp":"2025-02-12 12:06:02.703","source":" at process. (/snapshot/audiobookshelf/server/Server.js)","message":"[Server] Unhandled rejection: Error\n at Database. (/snapshot/audiobookshelf/node_modules/seq>
{"timestamp":"2025-02-12 12:06:04.085","source":" at process. (/snapshot/audiobookshelf/server/Server.js)","message":"[Server] Unhandled rejection: Error\n at Database. (/snapshot/audiobookshelf/node_modules/seq>
{"timestamp":"2025-02-12 12:06:06.984","source":" at process. (/snapshot/audiobookshelf/server/Server.js)","message":"[Server] Unhandled rejection: Error\n at Database. (/snapshot/audiobookshelf/node_modules/seq>
{"timestamp":"2025-02-12 12:06:08.588","source":" at process. (/snapshot/audiobookshelf/server/Server.js)","message":"[Server] Unhandled rejection: Error\n at Database. (/snapshot/audiobookshelf/node_modules/seq>
{"timestamp":"2025-02-12 12:06:12.369","source":" at process. (/snapshot/audiobookshelf/server/Server.js)","message":"[Server] Unhandled rejection: Error\n at Database. (/snapshot/audiobookshelf/node_modules/seq>
{"timestamp":"2025-02-12 12:06:13.936","source":" at process. (/snapshot/audiobookshelf/server/Server.js)","message":"[Server] Unhandled rejection: Error\n at Database. (/snapshot/audiobookshelf/node_modules/seq>
{"timestamp":"2025-02-12 12:06:18.844","source":" at process. (/snapshot/audiobookshelf/server/Server.js)","message":"[Server] Unhandled rejection: Error\n at Database. (/snapshot/audiobookshelf/node_modules/seq>
{"timestamp":"2025-02-12 12:07:07.668","source":" at process. (/snapshot/audiobookshelf/server/Server.js)","message":"[Server] Unhandled rejection: Error\n at Database. (/snapshot/audiobookshelf/node_modules/seq>
{"timestamp":"2025-02-12 12:07:08.819","source":" at process. (/snapshot/audiobookshelf/server/Server.js)","message":"[Server] Unhandled rejection: Error\n at Database. (/snapshot/audiobookshelf/node_modules/seq>
{"timestamp":"2025-02-12 12:11:00.065","source":" at process. (/snapshot/audiobookshelf/server/Server.js)","message":"[Server] Unhandled rejection: Error\n at Database. (/snapshot/audiobookshelf/node_modules/seq>
@nichwall commented on GitHub (Feb 12, 2025):
There is a crash in 2.19.1 (more details in https://github.com/advplyr/audiobookshelf/issues/3966) that is fixed in 2.19.2. Can you try again after updating to see if this is the same issue?
@gadinbot commented on GitHub (Feb 12, 2025):
I have upgraded to 2.19.2 and still getting the same issue and no change in the crash log.
@gadinbot commented on GitHub (Feb 18, 2025):
just tested on 2.19.3 getting the below in the logs, and nothing in the crash report. I'm able to go to the below URL and play the podcast directly in a web browser to rule out issues with DNS or my router.
2025-02-18 12:30:50.575
DEBUG
[podcastUtils] getPodcastFeed for "https://feeds.acast.com/public/shows/2c2eab86-45bd-53ae-b72f-f474f0e08bc9"
2025-02-18 12:30:50.882
FATAL
[Server] Uncaught exception origin: uncaughtException, error: Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues at assert (node:internal/assert:14:11) at internalConnectMultiple (node:net:1118:3) at defaultTriggerAsyncIdScope (node:internal/async_hooks:464:18) at GetAddrInfoReqWrap.emitLookup [as callback] (node:net:1510:7) at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:130:8) { code: 'ERR_INTERNAL_ASSERTION' }
@Piggeldi2013 commented on GitHub (Feb 23, 2025):
Hi,
seeing the exact same thing, even on trying to add a totally new podcast.
I'm on 2.19.4 Docker version.
As I'm updating regularely, I can't say when that started.
Just found out today that searching for new episodes (using the magnifying glass from podcast overview) nor adding new podcasts work.
I'm unsure if the normal scheduled downloads work right now - even if I can't see any error messages when forcing a manual update.
All podcast feeds can be downloaded when using command line in the container using curl - so network related stuff should not be the issue here.
Also to mention, that happens on trying to use / download from different podcast providers - so the issue seems not be the feed here.
Thanks for the nice work, btw!
@Piggeldi2013 commented on GitHub (Feb 25, 2025):
Got it fixed for me.
Even if curl / wget was able to download the feed in the container, I've found that I needed to add dns settings at the docker compose file.
Seems that this changed something in the node network configuration, which wasn't there before.
Now, all seems to be working again.
I'd also suggest to check if IPv6 is switched off / not used for node - there also seem some problems to be related, as far as I could see.
Hope this helps somehow.
Best,
Piggeldi
@gadinbot commented on GitHub (Feb 28, 2025):
Glad it worked for you, I'm running this in an LXC container in Proxmox. i did test and was able download using wget directly in to the container.
I updated the LXC DNS manually set it to my internal DNS and 1.1.1.1, and sadly I'm still getting the same error.
This one is doing my head in.
@advplyr commented on GitHub (Apr 5, 2025):
Did you resolve this?
@gadinbot commented on GitHub (Apr 5, 2025):
Sadly no, it's still ongoing for me. Happy if you have any guidance.
@Philipp0205 commented on GitHub (May 3, 2025):
Did somebody find a fix?
@Phantomwise commented on GitHub (Aug 30, 2025):
Might be worth a try to use alternate RSS links for those podcasts to try to bypass the problem?
Like
Midst: https://feeds.megaphone.fm/midst
Critical Role: https://feeds.simplecast.com/LXz4Q9rJ
Democracy Sausage with Mark Kenny: https://feeds.acast.com/public/shows/2c2eab86-45bd-53ae-b72f-f474f0e08bc9
etc
@cruux13 commented on GitHub (Aug 31, 2025):
I might have found the (workaroundish) solution for these kind of errors in a forum from an affected podcast.
https://talk.lagedernation.org/t/podcast-feed-kaputt/27017/5
It seems like you need to troubleshoot the feed with nslookup and if there are multiple dns answers just add some static entries to your docker configuration. Managed to get the podcast I mentioned above working again by adding the following hosts:
extra_hosts:
- "cdn.kicks-apps.com:139.162.176.235"
- "feeds.lagedernation.org:139.162.176.235"