Page 2 of 2

Re: Zimbra 8.7.11 and Zimbra Drive

Posted: Sat Dec 30, 2017 6:42 am
by zimico
The default config of zimbra already "enable" for accept untrusted cert.
[zimbra@mail ~]$ zmlocalconfig | grep ssl_allow_accept_untrusted_certs
ssl_allow_accept_untrusted_certs = true

I am waiting PTR record to be set up as Javier's suggestion and will post the result.

Regards,
Minh

Re: Zimbra 8.7.11 and Zimbra Drive

Posted: Sat Dec 30, 2017 1:27 pm
by zimico
I updated DNS with PTR record but no luck.
In 11.0.5 Nextcloud:

Code: Select all

[FAILED] Zimbra Drive extension connection test : Impossible to connect to Zimbra Drive extension (response http code: 400 ) 
And in Zimbra 8.8.5 on Centos 7:

Code: Select all

2017/12/30 20:40:39 [info] 11925#0: *44 client closed connection while SSL handshaking, client: x.x.x.x, server: 0.0.0.0:443
2017/12/30 20:40:39 [info] 11925#0: *45 client x.x.x.x closed keepalive connection
2017/12/30 20:40:39 [info] 11925#0: *47 client sent invalid "Content-Length" header while reading client request headers, client: x.x.x.x, server: mail.example.com, request: "POST /service/extension/ZimbraDrive_ConnectivityTest HTTP/1.1", host: "mail.example.com"
Regards,
Minh.

Re: Zimbra 8.7.11 and Zimbra Drive

Posted: Sat Dec 30, 2017 2:53 pm
by zimico
I enable and use http on both zimbra and nextcloud but no luck. Here are logs:
Zimbra side:

Code: Select all

2017/12/30 21:42:37 [info] 18886#0: *23 client closed connection while waiting for request, client: x.x.x.x, server: 0.0.0.0:80
2017/12/30 21:42:37 [info] 18886#0: *24 client x.x.x.x closed keepalive connection
2017/12/30 21:42:37 [info] 18886#0: *26 client sent invalid "Content-Length" header while reading client request headers, client: x.x.x.x, server: mail.example.com.default, request: "POST /service/extension/ZimbraDrive_ConnectivityTest HTTP/1.1", host: "mail.example.com"
Nextcloud side:

Code: Select all

GuzzleHttp\Exception\ConnectException: cURL error 28: Operation timed out after 150000 milliseconds with 0 out of 0 bytes received
/var/www/html/nextcloud/3rdparty/guzzlehttp/guzzle/src/RequestFsm.php - line 103: GuzzleHttp\Exception\RequestException wrapException(Object(GuzzleHttp\Message\Request), Object(GuzzleHttp\Ring\Exception\ConnectException))
/var/www/html/nextcloud/3rdparty/guzzlehttp/guzzle/src/RequestFsm.php - line 132: GuzzleHttp\RequestFsm->__invoke(Object(GuzzleHttp\Transaction))
/var/www/html/nextcloud/3rdparty/react/promise/src/FulfilledPromise.php - line 25: GuzzleHttp\RequestFsm->GuzzleHttp\{closure}(Array)
/var/www/html/nextcloud/3rdparty/guzzlehttp/ringphp/src/Future/CompletedFutureValue.php - line 55: React\Promise\FulfilledPromise->then(Object(Closure), NULL, NULL)
/var/www/html/nextcloud/3rdparty/guzzlehttp/guzzle/src/Message/FutureResponse.php - line 43: GuzzleHttp\Ring\Future\CompletedFutureValue->then(Object(Closure), NULL, NULL)
/var/www/html/nextcloud/3rdparty/guzzlehttp/guzzle/src/RequestFsm.php - line 134: GuzzleHttp\Message\FutureResponse proxy(Object(GuzzleHttp\Ring\Future\CompletedFutureArray), Object(Closure))
/var/www/html/nextcloud/3rdparty/guzzlehttp/guzzle/src/Client.php - line 165: GuzzleHttp\RequestFsm->__invoke(Object(GuzzleHttp\Transaction))
/var/www/html/nextcloud/3rdparty/guzzlehttp/guzzle/src/Client.php - line 125: GuzzleHttp\Client->send(Object(GuzzleHttp\Message\Request))
/var/www/html/nextcloud/lib/private/Http/Client/Client.php - line 137: GuzzleHttp\Client->get('https //www.own...', Array)
/var/www/html/nextcloud/settings/Controller/CheckSetupController.php - line 216: OC\Http\Client\Client->get('https //www.own...')
/var/www/html/nextcloud/settings/Controller/CheckSetupController.php - line 368: OC\Settings\Controller\CheckSetupController->isUsedTlsLibOutdated()
[internal function] OC\Settings\Controller\CheckSetupController->check()
/var/www/html/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 160: call_user_func_array(Array, Array)
/var/www/html/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 90: OC\AppFramework\Http\Dispatcher->executeController(Object(OC\Settings\Controller\CheckSetupController), 'check')
/var/www/html/nextcloud/lib/private/AppFramework/App.php - line 114: OC\AppFramework\Http\Dispatcher->dispatch(Object(OC\Settings\Controller\CheckSetupController), 'check')
/var/www/html/nextcloud/lib/private/AppFramework/Routing/RouteActionHandler.php - line 47: OC\AppFramework\App main('OC\\Settings\\Con...', 'check', Object(OC\AppFramework\DependencyInjection\DIContainer), Array)
[internal function] OC\AppFramework\Routing\RouteActionHandler->__invoke(Array)
/var/www/html/nextcloud/lib/private/Route/Router.php - line 299: call_user_func(Object(OC\AppFramework\Routing\RouteActionHandler), Array)
/var/www/html/nextcloud/lib/base.php - line 1012: OC\Route\Router->match('/settings/ajax/...')
/var/www/html/nextcloud/index.php - line 48: OC handleRequest()
{main}
It's not SSL certificate error and DNS PTR...

Minh.

Re: Zimbra 8.7.11 and Zimbra Drive

Posted: Wed Mar 07, 2018 2:20 pm
by zimico
Hi all,

With help from zimbra support, I solved my issue

Code: Select all

[FAILED] Zimbra Drive extension connection test : Impossible to connect to Zimbra Drive extension (response http code: 400 ) 
There is a bug with curl and php when using CentOS. You need to use php 7.1.14 and curl 7.38.0 (in my case 7.58.0). Hope to help someone who maybe have the similar issue.

Regards,

Re: Zimbra 8.7.11 and Zimbra Drive

Posted: Wed Mar 07, 2018 5:03 pm
by ckcheong79
How to update curl?

Re: Zimbra 8.7.11 and Zimbra Drive

Posted: Thu Mar 08, 2018 9:10 am
by zimico
You need to enable cityfan repo (as well as epel repo, I also enable webtalic repo when installing php71w).
To enable cityfan repo:

Code: Select all

#vi /etc/yum.repos.d/city-fan.repo
[CityFan]
name=City Fan Repo
baseurl=http://www.city-fan.org/ftp/contrib/yum-repo/rhel$releasever/$basearch/
enabled=1
gpgcheck=0
And update curl to latest version.
#yum update curl
#systemctl restart httpd

Regards,