Thanks for your answer. It may be that I have not fully understood how Meet works. But shouldn’t it give me a webinterface if I call http://meet1.mydomain.com ?

I tried it via port 80 before and it gave me a 404 - not found. (this message came from kweb)

Edit: Oh man… sorry… perhaps I should have tried: http(s)://meet1.mydomain.com/meet

SORRY!

Hi @mcdaniels,

@mcdaniels said in Installationerror python3-graphi.mfr / kopano-graphi-bin:

Concerning meet:final

no this is more about the versions of the rest api that is part of the Meet repository. Since the initial release of 8.7 there was quite a lot of work put into it so the currently master packages are not directly compatible.

Hi @haru,

just to run Meet with your own turn server the auth service mentioned by @longsleep is not neccesary. What you need to configure are the following two settings: https://stash.kopano.io/projects/KWM/repos/kwmserver/browse/scripts/kwmserverd.cfg#74-83

For the uri part its important that you actually specify a uri (which is something people seems to be struggling with). You can find examples of valid uris at https://tools.ietf.org/html/rfc7065#appendix-A.

Many thanks !! just adding one space and it’s working now. I couldn’t succeed without you !

@fbartels … and done!
Thank you very much!

Best regards, Christian.

@onex-de said in [SOLVED] how to debug Meet on UCS?:

I don’t know why this wasn’t enabled by default …?

That totally depends on the rest of your configuration (which you haven’t shared).

In the default configuration the openid provider is installed to the ucs-sso subdomain. There is documentation at Univention that says that if you change the domain in their app, you need to take care of Apache configuration yourself.

For the app appliance I had a similar challenge. To spare people from managing two domain names I moved the openid provider to the main domain. This can be easily scripted (as it needed to be for the appliance). The script can be found at https://stash.z-hub.io/projects/K4U/repos/kopano-apps/browse/kopano-meet/appliance_hook.

@strippe96 then i sincerely hope the both of you are getting better soon.

While the german health system feels quite broken at time, from am outside view it seems to perform quite well at the moment.

@krenzlin the next app version (currently waiting for review and release by Univention) with the version 2.1.0-1 has a settings UI for this.

If you enable the test appcenter then you could already give it a try. Steps to activate can be found at https://docs.software-univention.de/app-provider.html#testing:test-app-center

Not all apps there will be stable, so you should deactivate after updating meet.

In addition to this this app update also adds credentials for a free to use turn service (check the readme on limitations).

@Coffee_is_life said in The nginx config for meet as given in the docs does not work:

funny thing is, i can join everyting, even with guests but im getting the same error message:
Mar 24 16:29:08 <my_server> kopano-konnectd[452]: level=error msg=“inner authorize request failed”

This seems to be a wrong error message (since there was no error). Thanks all for reporting - a fix will be made. For now this message can be ignored unless additional fields (other than msg and level) are present as well.

This worked like a charm - many thanks for that -
thought i need to change everything to sso, not just activate the sso switch in server.cfg

i’ve got it running now with everything needed.
just 2 questions left:

first: i know kopano-meet is in developing state and some features arent available (like the apps-tab on the top right - deactivated calendar and contacts, rerouted the webapp to my actual webapp - so this is fine)
but is there any outview for the comeing features and maybe a timeline plan when this will aprox. published?

second: how do i log auth-fails in kwebd/konnectd/meet - fail2ban needs some infos on this and i dont want to expose any our servers without it.

thanks in advance, best regards and stay healthy
coffee_is_life

Hi @fkroeger,

the listing on kopano.com refer to the Kopano groupware product and the old web meetings product. For the new meet the relevant information are on meet-app.io.

Hey Bob,

for the openid-connect-provider issue, we couldn’t help much. It was, for at least one user, a reason for giving up using it :(
For the cam/mic issue, we could help the user via remote support. Maybe there could be a hint somewhere for the user, that they have to give permissions directly. (even it seems to be logical in a video-call context)

Is there a way to measure the traffic per user-session? I am asking this, because we’ve had users, that could easily participate in a group call, and next time it was more or less impossible to get a one-on-one session with that same user (even in a audio-only session). I know it there are a lot of chain links in that question. What we used to hear from our customers is something like “What about using skype instead? They can handle it.”

Cheers
Sebastian

@plzk-de if I remember correctly then for logged in users you could just reuse meeting room links, guests had a token which would expire at some point in time.

But you should really take a look at Meet, especially with many users you will have far more joy with it.

@longsleep: Thank you very much, that looks much better now.

I updated the rewrite rule as follows and now I’m at directed to the group call page as guest.

RewriteRule "^/meet/r/(.*)$" "/usr/share/kopano-meet/meet-webapp/index.html" [L]

Then I had a nice group call with my alter ego “Obsidian Solsticerider” \o/.

I will further test this configuration for now, as it’s a nice playground for me as an enthusiast. If things get more serious with meet I will definitely proxy to kweb.

@fbartels: thank you very much for your support.

@onex-de @zash1958 the Meet app has just been published for UCS 4.3 and 4.4. There is no listing on the Univention homepage yet, though. this usually follows a few hours later.

Looking forward to your feedback.

Now listed on the website as well:
https://www.univention.com/products/univention-app-center/app-catalog/kopano-meet/

@TGM said in Meet and Mattermost:

Replacement of the Jitsi widget with Kopano Meet inside of Matrix/Riot, for example?

Yes, exactly that. Replacing the current hard coded Jitsi integration with Kopano Meet.

Hi @thctlo

No.
The “good” worker installed this server and webmeetings never worked with his hand-made config.
Our sales team gave me the order to set up the TURN credentials. I just wanted to test if everything is working as expected. But it never did.
Yes from my previos posts it looks like I installed webmeetings. But I just reinstalled it once. Yes I know reinstalling is a windows thing.

Of course HSTS is a good thing. But I can accept the risk that apache connects unencrypted to localhost for webmeetings.
Or is there a privacy law that I’m already breaking?
I’m just a simple IT technician but surely i have to comply to privacy laws.

In the end I just wanted to post the solution for this problem.

Cheers Basti

Thanks for the report. Fixed in https://stash.kopano.io/projects/KWM/repos/kwmserver/commits/d0411f38fa1cb9dd9f6f8e9b1289518e1d7b3323 and will be in the next release.

@segro said in meet docker-compose with existing kopano setup:

error=“kc identifier backend logon error: failed to open unix socket: Get Connection timeout”

This error message indicates that your setting of KOPANO_SERVER_DEFAULT_URI=http://192.168.0.10:236 has no effect (since that error message is from the unix socket connector).

Hi @Chris1984,

yes Meet also works independently of the other Kopano servicde (it only requires Konnect and Kapi/grapi who all can be configured directly against ldap). in fact the default information on meet-app.io are also on!y referring towards ldap.