Hi @ckruijntjens and @MarcusRieche,

I have just pushed an update of the packages that now include 5.25.5, which is the current “Extended Support Release” of Mattermost. Please be aware that this will very likely be the last update to these packages.

To continue using Mattermost please follow the official installation instructions to choose an alternative install method. Migration instructions can be found in the Mattermost documentation.

solved, i’ve forgot to activate the notification in the user settings

Hi @ckruijntjens,

I don’t think Mattermost has this functionality. But general usage questions are probably better suited on the Mattermost forum anyways.

@ckruijntjens said in mattermost websockets:

Could this be the problem why websockets are not working?

Do you mean: “It does not work simply because it shows a different name for the issuer”? If so then, no I don’t think so.

But the issuer name implies that at your company a custom ca is installed on workstations. This can be used to decrypt traffic. And maybe the system that decrypts traffic also mangles it and breaks the websocket connection.

Again: I would recommend to follow up with the it responsible at your company because this cannot be meaningfully debugged without access to the environment or knowledge about configuration/product details only your it knows.

Hi @ckruijntjens,

you will likely have more luck asking such questions on the mattermost forum.

@ckruijntjens @fbartels

allredeay resolved it :-)

Or can you add the debian 10 packages?

@TGM said in Issue when make Kopano plugin for Mattermost:

@fbartels do you know, which URL exactly the plugin is trying to open at the kwmserverd machine?

Kwmserver exposes an API. For an example URL routing configuration, take a look at https://stash.kopano.io/projects/KWM/repos/kwmserver/browse/Caddyfile.example - Mattermost plugin uses API v1 while Meet uses API v2.

Generally it is perfectly normal to get a 404 if you access the web server route of kwmserver (since nothing is there).

@_r9 thanks for sharing. The documentation I was referring to was the included Apache vhost in our Mattermost packages, but since you’re running in Docker you are probably not using these.

These had already something quite similar to your code, except it used a header edit. But on the other hand since we both consulted the same apache documentation it also had the same unset.

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.

Hi @irreleph4nt,

the webmeetings plugin and meet are two separate pieces of software, which at the moment do not interact (and only relate to each other because they are webrtc based and use kwmserver as a signalling server).

That Mattermost sometimes does not load after enabling the plugin is known, but since there are not that many users using it we did have a priority for fixing this. Honestly there is even a chance that the plugin will be discontinued and be replaced with a simple wrapper around Meet.

Hi @mcdaniels ,

such very specific Mattermost questions are probably better suited for the Mattermost forum. You can find it at https://forum.mattermost.org/

Update: Hm, today it is working. Nothing changed. (Except the Workstation, where Deskapp runs, was shutdown/restarted).

Thank you very much, Felix!

Hi @janwie ,

No sorry not yet. I’ve asked the developer for an update.

As per your signature you are still on Mattermost 4.4.2. Why are you so far behind? Also Core, WebApp and Z-push have seen quite some releases meanwhile…

as for your question. it seems you are looking for https://docs.mattermost.com/administration/config-settings.html#enable-integrations-to-override-usernames

We have a pr ready that implements OpenID connect (as for example provided through Kopano Konnect). We still need some more votes on the feature request to convince the Mattermost team that the community wants it. Please feel free to share the link ;-)

https://mattermost.uservoice.com/forums/306457-general/suggestions/10197642-support-openid-connect

If you have something time critical I would recommend to open a support case instead.

@a-altenhoff said in Mattermost Update 4.4.2:

In addition, I still have the message ‘AD/LDAP is not available on this server’ for some users.

This option is only available if you have a Mattermost license file uploaded on the server.