@flobian
well I updated now too. We are running the same UCS version now. No luck at all.

Still this message after logging in to UCS and try to use kopano meet. Still unsure whether this message is triggered by not being able to connect to the ucs-kopano turn server, or not.

failed_conn_kopano.JPG

Hi @nanathlor,

kweb is intended to make the usual Kopano setup simpler and more secure.

Exposing a system through multiple domain names is rather unusual and only useful in bigger environment that need finer tuning anyways. You should look into other reverse proxies.

@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.

@xplod-ing hmm… that looks all correct. Not quite sure why logins then don’t work on your system. I am guessing there is no further logging upon a denied client login?

If you have a subscription I would recommend to get in direct contact with the Kopano support, so that someone could have a direct look at your system.

@fbartels: The way we had set up the meeting was by a link that she had received in Facebooks messenger. From there she/the Android OS might have activated the standard browser - so yes very plausible that she did not use Chrome.

We will have that in mind next time (if we send by mail, the Android OS will prompt a browser choice for the user)

… on the other hand; hope that you will fix it, so it can run smoothly on all browser in the future (you have sustainable politics on your side as Zoom is partially made in China :-) )

@fbartels
The options are amazing, I always thought my camera was so bad…

Well, that should really be adjustable in the maindoku and in the web interface.

Hi @nanathlor,

the packages in the location that you posted are basically leftovers from what we choose to publish at https://download.kopano.io/supported/meet%3A/. Suse (in fact rpm support in general) is missing from Meet as a whole, which is partly because of difficulties packaging python applications for these platforms (too old Python, combined with the need to package additional dependencies).

It simply wasn’t worth the effort to us so far.

Hi @jochen77,

I think the browser console shows error message from a different application. But since your url was part of the screenshot I tried opening meet there myself. What can be seen there is that the Univention ID Provider responds with “temporarily_unavailable”.

This and similar topics have been discussed in the Univention forum at https://help.univention.com/t/kopano-meet-not-working/13943/. Please check that thread and report back (here or there) if you were not able to resolve the issue yourself.

In case you have a subscription for Meet you of course can also get in touch with the Kopano support directly.

Hi @segro,

a working example configuration can be found at https://github.com/Kopano-dev/kopano-docker/tree/master/examples/meet

Hi @boospy,

if you are using windows this might work https://itstillworks.com/play-sounds-over-skype-having-put-mic-up-speaker-22542.html

Hi @mcdaniels,

their compat document states:

and other video conferencing, recording, and broadcasting applications that support USB cameras

So I would say that using Meet with it should be no problem.

@fbartels Thanks, now it works :-)

UPDATE:

First of all thanks @fbartels …

The problem was wrong Hardware Clock it was different than the system clock.

I had to disable the HyperVisor Sync Time and then i did

hwclock -w on the command line, to set the hardware clock equal to system clock.

Now it works Thanks a lot

Best Regards,

@longsleep

That’s all ok, if i set allow_guest_only_channels to yes.

Could it not be easily adapted in the check, whether the channel is
active, if a guest want to join in. If the check will be extended to look
for an registered user looged in, before it allows the guest to login ?

Thanks for the info. We have a synchronous fiber connection here (150/150). However, only one fixed IP.
So the thought was obvious to place the Coturn server here.

We have an external webserver but we don’t have full access to it to install Coturn.

I will ask the ISP if we can get a second fixed IP.

I am still reading through the documentation and will also try to get it running.

What is confusing for me is that I find many different statements on the web about this use case:

Works with second IP Is complete nonsense Works also with one IP

Sorry it’s not a kopano issue but an haproxy one. I just update it too from 2.1.10-1~bpo10+1 to 2.2.6-1~bpo10+1

I just test with an rewrite of my /etc/hosts and kopano is working well without haproxy.

Hi @kios_gmbh,

grapi is a dependency that can be resolved through the following repository https://download.kopano.io/supported/core%3A/8.7/

@ckruijntjens i don’t understand the question. Just like you would install any other package.

If you had a subscription you could simply configure our repository. Since you have not you either need to build a local repository or manually install the package.

@Jochen77 said in Kopano Meet with UCS after "Login" 404 not found:

and the ssl certificates are valid.

curl does disagree with you:

curl $(ucr get oidc/konnectd/issuer_identifier)/.well-known/openid-configuration curl: (51) SSL: no alternative certificate subject name matches target host name 'ucs-sso.url.intranet' curl $(ucr get oidc/konnectd/issuer_identifier)/signin/v1/welcome curl: (51) SSL: no alternative certificate subject name matches target host name 'ucs-sso.jh-edvservice.intranet'

Its also strange that this complains about two different domains not being part of the domain. as in the ucr variable has a different domain stored each time you request it. Is that a system with multiple ucs nodes?

@Jochen77 said in Kopano Meet with UCS after "Login" 404 not found:

curl https://$(ucr get kopano/docker/FQDN_SSO)/signin/v1/welcome [..] <address>Apache/2.4.25 (Univention) Server at ucs."External domain.de Port 443</address>

This (that its an Apache error) indicates that the univention openid provider is not configured properly (which has to be done manually when changing the domain name). Normally it should proxy that url to a Docker container, but that proxy seems to be missing in your case.

Hi @pixel,

I’ve answered the phone question at https://help.univention.com/t/meet-webmeetings-matterhost/16230/2