Hello Nicholas, took me some time, but I have found more information, while I was setting up a FreeBSD-Environment in a box in which I could build SOGo and SOPE in explicit versions and have all the connnected services like ldap/AD, postfix and dovecot configured.
The problem seems to be in conjunction with requests made to other services: If the imap or ldap connections fail, for example because ldap is not reachable or the imap configuration is wrong. Then the WebUI simply won't finish to load. What I can see is about 70% that the SOGo-Backend delivers to Angular in the Frontend and then stops. This causes the UI to go blank seemingly without any error displayed. But not totally. While clicking around in the Browser I rather randomly went to the browser's Java Script-Console and this shows a Proxy-Error after about a minute, which seems to be a timeout. In the apache log I see this ProxyError > [Wed Nov 04 12:12:42.956664 2020] [proxy_http:error] [pid 18011:tid 34399326720] (70007)The timeout specified has expired: [client 2a00:b580:a000:c800::100d:35790] AH01102: error reading status line from remote server 127.0.0.1:20000, referer: https://vpro0214.proserver.punkt.de/SOGo/so/ry86/Mail/view > [Wed Nov 04 12:12:42.956774 2020] [proxy:error] [pid 18011:tid 34399326720] [client 2a00:b580:a000:c800::100d:35790] AH00898: Error reading from remote server returned by /SOGo/so/ry86/Mail/0/folderINBOX/view, referer: https://vpro0214.proserver.punkt.de/SOGo/so/ry86/Mail/view and in the maillog Dovecot writes the following: > Nov 4 12:24:43 vpro0214 dovecot: imap-login: Disconnected: Inactivity (no auth attempts in 180 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, TLS handshaking, session=<uD/eOUaz4nx/AAAB> When restarting sogod I the many log entries with activated Debug logs I can see this: > Nov 04 12:25:43 sogod [85659]: <0x0x80c3c7028[NGImap4Client]> ERROR(-[NGImap4Client _processUnknownCommandParserException:]): catched non-IMAP4 parsing exception NGSocketException: NGActiveSocket is not open >Nov 04 12:25:43 sogod [85659]: [ERROR] <0x0x8123bd708[NGImap4ConnectionManager]> IMAP4 login failed: > host=localhost, user=ry86, pwd=yes > url=imaps://ry86@localhost:993/?tls=YES&tlsVerifyMode=allowInsecureLocalhost > base=(null) > base-class=(null)) > = <0x0x80c3c7028[NGImap4Client]: login=ry86(pwd) socket=<NGActiveSocket[0x0x80caab988]: mode=<closed> address=<0x0x80caeb758[NGInternetSocketAddress]: host=localhost port=42967>>> So I started playing around with the imap configurations I made: > domains = > { > punkt.de = > { > /* Mail */ > SOGoDraftsFolderName = "Entwürfe"; > SOGoSentFolderName = "Gesendet"; > SOGoTrashFolderName = "Mülleimer"; > SOGoJunkFolderName = "Junk"; > SOGoIMAPServer = "imap://localhost:993/?tls=YES&tlsVerifyMode=allowInsecureLocalhost"; > SOGoSieveServer = "sieve://localhost:4190/?tls=YES&tlsVerifyMode=allowInsecureLocalhost"; > SOGoSMTPServer = "smtp://localhost:465/?tls=YES&tlsVerifyMode=allowInsecureLocalhost"; > SOGoMailDomain = punkt.de; > SOGoMailingMechanism = smtp; When I turn TLS off for imap and switch to port 143, everything works fine. > SOGoIMAPServer = "imap://localhost:143/"; So there has to be some kind of problem between SOGo and Dovecot when communicationg over TLS. But I was not able to figure out what the exact Problem is. For the moment it would be ok switching to imap nistead of imaps. But before trying this in our production system I will replay the whole upgrade process from 4 to 5 with changing to imap in a clone of our production system for testing. Maybe you are able to make out something from this mail to find the underlying problem in the SOGo Code. Cheers Lars Am 12.10.20 um 15:55 schrieb Nicolas Höft (nico...@hoeft.de): > Hi Lars, > >> Any ideas on that? >> >> It is no problem running 5.0.0 for us for now, I just wanted to share >> this, as it might be helpful. Or should I run SOGo 5.0.1 with SOPE >> 5.0.0 on commit 099e8b0ec8251dbddeff337fe728d9398ba744b2? >> > This Log is not really helpful (at least not to me), unfortunately. If > you have time and want to figure out what commit is causing this, I'd > suggest to start with 5.0.0 both SOGo and SOPE and then upgrade SOPE > to 5.0.1 and then if it still works try to bisect which SOGo commit is > causing the login problems. > > > cheers, > > Nicolas > > > -- --- punkt.de GmbH Lars Liedtke .infrastructure Kaiserallee 13a 76133 Karlsruhe Tel. +49 721 9109 500 https://infrastructure.punkt.de i...@punkt.de AG Mannheim 108285 Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein -- users@sogo.nu https://inverse.ca/sogo/lists
