Hello @rubelman, It seems that the Java environment variables are misconfigured in your server. Indeed, that "/bin/java" is uncommon. I suggest ch...

Hello @rony, I guess that the goal of the article is to list the ports used by Zimbra and give more details on them, so SysAdmins can properly confi...

Hello @trigg3r >I used Zextra to migrate my server from Zimbra 8.8.15 to Zimbra 9 Well, this of course confirms my hypothesis. Unfortunately, ...

Hello @roykato, may I ask you how you intend to perform the migration? If you're going to perform an incremental migration, which is the most advi...

Hello @r4v3n, This is the code snippet regarding your error: int status = response.getStatusLine().getStatusCode(); if (status >= 400) { t...

Hello @faith.feyrer, I guess that this can be caused by a wrong locator value inside the database, caused by the migration. Probably, the volume i...

Hello @trigg3r, Zimbra 9 only takes one parameter as order criteria for querying the database, please take a look at the SearchRequest API documenta...

@Humuku the solution seems to be the same as my first post in this thread. Glad that you confirm that resolves. 😊 This configuration is needed in...

@wenzling do you have any external reverse proxy between the clients and Zimbra, or any other network device that can interfere with the WebSockets co...

@wenzling great, let me know if it resolves! 😊

@wenzling your Team/Connect issue represented in the screenshot is usually caused by wrong reverse proxy settings, in particular, I suggest to run the...