[Bug]: Matching books using Audible.com showing "No Result" #2239

Closed
opened 2026-04-25 00:05:20 +02:00 by adam · 23 comments
Owner

Originally created by @seannymurrs on GitHub (Sep 6, 2024).

What happened?

Starting yesterday afternoon, I'm getting "No Results" every time I try to match a book using Audible.com. I've tried using the ASIN or the Title, and I get the same outcome. Below are the logs that I get when I try to match using the ASIN B0CKM5YQX8.

2024-09-06 18:39:32.115 ERROR [Audible] ASIN search error AggregateError 2024-09-06 18:39:33.249 ERROR [Audible] query search error AggregateError 2024-09-06 18:39:33.250 INFO [Audnexus] Searching for author "https://api.audnex.us/authors?name=b0ckm5yqx8" 2024-09-06 18:39:33.763 ERROR [Audnexus] Author ASIN request failed for b0ckm5yqx8 AggregateError

One thing that was pointed out to me when I asked about this in the Discord is the fact that the logs show that the ASIN is in all lowercase even though I enter it as all caps when searching. They pointed out that following the Audnexus url with the ASIN in all caps does provide a result, but the URL in the logs doesn't (presumably because it's in lowercase).

What did you expect to happen?

I expected the book to be matched to the correct book via its ASIN.

Steps to reproduce the issue

  1. Search for book using ASIN.
  2. See "No Results".

Audiobookshelf version

v2.13.3

How are you running audiobookshelf?

Docker

What OS is your Audiobookshelf server hosted from?

macOS

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

None

Logs

2024-09-06 18:39:32.115
ERROR
[Audible] ASIN search error AggregateError
2024-09-06 18:39:33.249
ERROR
[Audible] query search error AggregateError
2024-09-06 18:39:33.250
INFO
[Audnexus] Searching for author "https://api.audnex.us/authors?name=b0ckm5yqx8"
2024-09-06 18:39:33.763
ERROR
[Audnexus] Author ASIN request failed for b0ckm5yqx8 AggregateError

Additional Notes

I've tried the ASIN for other books as well as searching by Title and Author. I get "No Results" every time.

Originally created by @seannymurrs on GitHub (Sep 6, 2024). ### What happened? Starting yesterday afternoon, I'm getting "No Results" every time I try to match a book using Audible.com. I've tried using the ASIN or the Title, and I get the same outcome. Below are the logs that I get when I try to match using the ASIN B0CKM5YQX8. `2024-09-06 18:39:32.115 ERROR [Audible] ASIN search error AggregateError 2024-09-06 18:39:33.249 ERROR [Audible] query search error AggregateError 2024-09-06 18:39:33.250 INFO [Audnexus] Searching for author "https://api.audnex.us/authors?name=b0ckm5yqx8" 2024-09-06 18:39:33.763 ERROR [Audnexus] Author ASIN request failed for b0ckm5yqx8 AggregateError` One thing that was pointed out to me when I asked about this in the Discord is the fact that the logs show that the ASIN is in all lowercase even though I enter it as all caps when searching. They pointed out that following the Audnexus url with the ASIN in all caps does provide a result, but the URL in the logs doesn't (presumably because it's in lowercase). ### What did you expect to happen? I expected the book to be matched to the correct book via its ASIN. ### Steps to reproduce the issue 1. Search for book using ASIN. 2. See "No Results". ### Audiobookshelf version v2.13.3 ### How are you running audiobookshelf? Docker ### What OS is your Audiobookshelf server hosted from? macOS ### If the issue is being seen in the UI, what browsers are you seeing the problem on? None ### Logs ```shell 2024-09-06 18:39:32.115 ERROR [Audible] ASIN search error AggregateError 2024-09-06 18:39:33.249 ERROR [Audible] query search error AggregateError 2024-09-06 18:39:33.250 INFO [Audnexus] Searching for author "https://api.audnex.us/authors?name=b0ckm5yqx8" 2024-09-06 18:39:33.763 ERROR [Audnexus] Author ASIN request failed for b0ckm5yqx8 AggregateError ``` ### Additional Notes I've tried the ASIN for other books as well as searching by Title and Author. I get "No Results" every time.
adam added the bug label 2026-04-25 00:05:20 +02:00
adam closed this issue 2026-04-25 00:05:20 +02:00
Author
Owner

@hologram75 commented on GitHub (Sep 6, 2024):

I have the exact same issue (Docker Windows v2.13.3).

@hologram75 commented on GitHub (Sep 6, 2024): I have the exact same issue (Docker Windows v2.13.3).
Author
Owner

@advplyr commented on GitHub (Sep 6, 2024):

