Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Missing subpath in ebook url #3865

Closed
baal000 opened this issue Jan 20, 2025 · 0 comments · Fixed by #3864
Closed

[Bug]: Missing subpath in ebook url #3865

baal000 opened this issue Jan 20, 2025 · 0 comments · Fixed by #3864
Labels
awaiting release Issue is resolved and will be in the next release bug Something isn't working

Comments

@baal000
Copy link

baal000 commented Jan 20, 2025

What happened?

If I read an ebook in the browser it loads the ebook with the wrong url into the browser:
http://192.168.178.78:13378/api/items/16ae1df2-f091-4bc4-be32-5b52dcc33ea5/ebook instead of http://192.168.178.78:13378/audiobookshelf/api/items/16ae1df2-f091-4bc4-be32-5b52dcc33ea5/ebook

This leads to issues if you are using reverse proxies like nginx as the url for the ebook will not be available then.

What did you expect to happen?

It uses http://192.168.178.78:13378/audiobookshelf/api/items/16ae1df2-f091-4bc4-be32-5b52dcc33ea5/ebook to load the ebook into the browser

Steps to reproduce the issue

  1. open browser to audiobookshelf
  2. read ebook and check network traffic

Audiobookshelf version

v2.18.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?

Firefox

Logs

Additional Notes

No response

@baal000 baal000 added the bug Something isn't working label Jan 20, 2025
@advplyr advplyr added the awaiting release Issue is resolved and will be in the next release label Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting release Issue is resolved and will be in the next release bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants