Am 28.06.23 um 15:12 schrieb [email protected] ([email protected]):
We have increase the timeout in the latests nightly build (https://bugs.sogo.nu/view.php?id=5781)Can you try it ?
Thanks, it works now. I also read your remark:Be careful, this will lock process until download or timeout is complete. You may need to adjust WOWorkerCount and WOListenQueueSize
Frank
Le Mercredi, Juin 28, 2023 13:06 CEST, "Frank Richter" ([email protected]) <[email protected]> a écrit:Hello, > If you are using Apache in front, maybe you can try to increase timeout as > explained here :> https://serverfault.com/questions/948312/apache-reverse-proxy-timeout-in-60-seconds > <https://serverfault.com/questions/948312/apache-reverse-proxy-timeout-in-60-seconds>We use Apache in front, but this timeout occurs when SOGo fetches the calendar from the CalDAV server. So it’s IMHO a timeout in SOGo. We now take a look why the CalDAV server needs more than 20 secs to deliver the data to SOGo. Frank > > Le Vendredi, Juin 23, 2023 09:42 CEST, "Frank Richter" > ([email protected]) <[email protected]> a écrit: >> Hello, >> >> when users subscribe to web calendars (CalDAV) we see timeouts, when the >> CalDAV server answers too slow: >> >> Jun 23 09:27:11 sogod [2125260]:>> <0x5574f1f944d0[SOGoWebAppointmentFolder]:206DCC-64954980-19-3E98F2C0> Load>> web calendar https://….tu-chemnitz.de/users/…/calendar/ (401) >> Jun 23 09:27:39 sogod [2125260]: [ERROR]>> <0x5574f190c590[SOGoWebAppointmentFolder]:206DCC-64954980-19-3E98F2C0> CURL>> error while accessing https://….tu-chemnitz.de/users/…/calendar/ (28): >> Operation timed out after 20000 milliseconds with 229376 bytes received >> >> Is this timeout value configurable in SOGo?
-- Frank Richter Chemnitz University of Technology, Germany
smime.p7s
Description: S/MIME Cryptographic Signature
