Kopano Meet install on separate server

nanathlor

I have Kopano Core on openSUSE so have installed a new Meet server on Debian, install is quite straightforward following:
https://documentation.kopano.io/kopano_meet_manual/installation.html

However I get the login prompt but can’t login.

How do I configure meet to recognise that kopano core is not on the same server?
in konnectd.cfg I have tried setting:
kc_server_uri = https://kopano.server.com
kc_session_timeout = 300

But journalctl -xe shows:
level=info msg=“kc server identifier backend connection set up” client=“KCC(http:https://kopano.st-four.com)”

Is that right? It doesn’t work at all if I just put kopano.server.com

Login gives error:
Unexpected HTTP response: 500. Please check your connection and try again.

I can’t find anything in the docs they all expect a same server install, any pointers would be appreciated.

Thanks
Dave

nanathlor

Additional info: journalctl -f -u kopano-konnectd has error:
level=error msg=“identifier failed to logon with backend” error=“kc identifier backend logon error: failed to unmarshal SOAP response body”

Again, can’t find anything on this in the docs.

fbartels

@nanathlor said in Kopano Meet install on separate server:

“KCC(http:https://kopano.st-four.com)”

is this a copy/paste mistake or does it really have http(s) twice?

Generally speaking the address kopano-server is listening on (if configured for https) is port 237, so you would need to set kc_server_uri = https://kopano.server.com:237. In addition to this you need to change the socket in the grapi configuration.

@nanathlor said in Kopano Meet install on separate server:

I have Kopano Core on openSUSE

The alternative would be to migrate the whole system to a Debian base. Since the last fan of OpenSuse left our company earlier this year, we have cleaned up our builds (OpenSuse was anyways never officially supported) and now no longer provide builds for it.