Meanwhile, i made a “bare-metal” test installation on the same host, where my docker container are running. And the bare-metal nextcloud-instance feels lightning fast - sometimes the load times are below 1s. I’m already thinking about moving back to bare-metal or considering the use of VM’s like proxmox. But somehow i still don’t want to give up docker, because i really like the concept.
Hi I know this is an old post but I have NextCloud running on a very low-end Synology NAS although it is slow it’s not too slow for my purposes, wanted to let you know I sovled some performace issues recently I had LDAP running, I disabled this and it’s like night and day, perhaps test this as well
External S3 access can also make access to Files app very slow when it is set to update every time. In the setting of the s3 integration you can turn that off. It shaved 3-4 seconds off my response time with Files. It is now responding under 1.5 seconds almost consistently (with Redis).
Sup? I’m new to here. I’m HyunSoo Tony Lee from south korea.
Yesterday, I have tried the next cloud container on my ubuntu vm.
It was too slow to use it when it was connected via web interface or ip address.
googling doesn’t help at all, and I dig into it. here is the solution I’ve found.
additional port has to be open to localhost, and the port number is 9982
You know the container environment variables! default is that only port 80 is exposed to localhost port. so you have to add one more, 9982 to localhost:9982
disable the app named “builtin CODE” something.
login to nextcloud web GUI and click on the circled icon on the top right corner and click ‘app’ and find the name CODE something, then ‘disable’ it.
BTW, trusted_domains at the config/config.php is to be modified, so that you can access it remotely.
You may need vi editor, so you have to apt-get update then apt-get install vim first. the IP address or the range at config.php is not the remote client’s ip address or range, it is supposed to be the local ip or ip range where the nextcloud container is running. lookup the interfaces with the command like ifconfig at the container and the container hosting machine.
below is my example. edit it and restart the container.
that’s it. it should work as it is supposed to be.
Meanwhile i have migrated all of my infrastructure to a proxmox server. That means, that my Nextcloud is running now within a LXC container. And guess what? It runs lightning fast! Now, it is really fun to work with it on a daily base (like checking mails via rainloop).
First i changed my old server (Fujitsu Desktop PC) to run with proxmox. After some time i decided to build an entire new server based on a Ryzen 3 3100 and an ITX Mainboard. The main reason for upgrading my server was to have more RAM (now i have 64GB ).
But as i have now more processing power i also use it for other Tasks like ripping and recoding my BluRay collection.
I had a similar problem after moving to a containerized (fpm+nginx version in a podman pod with mariadb, redis and collabora) version of Nextcloud and some Google-foo landed me here which wasn’t really helping my case at all. Frankly most of the info here is a bit misleading. For example why would you need port 9982 exposed?
Hi @mfreudenberg! Thanks for your investigation and solution suggestions. It helped me solve my slow loading problem. In my case disabling External storage support helped a lot! I have some SMB and local (USB drive) devices and now I will to enable it back and debug this problem. Cheers!