mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: Audiobookshelf widget in Homepage is not working #2560
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#2560
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 @joalmeid on GitHub (Feb 9, 2025).
What happened?
The Homepage tool (https://gethomepage.dev), supports multiple widgets for multiple tools. One is Audiobookshelf which is documented here.
By following documentation and setting up the correct services YAML for the Audiobookshelf widget an error is obtained from the Audiobooksheld API.
What did you expect to happen?
The widget being well rendered in the homepage web page, showing information about the libraries.
Steps to reproduce the issue
Audiobookshelf version
v2.19.0
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?
None
Logs
Additional Notes
No response
@Vito0912 commented on GitHub (Feb 9, 2025):
This appears to be more like an error with the tool you're using.
What API endpoint is it trying to contact, and does it work if you connect to it via a browser directly?
@joalmeid commented on GitHub (Feb 9, 2025):
I can ping the Audiobooksheld container (API) from the homepage container:
Then I tried to hit the Audiobookshelf API directly, from homepage container:
NOTE: xxx values validated
@Vito0912 commented on GitHub (Feb 9, 2025):
It is not about pinging. Your second code block is more important.
I am not sure why you provided a token and a user (and whether the user works in abs).
Make sure to use the correct token. Also, try fetching the URL in your browser or with a simple wget command that includes the token parameter nothing more.
@joalmeid commented on GitHub (Feb 9, 2025):
Yes, tried all, actually:
curl -L -k 'http://audiobookshelf:80/api/libraries?token=xxx'
Unauthorized
curl -L -k -u 'xxx:xxx' 'http://audiobookshelf:80/api/libraries?token=xxx'
Unauthorized
If I hit the url http://audiobookshelf:80/api/libraries?token=xxx from my browser, I get a JSON response:
{"libraries":[{"id":"803baf28-9b0c-4eb5-a9fd-7d5e378400b2","name":"Books","folders" (....)
@Vito0912 commented on GitHub (Feb 9, 2025):
Does it work with other things than curl. I am not sure if this is a issue with abs or an misconfiguration as ABS has no way to tell from where you make an connection so it should not block it from that or that place and allow it from a browser
@joalmeid commented on GitHub (Feb 10, 2025):
tried with wget as well:
wget -O - http://audiobookshelf:80/api/libraries?token=xxx
@joalmeid commented on GitHub (Feb 10, 2025):
And did one additional step:
Once I have my user's API token, can't I just provide it on any request (either by querystring or header as per documentation) to the ABS API? Why is login making any difference?
@joalmeid commented on GitHub (Feb 10, 2025):
Issue found.
API token being used was from a user with an account type of root in ABS. That presumably requires the user to be logged in to access the API.
Created another user with account type as user and the homepage widget worked perfectly fine.
Thanks for the support @Vito0912
@averageyogi commented on GitHub (Feb 12, 2025):
Just a further note, homepage does indicate using an Admin user's API token: https://gethomepage.dev/widgets/services/audiobookshelf/, but doesn't specifically list any problem on the documentation page about using Root, User, or Guest tokens.