1000M might in facts be too much for your setup, and perhaps even broadly for any api call.
Try to set client_max_body_size 1M;
Thank you again!
Thank you .. yes 1000M was excessive however I’d tried 1, 10 , 100 at that point ..
Ran sudo docker compose stop
Edited ssh://casey/home/ubuntu/docker/peertube/docker-volume/nginx/peertube
Docler compose up -d
Same issue.
Anything else I can try?
We could run a browser with another profile to be sure nothing is related to browser.
We could see http requests from browser in debug ( F11 on firefox ) and see how look like the request that fails with 413.
Thank you again ..
Setup new admin test
Logged in to new browser Firefox
F11 seems to go full screen vs any debug mode that I could find.
Changed video settings fine.
Tried to change anything in the settings tab .. same error ..
I’ve uploaded a screen recording to Peer Tube Error Saving Settings - PeerTube
1 « J'aime »
Well that was F12 not F11 
Was using CHrome .. here is Debug from Firefox
</L https://caseyandbros.walker.id/client/en-US/polyfills-PE3IR76Z.js:1
Storing component videos-list{} to reuse later. [chunk-VGQB5O46.js:16:165271](https ://caseyandbros.walker.id/client/en-US/chunk-VGQB5O46.js)
Reusing component videos-list{}. 2 [chunk-VGQB5O46.js:16:165271](https ://caseyandbros.walker.id/client/en-US/chunk-VGQB5O46.js)
Storing component videos-list{} to reuse later. [chunk-VGQB5O46.js:16:165271](https ://caseyandbros.walker.id/client/en-US/chunk-VGQB5O46.js)
XHRPUThttps://caseyandbros.walker.id/api/v1/config/custom[HTTP/2 413 6ms]
Error: 413 Request Entity Too Large
413 Request Entity Too Large
nginx/1.29.2 [chunk-VGQB5O46.js:16:165497](https:// caseyandbros.walker.id/client/en-US/chunk-VGQB5O46.js)
##Space added to URLS as won’t allow post with 2 URLs
That won’t be easy 
hint : for avoiding to fight with url due to discourse formatting, selet text block and use ‘</>’ ( or Crtl-E ) to have it as text.
(you might want to reedit your post
Very much appreciate your support .. and did hope we could find a solution in case anyone else saw the same error.
Sadly I’m a medic and a bit maxed out just now .. will try anything suggested but suspect I’m on my way to a fresh server build and re install.
@pwwuk so let’s test the default peertube nginx configuration again
to do within in parent directory of docker-volume. this is directory where docker-compose is too, in your case docker/peertube of ubuntu home.
sudo docker compose down
curl https://raw.githubusercontent.com/Chocobozzz/PeerTube/master/support/nginx/peertube > docker-volume/nginx/peertube
sudo docker compose up
ubuntu@Casey:~/docker/peertube$ curl https://raw.githubusercontent.com/Chocobozzz/PeerTube/master/support/nginx/peertube > docker-volume/nginx/peertube
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 9539 100 9539 0 0 58788 0 --:--:-- --:--:-- --:--:-- 58882Wowza ..
Not sure what happened .. did a shut down last night .. back up this morning (with a view I’d have to do a rebuild) .. same error ..
Just wan the curl command above ..
docker up
Problem FIXED !!! Would love to know how / why .. but am extremely grateful
@pwwuk during docker up, were some images updated ? this peertube-webserver is peculiar and is rebuild from time to time …
@pwwuk i’m happy to have been helpful, i’m not a medic i can’t save lives, but i do what i can in my free software field
Don’t think so .. I updated some images after it was up as part of testing
Super appreciate your help