Kopano Meet & WebMeetings

• 

  Runtime Panic starting kwmserverd when --iss not specified
  • sdobz  

  2
  0
  Votes
  2
  Posts
  20
  Views

  

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

  meet docker-compose with existing kopano setup
  • segro  

  3
  0
  Votes
  3
  Posts
  51
  Views

  

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

  kopano Meet without kopano groupware
  • Chris1984  

  2
  0
  Votes
  2
  Posts
  36
  Views

  

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

  Kopano Meet on Univention-Kopano Server
  • zash1958  

  6
  0
  Votes
  6
  Posts
  194
  Views

  

  @onex-de said in Kopano Meet on Univention-Kopano Server: any news or a dated milestone when the UCS app will be ready to install? We still need to sort out an update of the openid app on ucs to make this one compatible with Kopano Meet @onex-de said in Kopano Meet on Univention-Kopano Server: Will there also be a stun server app for Univention? No, this is not planned at the moment. A first step would be to integrate a turn server into kopano-docker, once this is done we could think about it. Relevant issue is https://github.com/zokradonh/kopano-docker/issues/146 if you want to contribute this feature.
• 

  Kopano Meet behind apache reverse proxy
  • ansib  

  8
  0
  Votes
  8
  Posts
  105
  Views

  

  @ansib said in Kopano Meet behind apache reverse proxy: Does the kwebd service have problems running behind an apache proxy? kwebd is running under port 443 with tls enabled (with valid certificate) so apache <> kwebd is using an https connection. No, kwebd is of no concern here since you said it works when used directly. So the issue is the Apache configuration. Not exactly sure where the issue is though. A working Apache configuration is like this RewriteEngine On RewriteCond %{HTTP:Connection} Upgrade [NC] RewriteCond %{HTTP:Upgrade} websocket [NC] RewriteRule /api/kwm/v2/(.*) ws://localhost:2015/api/kwm/v2/$1 [P,L] ProxyPass /api/kwm/v2/ http://localhost:2015/api/kwm/v2/ retry=0 Since yours looks very similar - maybe another rule matches before those rules in your config.
• 

  Strange resolution on desktop devices
  • ansib  

  5
  0
  Votes
  5
  Posts
  83
  Views

  

  @longsleep thank you for your answer. that’s what i expected. i think a solution like skype, hangouts would be nice (the solution which you or fbartels already provided). this topic can be closed or marked as solved, thank you
• 

  [SOLVED] Meet guest access does not work on mobile (Android)
  • irreleph4nt  

  3
  0
  Votes
  3
  Posts
  76
  Views

  

  @fbartels FYI - with the release of meet 1.0.0 this now works as expected. Thank you.
• 

  Cannot open kmeet with intranet plugin
  • white-eagle  

  9
  0
  Votes
  9
  Posts
  91
  Views

  

  @white-eagle said in Cannot open kmeet with intranet plugin: It would be nice if kweb offers the possibility to disable CSP. Well the CSP is for security - so to disable it is not the best idea. Though since this use case is valid it will eventually be possible to extend/configure the CSP. @white-eagle said in Cannot open kmeet with intranet plugin: I always get HTTP 400 errors after login if i use nginx. Well this means your Nginx configuration is not in order. More information might be found if you enable debug logging of the backend services so they do log client related connection issues. Error 400 can have many causes - most likely reason in relation to Nginx configuration might be wrong/no configuration for websocket reverse proxy. Remember kweb does nothing special - it just simplifies configuration. Without it you need a rather complex Nginx configuration to get the same level of security but functionality wise, the minimal Nginx configuration is not particular complicated.
• 

  Same issue Re: [Failed to load app Kopano Webmeetings]
  • TosoBoso  

  2
  0
  Votes
  2
  Posts
  29
  Views

  

  Pinging @domiblouw and @BigCheese. Maybe they can share what they changed.
• 

  Mattermost crashes when Kopano Web Meetings is enabled
  • markkahanmo  

  7
  0
  Votes
  7
  Posts
  77
  Views

  

  Hi @markkahanmo, no unfortunately still busy with other projects. If this is for a commercial deployment I’d recommend to get in contact with our support.
• 

  Guest login does not work (Error 502)
  • q5616417  

  4
  0
  Votes
  4
  Posts
  82
  Views

  

  Thanks for the trace Thomas! This helped and there is a missing return after an error was handled and because of that later on an unhandled panic happens. While i will fix the missing line shortly, this does not fix your problem. Since this is a configuration/setup error with a client the corresponding log entry is only logged when you enable debug logging. If you enabled that, you will see a log entry like "no request object signing alg for client_id key" which indicates, that the client configuration (in identifier-registration.yaml) has an invalid or unknown value for the request_object_signing_alg field.
