Zimbra 8.7.11 and Zimbra Drive
- fs.schmidt
- Outstanding Member
- Posts: 278
- Joined: Sat Sep 13, 2014 3:37 am
- Location: Brazil
- Contact:
Zimbra 8.7.11 and Zimbra Drive
Hi,
I'm trying to use Zimbra Drive and when running the test in the Nextcloud Zimbra Drive App it fails with the message below:
[FAILED] Zimbra Drive extension connection test: Impossible to connect to Zimbra Drive extension (response http code: 400 )
The only log we get is :
2017/09/13 10:06:19 [info] 39906#0: *32990 client closed connection while SSL handshaking, client: X.X.X.X, server: 0.0.0.0:443
2017/09/13 10:06:20 [info] 39906#0: *32991 client X.X.X.X closed keepalive connection
2017/09/13 10:06:21 [info] 39906#0: *32993 client sent invalid "Content-Length" header while reading client request headers, client: X.X.X.X, server: zimbra.mydomain.com.br, request: "POST /service/extension/ZimbraDrive_ConnectivityTest HTTP/1.1", host: "zimbra.mydomain.com.br"
Does anyone have any idea? It's a single server environment with Nextcloud 11.0.4 (stable).
Best regards.
I'm trying to use Zimbra Drive and when running the test in the Nextcloud Zimbra Drive App it fails with the message below:
[FAILED] Zimbra Drive extension connection test: Impossible to connect to Zimbra Drive extension (response http code: 400 )
The only log we get is :
2017/09/13 10:06:19 [info] 39906#0: *32990 client closed connection while SSL handshaking, client: X.X.X.X, server: 0.0.0.0:443
2017/09/13 10:06:20 [info] 39906#0: *32991 client X.X.X.X closed keepalive connection
2017/09/13 10:06:21 [info] 39906#0: *32993 client sent invalid "Content-Length" header while reading client request headers, client: X.X.X.X, server: zimbra.mydomain.com.br, request: "POST /service/extension/ZimbraDrive_ConnectivityTest HTTP/1.1", host: "zimbra.mydomain.com.br"
Does anyone have any idea? It's a single server environment with Nextcloud 11.0.4 (stable).
Best regards.
- jorgedlcruz
- Zimbra Alumni
- Posts: 2782
- Joined: Thu May 22, 2014 4:47 pm
Re: Zimbra 8.7.11 and Zimbra Drive
Hi Fabio,
It looks like a SSL problem, are you using a self-signed SSL on Nextcloud? If so, you will need to import it on the trusted keystore of Zimbra.
Best regards
It looks like a SSL problem, are you using a self-signed SSL on Nextcloud? If so, you will need to import it on the trusted keystore of Zimbra.
Best regards
- DualBoot
- Elite member
- Posts: 1326
- Joined: Mon Apr 18, 2016 8:18 pm
- Location: France - Earth
- ZCS/ZD Version: ZCS FLOSS - 8.8.15 Mutli servers
- Contact:
Re: Zimbra 8.7.11 and Zimbra Drive
Hi,
you can also enable ssl_allow_accept_untrusted_certs into zmlocalconfig from the mailstore.
you can also enable ssl_allow_accept_untrusted_certs into zmlocalconfig from the mailstore.
- fs.schmidt
- Outstanding Member
- Posts: 278
- Joined: Sat Sep 13, 2014 3:37 am
- Location: Brazil
- Contact:
Re: Zimbra 8.7.11 and Zimbra Drive
Hi Jorge and Dualboot,
Thanks for answering. I'm using a trusted wildcard certificate, so I've deployed the same certificate on both zimbra and nextcoud servers.
Regards.
Thanks for answering. I'm using a trusted wildcard certificate, so I've deployed the same certificate on both zimbra and nextcoud servers.
Regards.
- fs.schmidt
- Outstanding Member
- Posts: 278
- Joined: Sat Sep 13, 2014 3:37 am
- Location: Brazil
- Contact:
Re: Zimbra 8.7.11 and Zimbra Drive
I've installed a test environment with the following scenario:
1 - Zimbra OSE 8.7.11 Single Server (proxy and Zimbra Drive installed)
2 - Nextcloud 11 on Centos 7
I've installed a let's encrypt certificate on Zimbra and I'm running Nextcloud only without HTTPS (this is supported, right?). Both servers are on the same network without any firewall. I've followed all the steps in the wiki (https://wiki.zimbra.com/wiki/Zimbra_Dri ... mbra_Drive),
I've changed the zimbraDriveOwnCloudURL parameter for the test domain and ran zmcontrol restart:
zmprov gd improve.inf.br zimbraDriveOwnCloudURL
# name improve.inf.br
zimbraDriveOwnCloudURL: http://nuvem.improve.inf.br/nextcloud/index.php
When I try to test the Nextcloud Zimbra Drive App connectivity it fails:
[OK] Zimbra Drive app installation test : Zimbra Drive app is installed.
[OK] Enabled Zimbra's users test : Zimbra's users are enabled.
[OK] Enabled Zimbra's user login : Zimbra Drive authentication is enabled.
[OK] Is server url set test : The server url is set.
[OK] Is server port set test : The server port is set.
[OK] Zimbra host connection test : Zimbra Drive app can reach the host.
[OK] Zimbra authentication page connection test : Zimbra Drive app can reach Zimbra's authentication page.
[FAILED] Zimbra Drive extension connection test : Impossible to connect to Zimbra Drive extension (response http code: 400 )
If I try to use the Mailbox HTTPS ports (8443) instead of the proxy port it works:
[OK] Zimbra Drive app installation test : Zimbra Drive app is installed.
[OK] Enabled Zimbra's users test : Zimbra's users are enabled.
[OK] Enabled Zimbra's user login : Zimbra Drive authentication is enabled.
[OK] Is server url set test : The server url is set.
[OK] Is server port set test : The server port is set.
[OK] Zimbra host connection test : Zimbra Drive app can reach the host.
[OK] Zimbra authentication page connection test : Zimbra Drive app can reach Zimbra's authentication page.
[OK] Zimbra Drive extension connection test : Zimbra Drive app can reach Zimbra Drive extension.
When I click on the Zimbra Drive it displays the unable to connect to server error.
Kind regards.
1 - Zimbra OSE 8.7.11 Single Server (proxy and Zimbra Drive installed)
2 - Nextcloud 11 on Centos 7
I've installed a let's encrypt certificate on Zimbra and I'm running Nextcloud only without HTTPS (this is supported, right?). Both servers are on the same network without any firewall. I've followed all the steps in the wiki (https://wiki.zimbra.com/wiki/Zimbra_Dri ... mbra_Drive),
I've changed the zimbraDriveOwnCloudURL parameter for the test domain and ran zmcontrol restart:
zmprov gd improve.inf.br zimbraDriveOwnCloudURL
# name improve.inf.br
zimbraDriveOwnCloudURL: http://nuvem.improve.inf.br/nextcloud/index.php
When I try to test the Nextcloud Zimbra Drive App connectivity it fails:
[OK] Zimbra Drive app installation test : Zimbra Drive app is installed.
[OK] Enabled Zimbra's users test : Zimbra's users are enabled.
[OK] Enabled Zimbra's user login : Zimbra Drive authentication is enabled.
[OK] Is server url set test : The server url is set.
[OK] Is server port set test : The server port is set.
[OK] Zimbra host connection test : Zimbra Drive app can reach the host.
[OK] Zimbra authentication page connection test : Zimbra Drive app can reach Zimbra's authentication page.
[FAILED] Zimbra Drive extension connection test : Impossible to connect to Zimbra Drive extension (response http code: 400 )
If I try to use the Mailbox HTTPS ports (8443) instead of the proxy port it works:
[OK] Zimbra Drive app installation test : Zimbra Drive app is installed.
[OK] Enabled Zimbra's users test : Zimbra's users are enabled.
[OK] Enabled Zimbra's user login : Zimbra Drive authentication is enabled.
[OK] Is server url set test : The server url is set.
[OK] Is server port set test : The server port is set.
[OK] Zimbra host connection test : Zimbra Drive app can reach the host.
[OK] Zimbra authentication page connection test : Zimbra Drive app can reach Zimbra's authentication page.
[OK] Zimbra Drive extension connection test : Zimbra Drive app can reach Zimbra Drive extension.
When I click on the Zimbra Drive it displays the unable to connect to server error.
Kind regards.
- fs.schmidt
- Outstanding Member
- Posts: 278
- Joined: Sat Sep 13, 2014 3:37 am
- Location: Brazil
- Contact:
Re: Zimbra 8.7.11 and Zimbra Drive
Just to report that it worked when using the Mailbox port (8443) on the Nextcloud Zimbra Drive App:
https://github.com/fsschmidt/temporario ... pturar.PNG
In this case, it works, but what should I do in a multi server environment? Should I install the zimbra drive extension on my proxy servers? I can't use the mailbox port since on my multi server environment I have multiple mailbox servers.
Regards
https://github.com/fsschmidt/temporario ... pturar.PNG
In this case, it works, but what should I do in a multi server environment? Should I install the zimbra drive extension on my proxy servers? I can't use the mailbox port since on my multi server environment I have multiple mailbox servers.
Regards
- jorgedlcruz
- Zimbra Alumni
- Posts: 2782
- Joined: Thu May 22, 2014 4:47 pm
Re: Zimbra 8.7.11 and Zimbra Drive
Oh good to hear, that's weird, do you access using 443 to the web client?
- fs.schmidt
- Outstanding Member
- Posts: 278
- Joined: Sat Sep 13, 2014 3:37 am
- Location: Brazil
- Contact:
Re: Zimbra 8.7.11 and Zimbra Drive
Hello Jorge, it's good to hear from you.jorgedlcruz wrote:Oh good to hear, that's weird, do you access using 443 to the web client?
Yes, I access Zimbra using 443. This test environment is published online: https://mail.improve.inf.br
I've done another installation on a production environment (single server) and I had the same behaviour.
I couldn't find any solution to make it work connecting to port 443. I need to install Zimbra Drive on a Multi Server environment and connecting to a single mailbox wouldn't work in this case.
Kind regards.
- fs.schmidt
- Outstanding Member
- Posts: 278
- Joined: Sat Sep 13, 2014 3:37 am
- Location: Brazil
- Contact:
Re: Zimbra 8.7.11 and Zimbra Drive
I've updated the server to Zimbra 8.8.3 and the problem still persists.
Release 8.8.3_GA_1872.RHEL7_64_20170905143325 RHEL7_64 FOSS edition.
Release 8.8.3_GA_1872.RHEL7_64_20170905143325 RHEL7_64 FOSS edition.
-
- Posts: 38
- Joined: Sat Dec 27, 2014 7:09 pm
Re: Zimbra 8.7.11 and Zimbra Drive
Hello All
I think perhaps i ve reach a solution
I had the same problem with owncloud 9 and owncloud10.
All worked after this steps:
1) Include a dns entry A type as mynameserver.mydomain.xx in A a.b.c.d
2) Configure reverse dns for this
3) Get a Let's encrypt free certificate and install it
An after all works.
Perhaps can help someone... i Think that if you uses a self signed certificate, it does not work and needs a perfect dns setup.
best regards
I think perhaps i ve reach a solution
I had the same problem with owncloud 9 and owncloud10.
All worked after this steps:
1) Include a dns entry A type as mynameserver.mydomain.xx in A a.b.c.d
2) Configure reverse dns for this
3) Get a Let's encrypt free certificate and install it
An after all works.
Perhaps can help someone... i Think that if you uses a self signed certificate, it does not work and needs a perfect dns setup.
best regards