For me the default use of the build-incode Collabora Online Development Edition turns out to be the reason. Tested the docker-compose on different hardware. Slow like hell. Unuseable.
After changing the Collabora Online settings to Use a Demo Server my system is as quick as a direct installation.
Next is to use a Collabora Online instance in my docker-compose.
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.
ātrusted_domainsā ==>
array (
ālocalhostā,
ā172.17.0.ā,
ā192.168.0.ā
ā127.0.0.*ā,
),
thatās it. it should work as it is supposed to be.
when you mount the volume (im assuming you have nginx separate from your nextcloud src)
you must use :z for your nginx container as well as your nextcloud service
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?
Anywho, for those who have long load times and find this thread I strongly suggest checking your loglevel settings in your config.php. If set to 0 youāre basically DDoS-ing yourself. Another thing you could check is your Mariadb config. This might help you getting a better performance out of you db: Nextcloud 21 mit Apache2 (http/2) und PHP-FPM (fast track) ā Carsten Rieger IT-Services
@apinter
Thank you - forgot my loglevel at 0 and was wondering why my nextcloud is pretty slow, your hint pointed in the right direction now it works smoothly with nginx
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!
Sorry people, I have tried everything I found on this forum:
Setting loglevel to 1, 2
Disabling File access control (it was not even installed on my instance)
Disabling External storage
None of the points above helped. My instance is very slow, not only via the WEB interface, but especially when I access it via Android/iPhone apps.
Nextcloud Talk takes up to 15 seconds to load, and this is what I see every time I launch the app:
Image: Nextcloud
I sync my notes (I use Joplin Notes) via WebDAV, it takes up to 25 secs to establish connection before it starts syncing notes.
Nextcloud App also takes time to refresh itself.
Interesting part is: it takes a long time to establish connection (even log in), and when it is connected once (Talk, Joplin Notes, etc.), it seems to work just fine and fast enough. As soon as I close apps/connection, it takes a while to reestablish that connection.
CPU usage is 20/30% when I use Nextcloud.
My server is fast enough, and I host a few websites, forum and video streaming on it. Everything else is superfast.
I had the same error āslow nextcloud frontend in a docker containerā.
As I learned, Docker uses the iptables rules and caused me a server response time of over 3 seconds (in Chrome open the developer tools > network and for each request the āwaiting for server responseā was over 3 seconds).
Depending on the page in the Nextcloud, a request is made several times and then it quickly multiplies into the double-digit second range.
But now to the solution that helped me:
in the ā/etc/systemd/system/multi-user.target.wants/docker.serviceā file after the ācontainerd.sockā append āāiptables=falseā to disable the iptables function in Docker, then donāt forget āsystemctl daemon-reloadā and either restart the docker service āsystemctl restart docker.serviceā or reboot the whole server.
Then my response times were like on a bare metal server around 1 second.