failed to get KWM config



  • Hey,

    I’m trying to install a voice service for Mattermost, one that I can selfhost that is. Kopano is one of the few that have a mattermost integration, so I thought, why not use that one.

    But here is a Problem, I already have trouble enabling the Plugin. The console gets spammed with [Team Name] failed to get KWM config.

    The Mattermost log gets spammed with

    {"level":"error","ts":1565621793.3832557,"caller":"mlog/log.go:172","msg":"Plugin failed to ServeHTTP, RPC call failed","plugin_id":"kopanowebmeetings","error":"unexpected EOF"}
    

    I don’t know if this is a Plugin based problem, or if the problem lies with Mattermost, but would be thankful for any hint.


  • Kopano

    Hi @ArturStoeber,

    did you also setup kwmserver?

    You can find documentation about the Mattermost plugin at https://documentation.kopano.io/kopano_mattermost_manual/webmeetings.html



  • Hello @fbartels,
    yes I did setup the kwmserver and used the given nginx config.

    If I try to open the 2 URLs in Browser I get a “404 page not found” for /api/v1/websocket, and a “auth failed” for /api/v1/rtm.connect.

    I ignored these problems for the moment, because I wanted to get the plugin working first, and the plugin tries to reach a URL that is on the mattermost port (8065), not on the kopano port (8778), so I was thinking that the problem with the Plugin isnt related to having a working server.

    I did one thing different though. I downloaded the mattermost Server directly from mattermost.com (Team Edition 5.13.2), and didnt follow the steps laid down here (https://documentation.kopano.io/kopano_mattermost_manual/installation.html). Which I assume might be the problem, but it is kinda important to me to be able to use the most recent version of software with security patches.

    So I guess the better “First Question” would be “Is the Kopano Mattermost Plugin compatible with the most recent Mattermost Server (5.13.2)”, if thats the case, Im back to my original post.


  • Kopano

    @ArturStoeber said in failed to get KWM config:

    So I guess the better “First Question” would be “Is the Kopano Mattermost Plugin compatible with the most recent Mattermost Server (5.13.2)”, if thats the case, Im back to my original post

    I have not yet tried the Plugin with this version of Mattermost, but am not aware of any incompatible changes in Mattermost.

    @ArturStoeber said in failed to get KWM config:

    I did one thing different though. I downloaded the mattermost Server directly from mattermost.com (Team Edition 5.13.2), and didnt follow the steps laid down here

    No, that should not really make a difference. The packages explained there are also just using the vanilla downloads provided by Mattermost.



  • @fbartels

    Can you confirm to me that the Kopano server needs to be running for the plugin to even start?

    Maybe it would make sense to get the normal desktop app and try to connect that to the Server, to see if the Server even works correctly?

    Any other Idea or input what I can do to either get it straight up running, or get you more/correct informations so you might identify the problem?


  • Kopano

    Hi @ArturStoeber,

    you’ve got me confused. What desktop app are you talking about?

    I can confirm that the mattermost plugin and kwmserver are completely independent of the rest of the Kopano system.

    @ArturStoeber said in failed to get KWM config:

    Any other Idea or input what I can do to either get it straight up running, or get you more/correct informations so you might identify the problem?

    When I last debugged this error message it was caused by Mattermost not being able to connect to kwmserver. So I would make sure that kwmserver is running and that Mattermost has access to it as well as that clients will be able to access it (reverse proxy setup for external access).

    If this is a commercial deployment you could also get in touch with our sales team at info at kopano dot com to organise a remote session on your system.


Log in to reply