You know I have come to really like Linux, but sometimes there is an understatement of things that just drives me nuts. That Collabora page could have had some kind of background image, and a message that contained credit information and links, and something like "Success! If you see this page your Collabora server is functioning properly. You don't need to access this page again. Now go back to your Nextcloud and set up your document server there. Go, make documents! Enjoy! Celebrate!" But no. All I get is a WHITE BLANK page with the word "OK"
Setting up nextcloud in docker
-
- OMV 5.x
- Rowr21
-
-
All I get is a WHITE BLANK page with the word "OK"
maybe you can put somewhere a -vvv to make it more verbose
-
You know I have come to really like Linux, but sometimes there is an understatement of things that just drives me nuts. That Collabora page could have had some kind of background image, and a message that contained credit information and links, and something like "Success! If you see this page your Collabora server is functioning properly. You don't need to access this page again. Now go back to your Nextcloud and set up your document server there. Go, make documents! Enjoy! Celebrate!" But no. All I get is a WHITE BLANK page with the word "OK"
Sounds like a github request to me.. lmao
Honestly, it doesn't bother me given it's use. "OK" tells me all I need to know.. the server is running properly.
I'm a simpleton like that though. -
I’m sorry. I guess I veered this thread a bit off topic. It was fun though.
-
Hi All, sorry to reopen this again.
I've recently been syncing a LOT of stuff to my nextcloud and having issues with files over 1gb or so.
I think this is because of my PHP Memory limit and Upload max size and on other sites I've seen the way to remedy this. However on this setup I'm not sure where to add the commands. Has anyone got any advice on this?
Also if I allow bigger files, will I cause timeout errors too? Find attached a screenshot from the "System" page on the nextcloud web GUI
Thanks for the help,
Rowan
-
having issues with files over 1gb or so.
For the general configuration of the nginx server you can do it in the file /your path of nextcloud config/nginx/nginx.conf
Find the line client_max_body_size
You can set it to client_max_body_size 0; which would be equal to No limit.
For the Nextcloud site configuration it is the file /your path of nextcloud config/nginx/site-confs/default
Look for the client_max_body_syze line and set the size you need.
-
For the general configuration of the nginx server you can do it in the file /your path of nextcloud config/nginx/nginx.conf
Find the line client_max_body_size
You can set it to client_max_body_size 0; which would be equal to No limit.
For the Nextcloud site configuration it is the file /your path of nextcloud config/nginx/site-confs/default
Look for the client_max_body_syze line and set the size you need.
Thanks for this, however I set both of these to client_max_body_size 0;
This still shows: -
Yes. I was expecting something similar. According to Nextcloud documentation
https://docs.nextcloud.com/ser…upload_configuration.html
these parameters need to be configured.
[tt]upload_max_filesize[/tt] and
[tt]post_max_size[/tt]
I had the same problem a long time ago and was able to fix it, but I'm afraid the Nextcloud updates have removed this setting on my Nextcloud. Let me remember how I did it...
-
Yes. I was expecting something similar. According to Nextcloud documentation
https://docs.nextcloud.com/ser…upload_configuration.html
these parameters need to be configured.
[tt]upload_max_filesize[/tt] and
[tt]post_max_size[/tt]
I had the same problem a long time ago and was able to fix it, but I'm afraid the Nextcloud updates have removed this setting on my Nextcloud. Let me remember how I did it...
Thank you, let me know if you can work it out!
-
-
Thanks anyways!
-
-
Look here, this *might* be it (note I've not tested or tried this).
/nextcloud/nginx/site-confs
Just to be on the safe side.. .make a copy of default
cp default default.backup
Then nano default
and you'll see the lines in question (mine is default and shows 512mb... I don't have a large file I can test with at the moment).
After you complete, restart your nextcloud container.
If it screws something up, stop the nextcloud container and delete default and restore the backup
docker stop container_name (or stop it from portainer)
rm default
cp default.backup default
then restart nextcloud
-
Look here, this *might* be it (note I've not tested or tried this).
/nextcloud/nginx/site-confs
Just to be on the safe side.. .make a copy of default
cp default default.backup
Then nano default
and you'll see the lines in question (mine is default and shows 512mb... I don't have a large file I can test with at the moment).
After you complete, restart your nextcloud container.
If it screws something up, stop the nextcloud container and delete default and restore the backup
docker stop container_name (or stop it from portainer)
rm default
cp default.backup default
then restart nextcloud
Hi,
thanks for this, this is what I changed before and it doesn't change the 512 on the web GUI but I will test a larger file upload to see what happens.
Thanks!
-
Looks like it worked! Thanks!
-
Just one more thing.
This works but calling the file default.backup causes errors and breaks nextcloud with the following logs
I removed this and it works fine.
May I also quickly ask... I plan to replace my current small SSD with a few HDDs in a RAID configuration. How can I go about doing this in nextcloud? Can I keep the SSD and just change path to "nextclouddb" or shoud remake the server. Thanks!
/nextcloud/nginx/site-confs
Just to be on the safe side.. .make a copy of default
cp default default.backup
Then nano default
and you'll see the lines in question (mine is default and shows 512mb... I don't have a large file I can test with at the moment).
After you complete, restart your nextcloud container.
If it screws something up, stop the nextcloud container and delete default and restore the backup
docker stop container_name (or stop it from portainer)
rm default
cp default.backup default
then restart nextcloud
-
No no no. default.backup is two different files (in case you screwed up the old one). After you ran
cp default default.backup if you ls, you should have two files there.
If you don't then cp default.backup default
If everything is working ok, you can remove default.backup
rm default.backup
Codeken0201@openmediavault:~$ cd /NAS/AppData/nextcloud/nginx/site-confs/ ken0201@openmediavault:/NAS/AppData/nextcloud/nginx/site-confs$ ls default ken0201@openmediavault:/NAS/AppData/nextcloud/nginx/site-confs$ cp default default.backup ken0201@openmediavault:/NAS/AppData/nextcloud/nginx/site-confs$ ls default default.backup ken0201@openmediavault:/NAS/AppData/nextcloud/nginx/site-confs$ rm default.backup ken0201@openmediavault:/NAS/AppData/nextcloud/nginx/site-confs$ ls default ken0201@openmediavault:/NAS/AppData/nextcloud/nginx/site-confs$
-
No no no. default.backup is two different files (in case you screwed up the old one). After you ran
cp default default.backup if you ls, you should have two files there.
If you don't then cp default.backup default
If everything is working ok, you can remove default.backup
rm default.backup
Codeken0201@openmediavault:~$ cd /NAS/AppData/nextcloud/nginx/site-confs/ ken0201@openmediavault:/NAS/AppData/nextcloud/nginx/site-confs$ ls default ken0201@openmediavault:/NAS/AppData/nextcloud/nginx/site-confs$ cp default default.backup ken0201@openmediavault:/NAS/AppData/nextcloud/nginx/site-confs$ ls default default.backup ken0201@openmediavault:/NAS/AppData/nextcloud/nginx/site-confs$ rm default.backup ken0201@openmediavault:/NAS/AppData/nextcloud/nginx/site-confs$ ls default ken0201@openmediavault:/NAS/AppData/nextcloud/nginx/site-confs$
I did this, but it caused the error. The error only went away when i deleted default.backup
-
Can help tomorrow, still away from home.
Are you running Nextcloud via docker with the linuxserver's container?
I ask this again.
-
I did this, but it caused the error. The error only went away when i deleted default.backup
Hmm, weird. Sorry I didn't think having an additional file there (with a different name) would be an issue.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!