• 

  [Solved]: kcoid certificate error
  • q5616417  

  6
  0
  Votes
  6
  Posts
  111
  Views

  

  @q5616417 FYI there are a few more places where you need to set this value. https://documentation.kopano.io/kopano_meet_manual/installation.html#Kopano-configuration should be helpful here.
• 

  Webmeeting login with password containing special character '<' not possible
  password meet login konnect • • cguenther  

  5
  0
  Votes
  5
  Posts
  117
  Views

  

  @cguenther said in Webmeeting login with password containing special character '<' not possible: Resetting the password one without this special character, seems to be a workaround. Nevertheless, this might indicate to a problem of not proper escaping of the password Seems that i missed to merge one of my branches and then forgot about it. The underlaying issue is fixed in kcc-go 4.0.0 which will be part of the next Konnect release - both master branches have been updated accordingly. Thanks for reporting!
• 

  [SOLVED] How to obtain a Konnect token to validate payload
  • irreleph4nt  

  2
  0
  Votes
  2
  Posts
  32
  Views

  

  Hi @irreleph4nt, that value is sent to the client after he logged in and is not stored on the server side.
• 

  [SOLVED] Konnectd.service won't start (binary works though)
  • irreleph4nt  

  8
  0
  Votes
  8
  Posts
  162
  Views

  

  @longsleep Your suspicion regarding TLS validation was spot on. Using insecure mode, things started working right away, so I looked into it and sorted out my SSL certificates. Thank you! :)
• 

  Kopano WebMeeting missing some features.
  • Drees  

  3
  0
  Votes
  3
  Posts
  90
  Views

  

  Hi @fbartels thanks for your quick answer. Actually the text field is missing entirely from our installation. i still was wondering since some more things were missing from our setup that were present in the documentation. Maybe instead of investing more time into kopano webmeeting i will take a look at Kopano Meet. Thank you for your time though
• 

  Kopano meet PWA works as app on IOS?
  iosmeet • • hsantos  

  5
  0
  Votes
  5
  Posts
  134
  Views

  

  Thank you for your support. Regards.
• 

  Webmeetings on UCS 4.3
  • sebschremser  

  4
  0
  Votes
  4
  Posts
  117
  Views

  

  @sebschremser said in Webmeetings on UCS 4.3: Any other hints? Then I’d recommend to get in contact with our support, so they can have a look directly on the system.
• 

  Kopano WebMeeting and Plugins vs Kopano Meet
  • ansib  

  14
  0
  Votes
  14
  Posts
  240
  Views

  

  @ansib said in Kopano WebMeeting and Plugins vs Kopano Meet: this surplus $ is still in my binscript under /usr/sbin Yes, I was already thinking it was something like that. I don’t think we have meanwhile tagged a new release, therefore it’s not yet in the packages. @ansib said in Kopano WebMeeting and Plugins vs Kopano Meet: unfortunatly there is still no video media data, only a blue screen, if i start a call. Debugging turn is a bit more difficult. I would recommend to get in direct contact with our support so they can look at it in a remote session.
• 

  The nginx config for meet as given in the docs does not work
  • irreleph4nt  

  4
  0
  Votes
  4
  Posts
  185
  Views

  

  @fbartels I solved this. The issue is that the nginx config given in the kopano-meet installation guide is inclomplete. Looking through the overrides and proxy commands in kweb’s base.go file, I found that it contains a lot more such lines than the nginx config presented. To make meet work with nginx, the below entries had to be added. Please let me know in case I am still missing any not-so-obvious ones. # the alias is missing which makes nginx look for the service-worker.js file in the wrong place (/etc/nginx) location /meet/service-worker.js { alias /usr/share/webapps/kopano-meet/service-worker.js; expires -1; } # all of the below is missing, because of which meet fails to connect to kwmserverd and turnserver location /api/v1/rtm.connect/ { proxy_pass http://kwmserver/api/v1/rtm.connect/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; } location /api/v1/rtm.turn/ { proxy_pass http://kwmserver/api/v1/rtm.turn/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; } location /api/kwm/v2/ { proxy_pass http://kwmserver/api/kwm/v2/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; } # technically works without this one but would be lacking call history if obmitted (i.e. recent calls always empty) location /api/kvs/ { proxy_pass http://kapi/api/kvs/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; } EDIT: Follow-up question: Is there a way to ssl-encrypt the proxy_pass connections to the upstream kopano-services?