Hi,
Thanks for reaching out and for the PR to update the docs.
Good to see that you already found a workaround.
The error message “upstream sent too big header while reading response header from upstream” refers to the size of the response headers sent by Nextcloud. Requests to / are usually just a redirect, either to the login page or, if you are already logged in, to the default app.
I’m a bit puzzled how a simple redirect response could grow that large. A good first step to troubleshoot this is to run curl -i ``https://your-nextcloud-instance.com. This prints the response headers and should give us an initial idea. Please make sure to remove your domain name before sharing the output.
If there is a change in Nextcloud 32 that causes unusually large headers, we definitely need to take a closer look.