@junglemarc +1

Hi, I had a similar problem, but I installed the original version of the Outlook, and reinstalled the latest one. It helped me :)

apt update ; apt upgrade

is good now, thank you.

Marc

Hi @fkoyer,

thanks for the notice. The system was acting up in the last days and it seems to confluence java processes had been killed. I just applied some updates and restarted it to bring it back online.

@fkoyer said in Bad Gateway accessing Wiki:

Also, are you planning to update all the links in the forum that point to z-hub.io that are now broken?

Like going through all the posts in this forum and editing posts to link to the new domain? No, I am not planning this, but if anybody volunteers for this we can look into how to make this possible.

@tboernert if need be, we’d like to contribute (money, testing capabilities, unnecessary comments, :) )
We are also looking for such a solution and kopano seems to be not available (or not interested).

Just say the word.
Best regards
wleithner

Not yet. I have a ticket open for this request for zpush. https://jira.kopano.io/browse/ZP-1638

OK, an admin removed the IPv6s that weren’t working.
So it’s legacy IP only for now, but at least it works with NAT64/DNS64.

Thanks :)

Hi @gutschy,

the primary language of this forum is english. Please translate your question so that other users can benefit of it as well.

Hi @fbartels ,
thanks for not calling me a complete idiot. Of course using ssh. I’m not a server guy but done a few things with some raspberries. To my apologize, I would like to say that I’ve been more on the arduino track in the last two years.

greetings,
gutschy

THX, will test in a few moments.
Cheers
W.

Thanks to all for your help, now I’m in. I’ve done a new installation with “debian 9 64 bit” and everything looks fine. Now we will see. :)

Hi @odix67,

in general we adopted semantic versioning for our software a while ago, which specifies when a new tag should be major, minor or patch.

The mix of versions in Core can be explained in the following way:

8.7 is the current stable for all customers 9.x is part of Kopano One and brings a nice licensing component, Kopano One is the recommended installation for new customers because of the new licensing component users upgrading from 8.7 need to convert their subscription key, which requires some more automation to provide a smooth transition 11.x is the head of our main development branch

@odix67 said in Version numbering for community version, Kopano One and Kopano core:

btw. are there any plans in the near future for a replacement of the current WebApp ?

Yes, the idea is still to replace WebApp with new web applications designed as so called Progressive Web Apps (PWA), which make use of OIDC and a RestAPI to communicate with the Kopano backend.

Weird, judging from past occurrences I would guess that more likely the build process if broken than that this is a conscious decision to only support limited operating systems? I have no clue though.

I don’t think it’s a problem for your upgrade, I would disable the kopano services with systemd, then upgrade ubuntu 18.04 => 20.04 and then install the new packages (via a local repository is probably the best way). This should overwrite the old ones and sort out dependencies. Or you make a list of all kopano packages and remove them before upgrading (config and database will stay unless you “purge” instead of “remove”).

If you need old packages for ubuntu 18.04 PM me, i have
core-11.0.1.101.a68bc0f-Ubuntu_18.04-amd64.tar.gz from Apr 21
which is likely the last one that was offered here for download (i download 18.04 and 20.04 core archives weekly with a script if there are new versions, this is the most recent 18.04 version my script downloaded)

You can configure multi tenant mode of the Kopano server by following these steps.

KCCONF_SERVER_ENABLE_HOSTED_KOPANO=YES
KCCONF_LDAP_LDAP_COMPANY_TYPE_ATTRIBUTE_VALUE=kopano-company

Also, I am using Cloudways managed hosting and I have done this process through their platform which is much easier.

@fbartels Thank you very much for your time! Now I see what I can do.
Kind regards,
Andreas

@ebroch and @Sinux a statement can be found here https://forum.kopano.io/topic/3738/packages-and-services-available-under-new-locations

If your database is only used on this host, you may also use:

skip-external-locking skip-name-resolve

57 connections is not a whole lot, I would not limit that anyway - the default is 150.
“query_cache_size” and “query_cache_limit” with InnoDB are a difficult topic - it is usually better to set “0”.

You may also use multiple buffer pools for better concurrency with:

innodb_buffer_pool_instances

I usually match my number of cpu cores with the number of buffer pools and io-threads.
The overall buffer pool size is calculated “innodb_buffer_pool_instances” * “innodb_buffer_pool_size”.

Why are you increasing “innodb_lock_wait_timeout” ?

More is not always better…