Navigation

    Kopano
    • Register
    • Login
    • Search
    • Categories
    • Get Official Kopano Support
    • Recent
    Statement regarding the closure of the Kopano community forum and the end of the community edition

    Z-Push with HA Zimbra Architecture . Proxy issue

    Z-Push when using other backends
    4
    20
    5038
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • oloncle
      oloncle last edited by oloncle

      My issue was coming from the IPC share memory. I re installed it and the IPC error has disappear but the proxy error was also present.
      I push from production the z-push version 2.1.3 and it “seems” work but in reality any account false ou true is working via z-push but the synchronisation is not working with a mobile phone. The data synchro is not available.

      ynchronized by user: test.user

      DeviceId: sec1925ecbacacce
      Device type: SamsungDevice
      UserAgent: Android-SAMSUNG-SM-A320FL/101.700
      Device Model: SM-A320FL
      Device IMEI: 357xx408xxx4xx9
      Device friendly name: a3y17ltexc
      Device OS: Android
      Device OS Language: français
      Device Phone nr: +33xxxxxxxx
      Device Operator: Free
      ActiveSync version: 14.0
      First sync: 2018-06-05 19:01
      Last sync: never
      Total folders: 1
      Synchronized folders: 0
      Synchronized data: None available
      Status: OK
      WipeRequest on: not set
      WipeRequest by: not set
      Wiped on: not set
      Attention needed: No errors known

      Anybody has already implemented z-push with Zimbra 8.8.7 ?

      liverpoolfcfan 1 Reply Last reply Reply Quote 0
      • oloncle
        oloncle @liverpoolfcfan last edited by

        @liverpoolfcfan
        php-process-5.4.16-45.el7.x86_64
        php-pecl-memcache-3.0.8-4.el7.x86_64
        php-common-5.4.16-45.el7.x86_64
        php-mbstring-5.4.16-45.el7.x86_64
        php-soap-5.4.16-45.el7.x86_64
        php-pear-1.9.4-21.el7.noarch
        php-cli-5.4.16-45.el7.x86_64
        php-5.4.16-45.el7.x86_64
        php-xml-5.4.16-45.el7.x86_64

        1 Reply Last reply Reply Quote 0
        • thctlo
          thctlo last edited by

          have you tried to change :

          define(‘ZIMBRA_URL’, ‘http://proxy.domain.tld’);
          

          to

          define(‘ZIMBRA_URL’, ‘https://proxy.domain.tld’);
          

          Please note, i dont know zimbra, but i did see: https://sourceforge.net/p/zimbrabackend/support-requests/167/
          and maybe you can use this info : https://forums.zimbra.org/viewtopic.php?t=60300#p270549

          1 Reply Last reply Reply Quote 0
          • oloncle
            oloncle last edited by

            Yes already tried theses workaround.
            06/06/2018 11:04:48 [13350] [ INFO] [test.user] cmd=‘Provision’ memory=‘7.22 MiB/7.50 MiB’ time=‘0.12s’ devType=‘SamsungDevice’ devId=‘sec1925ecbacacce’ getUser=‘test.user’ from=‘X.X.X.X’ idle=‘0s’ version=‘2.4.2+0’ method=‘POST’ httpcode=‘401’

            We can see an 401 authentication error … We tried to manually send the soap request and it works :(

            1 Reply Last reply Reply Quote 0
            • thctlo
              thctlo last edited by thctlo

              i also found this one.
              https://forum.kopano.io/topic/682/z-push-behind-basic-authentication
              check if this also applies to your setup.

              and check if your upgrade replaced a setting or more.

              /var/www/html/z-push/backend/zimbra/config.php
              

              check if you server is in the config.php

              For me, im out of thoughts… i do think this is a zimbra problem and it looks like zimbra is not detecting some z-push settings.

              1 Reply Last reply Reply Quote 0
              • oloncle
                oloncle last edited by oloncle

                not my case the authentication is validated by a SSO. I unable a debug in the PHP code and see an error on the soap response .

                06/06/2018 12:12:29 [13606] [DEBUG] [test.user] Zimbra->SoapRequest(): SOAP Message: <soap:Envelope xmlns:soap=“http://www.w3.org/2003/05/soap-envelope”>
                soap:Header<context xmlns=“urn:zimbra”>
                <session />
                <authToken></authToken>
                <notify seq=“0” />
                <format type=“js” />
                <userAgent name=“Android-SAMSUNG-SM-A320FL/101.700(…acacce) devip=172.17.43.1 ZPZB” version=“68” />
                </context></soap:Header>
                soap:Body<NoOpRequest xmlns=“urn:zimbraMail” /></soap:Body>
                </soap:Envelope>
                06/06/2018 12:12:29 [13606] [DEBUG] [test.user] Zimbra->SoapRequest(): SOAP response: Erreur : SOAP content truncated 0!=687
                06/06/2018 12:12:29 [13606] [DEBUG] [test.user] NoOpResponse:
                06/06/2018 12:12:29 [13606] [DEBUG] [test.user] NoOpResponse:
                06/06/2018 12:12:29 [13606] [ERROR] [test.user] Zimbra->Logon(): END Logon - Proxy Error { connected = false }
                06/06/2018 12:12:29 [13606] [ INFO] [test.user] AuthenticationRequiredException: Access denied. Proxy unable to initiate a session on user mailbox server - code: 0 - file: /ideosante/data/z-push/backend/zimbra/zimbra.php:1208

                I think is a problem with the source code because even if i configure my preproduction z-push to communicate with my Zimbra server (8.0.7) in production, it’s doesn’t work. I got the same error.

                liverpoolfcfan 1 Reply Last reply Reply Quote 0
                • thctlo
                  thctlo last edited by thctlo

                  A thing you could try also, is to disable gzip on the webserver running the z-push vhost.
                  That might fix the SOAP content truncated 0!=687 part
                  I’ve found some other things you can read, maybe it helps.

                  Look at : https://github.com/iomarmochtar/ozpy maybe thats an option

                  You could try to setup with https://xdebug.org/ a php debug extention.

                  and these maybe related
                  https://bugzilla.zimbra.com/show_bug.cgi?id=99482
                  https://bugzilla.zimbra.com/show_bug.cgi?id=75827

                  So i suggest, report this bug at zimba.

                  1 Reply Last reply Reply Quote 0
                  • oloncle
                    oloncle last edited by

                    Re,

                    after wide troubleshooting it’s should be an issue with Transfer-Encoding: chunked . The response size doesn’t match the attended size … We have tried all way rproxy, proxy, zimbra no luck :(
                    Maybe a curl issue … troubleshooting again …

                    1 Reply Last reply Reply Quote 0
                    • oloncle
                      oloncle last edited by

                      Got it !: The issue is due to a encoding problem, forcing a soap request in UTF-8 works … why the web server is not working correctly will be the last question !

                      Come back asap with the workaround !

                      liverpoolfcfan 1 Reply Last reply Reply Quote 0
                      • liverpoolfcfan
                        liverpoolfcfan @oloncle last edited by

                        @oloncle said in Z-Push with HA Zimbra Architecture . Proxy issue:

                        Anybody has already implemented z-push with Zimbra 8.8.7 ?

                        I have set up a test instance of zimbra 8.8.8 on Centos 7, with z-push 2.4.2.beta1+0 and zimbra backend 68 running on Centos 6/Apache 2.4.latest and everything looks to work correctly.

                        1 Reply Last reply Reply Quote 0
                        • liverpoolfcfan
                          liverpoolfcfan @oloncle last edited by

                          @oloncle said in Z-Push with HA Zimbra Architecture . Proxy issue:

                          Got it !: The issue is due to a encoding problem, forcing a soap request in UTF-8 works … why the web server is not working correctly will be the last question !

                          Check your php.ini setting for the directive

                          default_charset = “UTF-8”

                          and your HTTPD settings for the directive

                          AddDefaultCharset UTF-8

                          1 Reply Last reply Reply Quote 0
                          • liverpoolfcfan
                            liverpoolfcfan last edited by

                            By the way, if you use RH/Centos with the sclo repositories, the php.ini file is not necessarily in the normal place - in my case the active one is found at /opt/etc/rh/rh-php70/php.ini

                            Always a good idea when troubleshooting to first create a phpinfo.php file

                            <?php
                            phpinfo();
                            ?>

                            and see where it tells you it is picking up the php.ini file from.

                            Configuration File (php.ini) Path /etc/opt/rh/rh-php70
                            Loaded Configuration File /etc/opt/rh/rh-php70/php.ini

                            1 Reply Last reply Reply Quote 0
                            • liverpoolfcfan
                              liverpoolfcfan @oloncle last edited by

                              @oloncle said in Z-Push with HA Zimbra Architecture . Proxy issue:

                              I think is a problem with the source code because even if i configure my preproduction z-push to communicate with my Zimbra server (8.0.7) in production, it’s doesn’t work. I got the same error.

                              Did you edit the source zimbra.php file after downloading it?

                              By default, all editing is done using Notepad++ with Encoding set to UTF-8. This should cause it to be interpreted by the web server as UTF-8, and to send requests/expect responses in UTF-8.

                              If you edited the file with an editor that saved it in any other Encoding format then that could be the source of your issue.

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post