latest kopano build breaks z-push functionality
After these package upgrades it breaks
What exactly do you mean with “breaks”? The message about kept back packages? Apt only updates packages when running an upgrade. To also get new/changed dependencies in you need to run
ckruijntjens last edited by ckruijntjens
hi i have done this, but after this step mobile sync is not working anymore. so all is fine until the last step
The following packages will be upgraded:
kopano-search kopano-server libkcserver0 libkcsoap0 python3-kopano
When these above packages are upgraded i get a blank page after login.(503) if i restore my backup before the update everything is working again as it should.
ah, this is the build with the new gsoap. if you check on your server with netstat on which ports kopano-server is listening you will notice that it currently only listens on ipv6, while z-push want to talk to it through ipv4.
a thank you for your reply and indeed this is the problem. How can i make it that kopano listens on ipv4 again?
@ckruijntjens you have to wait until to above linked ticket has been fixed.
ok thank you. now i now it is not a problem on my side. thank you for the reply and explaining.
Hi any eta on the fix?
marcus.bauch last edited by marcus.bauch
Working on Supported, but there is a z-push login error, too.
First you should check /etc/kopano/server.cfg is bind to the IP-address you prefer.
#server_listen = *:236 server_listen = [18.104.22.168]:236
Before update *:236 is binding kopano-server to all IP-addresses running on the maschine. After update, kopano-server bind it self only to localhost.
Our WebApp- and z-push-server are running on a different maschine in a dmz. So, not all packages from core are needed to be installed, but kopano-server need to run on an IP of choise. Maybe, if you run core grater then 8.7.x two more dependencies (libkcutil0) need to be installed, because they not installed automatically:
After that, z-push AND WebApp working as supposed.
Hi marcus yust tried however server is not listening on the ip and port provided.
After latest build (last night) everything seems to work again