Trying to figure out if there are IPv6 issues or just a slow computer. #4604
-
I'm very confused and I am wondering if https://github.com/nextcloud/all-in-one/blob/main/docker-ipv6-support.md applies if the setup is behind a reverse proxy. I'm using HAProxy in my case. Occasionally I will get some timeouts (the reverse proxy throwing a 503) when trying to do some tasks like looking at emails via the Nextcloud Mail app. I'm trying to figure out if IPv6 is the issue and docker is tripping. But I suspect maybe I'm just using too limited hardware for some tasks maybe. System specs via neofetch
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
I solved some timeout issues by having If I understand it correctly it's just really useful if you have a load-balancing setup behind your reverse proxy. If you only ever have one nextcloud server you don't need to "redispatch". In my case I am using Nextcloud with the data directory on an external USB 3.0 5-bay drive hardware RAID enclosure from yottamaster which can be slow sometimes, slow enough to cause HAProxy to trigger a timeout with "redispatch" enabled. It seems like possibly when the Nextcloud server is slow it was allowing the session to be dropped prematurely. The other issue was the mail app and adding these two to Nextcloud seemed to help. From the defaults I up it to 60 second IMAP and 20 second SMTP connection timeouts.
The system still is "slow" as some tasks take a little bit, but I haven't seen a 503 HAProxy timeout page in a bit now. I probably have a bottleneck with the I/O on the USB storage. |
Beta Was this translation helpful? Give feedback.
-
As for the IPv6 question above, I'm not sure still. Any ideas? |
Beta Was this translation helpful? Give feedback.
I solved some timeout issues by having
option redispatch
set tono option redispatch
in my haproxy.conf. As per https://www.haproxy.com/documentation/haproxy-configuration-tutorials/service-reliability/retries/ and https://docs.haproxy.org/2.9/configuration.html#option%20redispatchIf I understand it correctly it's just really useful if you have a load-balancing setup behind your reverse proxy. If you only ever have one nextcloud server you don't need to "redispatch".
In my case I am using Nextcloud with the data directory on an external USB 3.0 5-bay drive hardware RAID enclosure from yottamaster which can be slow sometimes, slow enough to cause HAProxy to trigger a timeout with "redispa…