Audnexus API website is down

@advplyr commented on GitHub (Sep 6, 2024): Audnexus API website is down
Author
Owner

@CoolJoe72 commented on GitHub (Sep 7, 2024):

Domain Audnex.us Expires on 2024-09-06. Hopefully it gets renewed.

add
104.21.44.87 audnex.us api.audnex.us
to /etc/hosts for temp fix.

@CoolJoe72 commented on GitHub (Sep 7, 2024): Domain Audnex.us Expires on 2024-09-06. Hopefully it gets renewed. add 104.21.44.87 audnex.us api.audnex.us to /etc/hosts for temp fix.
Author
Owner

@valdearg commented on GitHub (Sep 7, 2024):

docker compose people can also use

    extra_hosts:
     - "audnex.us:104.21.44.87"
     - "api.audnex.us:104.21.44.87"
@valdearg commented on GitHub (Sep 7, 2024): docker compose people can also use ``` extra_hosts: - "audnex.us:104.21.44.87" - "api.audnex.us:104.21.44.87" ```
Author
Owner

@Abateman121 commented on GitHub (Sep 7, 2024):

docker compose people can also use

    extra_hosts:
     - "audnex.us:104.21.44.87"
     - "api.audnex.us:104.21.44.87"

You are a hero good person!

@Abateman121 commented on GitHub (Sep 7, 2024): > docker compose people can also use > > ``` > extra_hosts: > - "audnex.us:104.21.44.87" > - "api.audnex.us:104.21.44.87" > ``` You are a hero good person!
Author
Owner

@catduckgnaf commented on GitHub (Sep 7, 2024):

And legend among men

@catduckgnaf commented on GitHub (Sep 7, 2024): And legend among men
Author
Owner

@petenun commented on GitHub (Sep 7, 2024):

Thank you. I added those entries to my hosts file (Windows) and it's working nicely. The question is, what happened to the audnex.us domain registration in DNS. It's just gone.

@petenun commented on GitHub (Sep 7, 2024): Thank you. I added those entries to my hosts file (Windows) and it's working nicely. The question is, what happened to the audnex.us domain registration in DNS. It's just gone.
Author
Owner

@stibbons1990 commented on GitHub (Sep 7, 2024):

Kubernetes people can use

      hostAliases:
      - ip: "104.21.44.87"
        hostnames:
        - "api.audnex.us"
        - "audnex.us"
      containers:
        - image: ghcr.io/advplyr/audiobookshelf:latest
      ...
@stibbons1990 commented on GitHub (Sep 7, 2024): Kubernetes people can use ```yaml hostAliases: - ip: "104.21.44.87" hostnames: - "api.audnex.us" - "audnex.us" containers: - image: ghcr.io/advplyr/audiobookshelf:latest ... ```
Author
Owner

@sebinum commented on GitHub (Sep 7, 2024):

If you're on Unraid:

  1. Edit the container
  2. Switch from Basic View to Advanced View (can be toggled on the top right)
  3. Add the following into the Extra Parameters field and restart:
--add-host=audnex.us:104.21.44.87 --add-host=api.audnex.us:104.21.44.87
@sebinum commented on GitHub (Sep 7, 2024): If you're on Unraid: 1. Edit the container 2. Switch from **Basic View** to **Advanced View** (can be toggled on the top right) 3. Add the following into the **Extra Parameters** field and restart: ``` --add-host=audnex.us:104.21.44.87 --add-host=api.audnex.us:104.21.44.87 ```
Author
Owner

@xcy7e commented on GitHub (Sep 7, 2024):

If you use the linux package version, do this:

sudo echo "104.21.44.87 api.audnex.us" | sudo tee -a  /etc/hosts
sudo echo "104.21.44.87 audnex.us" | sudo tee -a  /etc/hosts

or add it manually to /etc/hosts:

# ... 

104.21.44.87 api.audnex.us
104.21.44.87 audnex.us
@xcy7e commented on GitHub (Sep 7, 2024): If you use the linux package version, do this: ```bash sudo echo "104.21.44.87 api.audnex.us" | sudo tee -a /etc/hosts sudo echo "104.21.44.87 audnex.us" | sudo tee -a /etc/hosts ``` or add it manually to `/etc/hosts`: ```bash # ... 104.21.44.87 api.audnex.us 104.21.44.87 audnex.us ```
Author
Owner

@advplyr commented on GitHub (Sep 7, 2024):

Audnexus is back up

@advplyr commented on GitHub (Sep 7, 2024): Audnexus is back up
Author
Owner

@ZLoth commented on GitHub (Sep 7, 2024):

