Closed fwerner13 closed 3 years ago
Thanks for opening your first issue here! Be sure to follow the issue template!
Cannot recreate using the provided docker-compose I'm afraid.
Heard another report in the BookStack discord of this error being thrown with the linuxserver image.
Just tested this myself, using the current v0.30.0-ls105
image, without any proxy in a fresh setup and could not reproduce. Saving a fairly large page and uploading images worked without issue.
Never mind the above, the issue does occur after restarting the containers. On restart the values from the php-local.ini
are read in, which were written in the previous container start-up, which then cause this error since the unexpected MB
in the written php-local.ini
causes application-level middleware to check the post body against a size of 100 bytes instead of 100 MB.
I see there's a pending pull request to solve this: https://github.com/linuxserver/docker-bookstack/pull/65
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
On a fresh install using the provided docker-compose.yml, whenever I post a form (create a new shelf, try to change the default admin password) I get an
Illuminate\Http\Exceptions\PostTooLargeException
.Perhaps this is caused by
https://github.com/linuxserver/docker-bookstack/pull/63/commits/8af8464d49025f14990a892a4a7ed1432e75ebc0#diff-47ffcee93649ec8520ea742cfddc9b9bR66
Expected Behavior
I should be able to post forms.
Current Behavior
When I post any form, the error
Illuminate\Http\Exceptions\PostTooLargeException
appears.Steps to Reproduce
Environment
OS:
CPU architecture: x86_64/arm32/arm64
How docker service was installed:
Command used to create docker container (run/create/compose/screenshot)
Docker logs
The docker logs show nothing, but the nginx logs do:
I'm don't know that much about php.ini configuration, but googling for
post_max_size
the size was always specified as100M
while the recent change used100MB
- don't know if that could be the problem maybe.