I think it is all working now for installs and updates.
From the zip file, place kopano.repo in /etc/yum.repos.d. Then edit the repo file, replacing "YOURSERIALNUMBER" with your serial number that you should be able to find from your Webconfig.
Place the four rpm's in a folder of your choice then, in ssh, navigate to that folder and run:
In the Webconfig, you can now set a port to and it will disable the service.
You will find in the webconfig that the "Secure iCal Port" is blank. This is because, although it shows as 8443 with Kopano 8.5.8, it is actually disabled due to another pref and the certificates are not set up to enable it to work. In 8.7.5 upgrade, I have set up the certificates to work but not enabled it as this, in effect, changes a current preference which the user may not want to do. If you want to enable "Secure iCal Port", just set it to 8443 or a port of your choice and it should work. In a fresh installation, "Secure iCal Port" is enabled by default.
I have also changed kopano-conderstart to do a proper condrestart i.e to only restart if the app is running. Formerly it just did a restart and there was a cron job in the background triggering this every night (among other things) so it was impossible for anyone to shutdown Kopano or any of its features for more than a day!
If you want to try a fresh installation, place and edit the files as before then do a:
Note I am doing a --nogpgcheck as I can't get the webapp key to work for the moment.
If ping times are really bad, keep your eye on /var/log/syswatch to see if it is not working correctly. If it is struggling to get pings have a look at /etc/syswatch. A while ago it was made so it could also work with tcp and udp pings for slow links. It is now far more configurable.
I've done some testing and it looks like once you make a change to a key's permissions, it is copied through on all renewals so you don't need the bit in the event file.
What I'll probably do is change the instructions so that for the initial set up you do:It should then work for posterity.
Yes. It is a bit brutal because it is generic so has to make the change recursively. Better would be to do:
But then it would be not be a generic solution for everyone that they can copy and paste.
Even better would be to have a standalone job which did it once as it is conceivable that you will have more than one events file - I have both postfix and cyrus-imapd bit I don't know the order of the firing of the events. I am trying to do some tests.
.... the one you created, cyrus-imapd. Put the lines before the restart.
It is looking like there has been a change somewhere along the line. I have set up some tests to see if new certs inherit the old permissions or if there is something else going on and there is a different set up between certificates. My newest are 0600 and older ones are 0644. I don't know if I changed my primary certificate, but I know I did not change my second or third which are 0644. The fourth is 0600. Once I get an idea, I'll amend the HowTo.
Tonight (17/09/19-18/09/19) the following updated packages are being released:
All packages released into the Community last week are being pushed into Business and Home.
* = the package is also being released to Business at the same time.
Packages available for testing
- app-network - probably not worth testing as there is a pending merge request which may cover some iof the issues found. Also you currently need to have at least two unconfigured interfaces before you can create a bridge interface in the first place. To permanently enable the Add Bridge button, you can change line 74 in /usr/clearos/apps/network/views/ifaces.php to:This is a separate issue.
- nextcloud - update to 16.x. Details in this thread.
- app-kopano - update underlying Kopano package to 8.7.5. The update part of the package is complete and available for testing for anyone with a valid kopano licence only. Details are in this post
- app-wordpress - remove dependency on wget; update versions of WP available for download. This is sort of ready but the build system has a minor issue so the package is not really available for download yet. As soon as it is, to update you can do a:
Packages available for testing can be installed with:
Packages being worked on:
- app-network - part way through code merge
- app-kopano - I have not tested a fresh installation, only an upgrade so I need to work through any issues arising. Theoretically I've done the updates .....