Hopefully, this won't occur again next September. Per https://github.com/laxamentumtech/audnexus/issues/808: "Yes, the auto renew failed. I've manually fixed it. Should be back soon."

@ZLoth commented on GitHub (Sep 7, 2024): Hopefully, this won't occur again next September. Per https://github.com/laxamentumtech/audnexus/issues/808: "Yes, the auto renew failed. I've manually fixed it. Should be back soon."
Author
Owner

@seannymurrs commented on GitHub (Sep 8, 2024):

I'm still seeing the same issue I originally was.

@seannymurrs commented on GitHub (Sep 8, 2024): I'm still seeing the same issue I originally was.
Author
Owner

@MaxPowers1337 commented on GitHub (Sep 9, 2024):

Jeah, same probleme here, too.

For me it seems that the audnex api is not getting the correct values from audible itself.

ive created an issue there.

@MaxPowers1337 commented on GitHub (Sep 9, 2024): Jeah, same probleme here, too. For me it seems that the audnex api is not getting the correct values from audible itself. ive created an [issue there.](https://github.com/djdembeck/Audnexus.bundle/issues/122)
Author
Owner

@xcy7e commented on GitHub (Sep 9, 2024):

Jeah, same probleme here, too.

For me it seems that the audnex api is not getting the correct values from audible itself.

ive created an issue there.

Hm, can't reproduce - works fine here, if I avoid the DNS by mapping the APIs IP directly to the domains using the hosts file.

Even direct search for ASIN works.

Anyways this is no audiobookshelf-related issue and should not be reported here, hence this issue is already closed.

@xcy7e commented on GitHub (Sep 9, 2024): > Jeah, same probleme here, too. > > For me it seems that the audnex api is not getting the correct values from audible itself. > > ive created an [issue there.](https://github.com/djdembeck/Audnexus.bundle/issues/122) Hm, can't reproduce - works fine here, if I avoid the DNS by mapping the APIs IP directly to the domains using the `hosts` file. Even direct search for `ASIN` works. Anyways this is no audiobookshelf-related issue and should not be reported here, hence this issue is already closed.
Author
Owner

@MaxPowers1337 commented on GitHub (Sep 9, 2024):

Jeah, same probleme here, too.
For me it seems that the audnex api is not getting the correct values from audible itself.
ive created an issue there.

Hm, can't reproduce - works fine here, if I avoid the DNS by mapping the APIs IP directly to the domains using the hosts file.

Even direct search for ASIN works.

Anyways this is no audiobookshelf-related issue and should not be reported here, hence this issue is already closed.

The url works for you?

https://api.audnex.us/books/B0DFHJFZQH?region=de

@MaxPowers1337 commented on GitHub (Sep 9, 2024): > > Jeah, same probleme here, too. > > For me it seems that the audnex api is not getting the correct values from audible itself. > > ive created an [issue there.](https://github.com/djdembeck/Audnexus.bundle/issues/122) > > Hm, can't reproduce - works fine here, if I avoid the DNS by mapping the APIs IP directly to the domains using the `hosts` file. > > Even direct search for `ASIN` works. > > Anyways this is no audiobookshelf-related issue and should not be reported here, hence this issue is already closed. The url works for you? https://api.audnex.us/books/B0DFHJFZQH?region=de
Author
Owner

@xcy7e commented on GitHub (Sep 9, 2024):

Everything within audiobookshelf works for me, relating this context.

@xcy7e commented on GitHub (Sep 9, 2024): Everything within audiobookshelf works for me, relating this context.
Author
Owner

@MaxPowers1337 commented on GitHub (Sep 9, 2024):

Could you kindly check if the above ASIN works for you, too? Audiobookshelf is not able to match this item and i keep getting this error :

    data: {
      statusCode: 500,
      error: 'Internal Server Error',
      message: "Required key 'asin' does not exist in Audible API response for ASIN B0DFHJFZQH"
    }

I strongly suspect that audnexus has a problem with this specific item and that the error is not on audiobookshelf's side.

@MaxPowers1337 commented on GitHub (Sep 9, 2024): Could you kindly check if the above ASIN works for you, too? Audiobookshelf is not able to match this item and i keep getting this error : ``` data: { statusCode: 500, error: 'Internal Server Error', message: "Required key 'asin' does not exist in Audible API response for ASIN B0DFHJFZQH" } ``` I strongly suspect that audnexus has a problem with this specific item and that the error is not on audiobookshelf's side.
Author
Owner

@petenun commented on GitHub (Sep 9, 2024):

I just looked in DNS and it looks like audnex.us has a split domain, pointing to multiple IP addresses. Since this works for some people but not others, it seems feasible that one of the IP addresses could be broken. The 104.21.44.87 address seems to work for me, so you may want to keep using the modified host file until a fix is in place.

NSLOOKUP

audnex.us
Server: dns.google
Address: 8.8.8.8

Non-authoritative answer:
Name: audnex.us
Addresses: 2606:4700:3030::ac43:c637
2606:4700:3037::6815:2c57
104.21.44.87
172.67.198.55

@petenun commented on GitHub (Sep 9, 2024): I just looked in DNS and it looks like audnex.us has a split domain, pointing to multiple IP addresses. Since this works for some people but not others, it seems feasible that one of the IP addresses could be broken. The 104.21.44.87 address seems to work for me, so you may want to keep using the modified host file until a fix is in place. NSLOOKUP > audnex.us Server: dns.google Address: 8.8.8.8 Non-authoritative answer: Name: audnex.us Addresses: 2606:4700:3030::ac43:c637 2606:4700:3037::6815:2c57 104.21.44.87 172.67.198.55
Author
Owner

@wesf99 commented on GitHub (Oct 6, 2024):

I have been getting this error on my synology nas docker installation for the past few days.

I have added:
104.21.44.87 api.audnex.us
104.21.44.87 audnex.us
to my /etc/hosts

This does not seem to have helped me. Does anyone have any other suggestions to help me to get this working please.

@wesf99 commented on GitHub (Oct 6, 2024): I have been getting this error on my synology nas docker installation for the past few days. I have added: 104.21.44.87 api.audnex.us 104.21.44.87 audnex.us to my /etc/hosts This does not seem to have helped me. Does anyone have any other suggestions to help me to get this working please.
Author
Owner

@nichwall commented on GitHub (Oct 6, 2024):

I have been getting this error on my synology nas docker installation for the past few days.

I have added:
104.21.44.87 api.audnex.us
104.21.44.87 audnex.us
to my /etc/hosts

Are you getting the same error as mentioned in the original message, and have you checked that you get a response when manually querying api.audnex.us outside of ABS?

@nichwall commented on GitHub (Oct 6, 2024): > I have been getting this error on my synology nas docker installation for the past few days. > > I have added: > 104.21.44.87 api.audnex.us > 104.21.44.87 audnex.us > to my /etc/hosts Are you getting the same error as mentioned in the original message, and have you checked that you get a response when manually querying api.audnex.us outside of ABS?
Author
Owner

@wesf99 commented on GitHub (Oct 7, 2024):

I have been getting this error on my synology nas docker installation for the past few days.
I have added:
104.21.44.87 api.audnex.us
104.21.44.87 audnex.us
to my /etc/hosts

Are you getting the same error as mentioned in the original message, and have you checked that you get a response when manually querying api.audnex.us outside of ABS?

Thank you for your reply. Looking more closely, I am getting a different error:

Error: getaddrinfo EAI_AGAIN api.audnex.us

I was able to get a response from api.audnex.us outside of ABS.

I realized I had recently installed another docker compose app and had to add a firewall rule on my Synology to allow the new docker IP address. I added a new firewall rule to allow the ABS IP network and it fixed the problem. I'm not sure what happened as ABS had been working for me for over 12 to 18 months without needing a rule!

Thanks again for getting me to look more closely.

@wesf99 commented on GitHub (Oct 7, 2024): > > I have been getting this error on my synology nas docker installation for the past few days. > > I have added: > > 104.21.44.87 api.audnex.us > > 104.21.44.87 audnex.us > > to my /etc/hosts > > Are you getting the same error as mentioned in the original message, and have you checked that you get a response when manually querying api.audnex.us outside of ABS? Thank you for your reply. Looking more closely, I am getting a different error: Error: getaddrinfo EAI_AGAIN api.audnex.us I was able to get a response from api.audnex.us outside of ABS. I realized I had recently installed another docker compose app and had to add a firewall rule on my Synology to allow the new docker IP address. I added a new firewall rule to allow the ABS IP network and it fixed the problem. I'm not sure what happened as ABS had been working for me for over 12 to 18 months without needing a rule! Thanks again for getting me to look more closely.
Author
Owner

@SeMuh83 commented on GitHub (Jan 6, 2025):

Is this error still/again present?

I cannot retrieve any data via audible.de.
No matter whether I search with the ASIN, or the title, author, I only get the message that nothing was found for every audiobook and author

@SeMuh83 commented on GitHub (Jan 6, 2025): Is this error still/again present? I cannot retrieve any data via audible.de. No matter whether I search with the ASIN, or the title, author, I only get the message that nothing was found for every audiobook and author
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2239