starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Bug]: PayloadTooLargeError #2673

New Issue
Closed
opened 2026-04-25 00:09:29 +02:00 by adam · 6 comments
adam commented 2026-04-25 00:09:29 +02:00
Owner
Copy Link
Copy Source

Originally created by @JBlond on GitHub (Mar 18, 2025).

What happened?

There is an error message on the console when I open a Podcast Library

What did you expect to happen?

No error

Steps to reproduce the issue

  1. Open the App on the phone
  2. Choose a library that is from the typo podcast

Audiobookshelf version

v2.20.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

audiobookshelf  | [2025-03-18 08:20:00.048] INFO: [Database] Db initialized with models: SequelizeMeta, user, library, libraryFolder, book, podcast, podcastEpisode, libraryItem, mediaProgress, series, bookSeries, author, bookAuthor, collection, collectionBook, playlist, playlistMediaItem, device, playbackSession, feed, feedEpisode, setting, customMetadataProvider, mediaItemShare
audiobookshelf  | PayloadTooLargeError: request entity too large
audiobookshelf  |     at readStream (/node_modules/raw-body/index.js:156:17)
audiobookshelf  |     at getRawBody (/node_modules/raw-body/index.js:109:12)
audiobookshelf  |     at read (/node_modules/body-parser/lib/read.js:79:3)
audiobookshelf  |     at jsonParser (/node_modules/body-parser/lib/types/json.js:135:5)
audiobookshelf  |     at Layer.handle [as handle_request] (/node_modules/express/lib/router/layer.js:95:5)
audiobookshelf  |     at trim_prefix (/node_modules/express/lib/router/index.js:328:13)
audiobookshelf  |     at /node_modules/express/lib/router/index.js:286:9
audiobookshelf  |     at Function.process_params (/node_modules/express/lib/router/index.js:346:12)
audiobookshelf  |     at next (/node_modules/express/lib/router/index.js:280:10)
audiobookshelf  |     at urlencodedParser (/node_modules/body-parser/lib/types/urlencoded.js:100:7)

Additional Notes

ABS App 0.9.79-beta

The error is not logged in the daily log. The server does not crash.

Originally created by @JBlond on GitHub (Mar 18, 2025). ### What happened? There is an error message on the console when I open a Podcast Library ### What did you expect to happen? No error ### Steps to reproduce the issue 1. Open the App on the phone 2. Choose a library that is from the typo podcast ### Audiobookshelf version v2.20.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 ```shell audiobookshelf | [2025-03-18 08:20:00.048] INFO: [Database] Db initialized with models: SequelizeMeta, user, library, libraryFolder, book, podcast, podcastEpisode, libraryItem, mediaProgress, series, bookSeries, author, bookAuthor, collection, collectionBook, playlist, playlistMediaItem, device, playbackSession, feed, feedEpisode, setting, customMetadataProvider, mediaItemShare audiobookshelf | PayloadTooLargeError: request entity too large audiobookshelf | at readStream (/node_modules/raw-body/index.js:156:17) audiobookshelf | at getRawBody (/node_modules/raw-body/index.js:109:12) audiobookshelf | at read (/node_modules/body-parser/lib/read.js:79:3) audiobookshelf | at jsonParser (/node_modules/body-parser/lib/types/json.js:135:5) audiobookshelf | at Layer.handle [as handle_request] (/node_modules/express/lib/router/layer.js:95:5) audiobookshelf | at trim_prefix (/node_modules/express/lib/router/index.js:328:13) audiobookshelf | at /node_modules/express/lib/router/index.js:286:9 audiobookshelf | at Function.process_params (/node_modules/express/lib/router/index.js:346:12) audiobookshelf | at next (/node_modules/express/lib/router/index.js:280:10) audiobookshelf | at urlencodedParser (/node_modules/body-parser/lib/types/urlencoded.js:100:7) ``` ### Additional Notes ABS App 0.9.79-beta The error is not logged in the daily log. The server does not crash.
adam added the bug label 2026-04-25 00:09:29 +02:00
adam closed this issue 2026-04-25 00:09:29 +02:00
adam commented 2026-04-25 00:09:30 +02:00
Author
Owner
Copy Link
Copy Source

@advplyr commented on GitHub (Apr 16, 2025):

I'm not able to reproduce this

@advplyr commented on GitHub (Apr 16, 2025): I'm not able to reproduce this
adam commented 2026-04-25 00:09:30 +02:00
Author
Owner
Copy Link
Copy Source

@JBlond commented on GitHub (Apr 26, 2025):

@advplyr I foundout that this only happens if I connect to ABS over nginx proxy manager SSL vhost.

@JBlond commented on GitHub (Apr 26, 2025): @advplyr I foundout that this only happens if I connect to ABS over nginx proxy manager SSL vhost.
adam commented 2026-04-25 00:09:30 +02:00
Author
Owner
Copy Link
Copy Source

@chrisssssy commented on GitHub (May 2, 2025):

@JBlond did you ever resolve this? I also have this issue from time to time with nginx-proxy-manager and "Force SSL" enabled.

@chrisssssy commented on GitHub (May 2, 2025): @JBlond did you ever resolve this? I also have this issue from time to time with nginx-proxy-manager and "Force SSL" enabled.
adam commented 2026-04-25 00:09:31 +02:00
Author
Owner
Copy Link
Copy Source

@JBlond commented on GitHub (May 3, 2025):

@chrisssssy Sadly not. But I can live with it, since the server still run and I can listen to the audiobooks and podcasts.

@JBlond commented on GitHub (May 3, 2025): @chrisssssy Sadly not. But I can live with it, since the server still run and I can listen to the audiobooks and podcasts.
adam commented 2026-04-25 00:09:31 +02:00
Author
Owner
Copy Link
Copy Source

@JBlond commented on GitHub (May 3, 2025):

@chrisssssy I just compared the settings generated by nginx proxy manager and https://github.com/advplyr/audiobookshelf#reverse-proxy-set-up

well, too easy ... in the reverse proxy set up for "NGINX Reverse Proxy" you find

# Prevent 413 Request Entity Too Large error
      # by increasing the maximum allowed size of the client request body
      # For example, set it to 10 GiB
      client_max_body_size                10240M;

so give it a try to add client_max_body_size

if it works it may be added to the readme

@JBlond commented on GitHub (May 3, 2025): @chrisssssy I just compared the settings generated by nginx proxy manager and https://github.com/advplyr/audiobookshelf#reverse-proxy-set-up well, too easy ... in the reverse proxy set up for "NGINX Reverse Proxy" you find ```ini # Prevent 413 Request Entity Too Large error # by increasing the maximum allowed size of the client request body # For example, set it to 10 GiB client_max_body_size 10240M; ```` so give it a try to add client_max_body_size if it works it may be added to the readme
adam commented 2026-04-25 00:09:32 +02:00
Author
Owner
Copy Link
Copy Source

@chrisssssy commented on GitHub (May 3, 2025):

Thanks for the hint, it really does sound like it could work. Even though i didnt upload any large files when the error appeared.

@chrisssssy commented on GitHub (May 3, 2025): Thanks for the hint, it really does sound like it could work. Even though i didnt upload any large files when the error appeared.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2673
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?