Upgrade to 9.0.0P20...
 
Notifications
Clear all

Upgrade to 9.0.0P20 : chat disapear

6 Posts
3 Users
4 Reactions
1,187 Views
(@d-o-n-g-h-w-a-n)
Joined: 3 years ago
Posts: 2
Topic starter  

Hello, 

The built-in chat disappeard after update. Impossible to activate anymore. No error message.

My installation is a single server, Ubuntu 18.04LTS 4vcpu 8Go Ram 100 Users.

In addition, we will buy Zextras suite soon. I've just installed the trial version after 9.0.0P20 update and deployed Zextras Team Zimlet. Once again, Zextras Team is invisible by my users. Service is correctly running and zimlet is correctly deployed. Any ideas please ?

Best regards.

Damien


   
Quote
Fabio Knoll
(@fabio)
Joined: 4 years ago
Posts: 15
 

Hello Damien, 
thank you for taking interest in our products!

On our experience the most common reason that could be causing this behavior in your environment could be reverse proxy configuration, which can lead to WebSocket connectivity issues.

If that is the case please verify if your Domain configurations are properly set, it is possible to verify this in your environment by running the following command as zimbra user:

* `for dom in $(zmprov gad); do zmprov gd $dom zimbraPublicServiceProtocol zimbraPublicServiceHostname zimbraPublicServicePort; done`

The configuration can also be accessed and changed both on GUI and CLI:

* GUI Admin pannel through the menus Configure `>` Domains `>` Your Domain;
* CLI by running: `zmprov md DOMAIN.TDL zimbraPublicServiceProtocol PROTOCOL zimbraPublicServiceHostname HOSTNAME zimbraPublicServicePort PORT`

Please remember to substitute the uppercase values according to your needs, example:

* `zmprov md example.com zimbraPublicServiceProtocol https zimbraPublicServiceHostname mail.example.com zimbraPublicServicePort 443`

If any changes are made to your domain configuration please regenerate the reverse proxy scripts with `/opt/zimbra/libexec/zmproxyconfgen` and finally restart the reverse proxy with `zmproxyctl restart` command.

Then clearing server cache with `zmprov fc all && zmprov fc zimlet` as a good practice.

And of course, please feel free to reach out to us through our Zendesk support platform, we will be happy to help!

This post was modified 3 years ago by Arman Khosravi

   
ReplyQuote
(@d-o-n-g-h-w-a-n)
Joined: 3 years ago
Posts: 2
Topic starter  

Fabio, thanks for your help.

 

Now, need to find a solution to make working the reverse proxy with https and websocket ...

 

Best regards.


   
ReplyQuote
Fabio Knoll
(@fabio)
Joined: 4 years ago
Posts: 15
 

Hello Damien, glad to be of help!

Posted by: @d-o-n-g-h-w-a-n

Now, need to find a solution to make working the reverse proxy with https and websocket ...

Could you please describe which issues are you currently experiencing?

In the meantime, I would like to suggest to please take a look at this documentation: https://wiki.zimbra.com/wiki/Zimbra_Proxy_Guide

Hope you may find it useful but feel free to ask any questions!


   
ReplyQuote
dominix
(@dominix)
Joined: 12 years ago
Posts: 130
 

usually I fix this problem with this command (as zimbra user) if you consider using 80 and 443 for proxy and 8080 and 8443 as service listening.

 ./libexec/zmproxyconfig -e -w -o -a 8080:80:8443:443 -x https -H $HOSTNAME

you need a zimbra restart after that.


   
ReplyQuote
dominix
(@dominix)
Joined: 12 years ago
Posts: 130
 

usually I fix this problem with this command (as zimbra user) if you consider using 80 and 443 for proxy and 8080 and 8443 as service listening.

 ./libexec/zmproxyconfig -e -w -o -a 8 0 8 0:8 0:8 4 4 3:4 4 3 -x https -H $HOSTNAME

you need a zimbra restart after that.

edit: don't know why but formatting is bad for me, the real line is with no space between the digit after -a  but if I do not put the space the display is f***ed.

 ./libexec/zmproxyconfig -e -w -o -a 8080:80:8443:443 -x https -H $HOSTNAME

 ./libexec/zmproxyconfig -e -w -o -a 8080:80:8443:443 -x https -H $HOSTNAME

 


   
ReplyQuote