I came here looking for help. I have Nextcloud AIO installed on 2 different servers. Pretty basic setup, nothing fancy. Before switching to AIO, I used regular docker install and was pretty satisfied, except trying to put multiple things together (+collabora, etc.) and AIO just made more sense.

However my issue is - I set it up just fine, all works. But often, when I browse into NC (to upload/download/edit some files via web mostly), NC would just stutter - requests eventually ends with 504 Timeout error. That lasts for couple of minutes (3-5?) and then all comes back to life. Almost like there is some bottleneck or something that NC just can't digest and stutters.

I tried checking obvious things - found nothing specific in apache logs, master container logs or NC logs at all. 

 

I am using Nginx proxy manager - if that matters.

I know this is not much to start with, but I am hoping that someone encountered something similar and would be able to advise.

 

Edit: for instance just now (3:21 PM) - i have deleted 3 files and tried to upload one, it just spins. If I refresh the page - i get 504 error

 

Logs in apache/nextcloud/mastercontainer are only from the time of start, nothing recent. 3:26 PM and it is back working.

 

Similar hiccup happened on other instance the other day where I just logged in, and that kicked it down.

Edited March 25, 20251 yr by stefan.tomko

you should start with logs in nextcloud instance.

There are no logs with or around the timestamp when that issue occurs.

in that case if there is no error within nextcloud logs (pay attention to log level), i would search in nginxproxymanager config and logs and also look for dns errors.

Thanks to other forum topic on NC forum where someone pointed out the issue is with the way how NPM connects, i managed to resolve it on my host, by attaching internal docker network from nextcloud to NPM and referring connection to docker container name instead of ip on bridged network.

However I still face an issue since I host 2 NC instances behind my reverse proxy. While one is pointed to internal docker network, other NC instance is hosted on different machine in network where I need to access it via br.

Any ideas on where the issue is, or how to overcome it, without needing to specify other port on wan and forward that over to 2nd npm instance?

OK, I figured this out. Perhaps it will help someone too.

So my setup is - I run several instances of Nextcloud. Before using AIO, I used classic multi-docker install and never had such issues. It started when I switched to AIO. I am using Nginx Proxy Manager. My problem was that with default AIO setup, your nextcloud runs on port 11000 on the IP of your unraid server - this is where you have to forward your traffic to using reverse proxy (NPM in my case).

My NPM is running on br0 and I typically assign specific IPs to docker. Whenever I would connect to either nextcloud instance, it would stutter, become unresponsive. Like - I would get to login pace, log in, but after that, it would not be responsive for few minutes. I figured, after reading other posts on NC forum, it has something to do with networking within unraid - perhaps that I am using br0 for my NPM, connecting to Nextcloud AIO... (I am using ipvlan for dockers, if that is of interest).

 

To get this working - here is what I needed to do:

1) In NPM properties - enable advanced view and in "Post arguments" put this:

; docker network connect nextcloud-aio Nginx-Proxy-Manager-Official

  This will assing NPM also network adapter from internal nextcloud aio network through which all NC dockers communicate

2) Modify your proxy host so that instead of an IP and port 11000, it connects to docker name. Example: your.cloud.domain points to http://nextcloud-aio-apache:11000

 

That resolved connection issues for one of my servers (NC). However I have another unraid server, running different cloud instance, and I needed to figure out a way to pass connection to second NPM. I did not want to dedicate other external port for 2nd instance. Therefore since all my https is forwarded to primary NPM, that is the place where to distinguish connections based on domain accessed.

To make this work:

1) Edit proxy host - configure for example your.second.domain to connect to https://ip_of_second_NPM:443 (assign proper SSL certificates)

2) In that proxy host, navigate to advanced settings and put this there:

proxy_set_header Host your.second.domain;
proxy_ssl_name your.second.domain;
proxy_ssl_server_name on;

3) In secondary NPM, create proxy host that will actually connect to apache of your second instance. Follow same instructions as in first part of this post - assign internal interface to NPM and point connection to docker name instead of IP.

 

That should do it. Now both your.cloud.domain as well as your.second.domain are firstly sent to primary NPM. From there, your.cloud.domain connects to apache docker running on that server, while your.second.domain is sent over to another NPM instance and configured there to connect to apache docker on internal nextcloud network.

 

No more connectivity issues for me.