@drauer said in Kopano One Repo gone: > re-activated the Kopano One repository
THX for reactivating! I hope the repo and Kopano One stays available for some time as parallel option to Groupware. PLS understand 2016-2021 I spend hundreds of hours integrating Kopano as k4s with Synology recently for DSM-7 with this repo by enthusiasm and for fun. Well, it is no fun when the repo and product goes away with any comm’s or warning.
Is Kopano ONE not based on the same Core? You said I make a downgrade so Kopano ONE is at the moment based on Kopano Core 9.X?
It is based on the same software, just uses a different version. The nightly downloads come from the main development branch, whereas proper releases come from their individual releases branches. For Kopano One we decided to use a build from the 9.x branch, which technically is a downgrade.
I think this is rather a symptom, than the cause of your login troubles. But since you already have a support case open my recommendation would still be to follow this up directly with the Kopano support.
however the port 443 is already in used by another service.
on the same machine? Port 443 is the default port when it comes to services being available through https. For any other port you would need to specify it when opening the address, which negatively impact the user experience.
For example: in apache it is located in /var/www folder and will need to just setup /etc/apache2/config to be able to run the web app. How does it work for Kopano One? Please help to advise.
Kopano One delivers its own webserver to simplify the process of securely serving the WebApp. When following the instruction you have configured it in “11. Configure Kweb”. You could change the port of kweb in https://stash.kopano.io/projects/KGOL/repos/kweb/browse/scripts/kwebd.cfg?at=4323c71be30#50,55 (which also means that you would need to change the port in other places, such as server.cfg to open the right discovery document), but as said before then your users would need to remember a port on top of a domain name.
Generally speaking Kopano One should be installed on a new system, I am not sure if other applications running on the same server is a supported scenario.
actually the man page of the hostname utility recommends to use -f over -d:
Display the name of the DNS domain. Don't use the command domainname to get the DNS domain name
because it will show the NIS domain name and not the DNS domain name. Use dnsdomainname instead. See
the warnings in section THE FQDN above, and avoid using this option.
-f, --fqdn, --long
Display the FQDN (Fully Qualified Domain Name). A FQDN consists of a short host name and the DNS
domain name. Unless you are using bind or NIS for host lookups you can change the FQDN and the DNS
domain name (which is part of the FQDN) in the /etc/hosts file. See the warnings in section THE FQDN
above und use hostname --all-fqdns instead wherever possible.
PS: since you have a subscription for Kopano One the recommended approach to get support is to directly open a ticket with the Kopano helpdesk. This place is just a forum for the community and not an official support channel.
similar to how it is with our general release (the packages that you were referring to are the nightly builds), the packages of Kopano One can only be fully used by Kopano customers with a valid subscription.
You can install the software without a valid subscription but the server will prevent you from creating users until a license file has been supplied.