My name is Thomas Elsen.
You can find more information on my LinkedIn profile: http://be.linkedin.com/in/thomaselsen
My name is Thomas Elsen.
You can find more information on my LinkedIn profile: http://be.linkedin.com/in/thomaselsen
By continuing to use the site, you agree to the use of cookies. more information
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.
Zimbra : Version 8.8.5 (with proxy and memcached)
If I do not restart zimbra services at least once a day (zmcontrol restart), I will get this error msg next day in zimbra.log. All email clients will prompt for username and password when this happen.
Apr 14 14:49:46 mail saslauthd[9937]: authentication against url ‘https://mail.domain.com:7073/service/admin/soap/’ caused error “curl_easy_perform: error(28): Operation timed out after 15000 milliseconds with 0 out of 0 bytes received”.
Some online articles commented due to the old version of Curl. I have upgraded curl version to the latest version but till no luck.
curl 7.59.0 (x86_64-redhat-linux-gnu) libcurl/7.59.0 NSS/3.28.4 zlib/1.2.7 libpsl/0.7.0 (+libicu/50.1.2) libssh2/1.8.0 nghttp2/1.21.1
Release-Date: 2018-03-14
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz HTTP2 UnixSockets HTTPS-proxy PSL Metalink
Some said due to the GoogleDNS, I have changed the resolv.conf NOT pointing to GoogleDNS, but still not luck.
https://www.digitalocean.com/community/questions/how-to-solve-curl-error-28-resolving-timed-out-after-10518-milliseconds