AlphaObeisance
Well-Known Member
First and foremost my children and I greatly appreciate the contributors to mattermost; it directly supports the education and growth of my family. That said, shame on whoever is in charge for forcing private/personal not for profit users to purchase basic functionalities that were once provided for FREE with this FOSS project. I'm not above supporting a project, but this very much taints my taste and desire to do so.
This resolves the issue for me being just a dude hosting MM on my home lab so I can collaborate with my children; being forced to pay for a pre-existing service is quite mind blowing to me. I must admit that I'm new to Mattermost. But to my surprise, trying to do a group call yielded "Only available in DM Channel" or whatever had me scratching my noggin thinkin to myself "What? This is like, basic functionality..."
FIX IT (Difficulty: Easy)
For those who compile manually (useful to users new to self hosting/home-labbing); this replicates the docker fix. Works on the following build.
Mattermost
Version: 10.6.1
Build Number: 13860096928
Build Date: Fri Mar 14 15:43:33 UTC 2025
Build Hash: 0572f0e376faaa63702aba05e6579a69f32e0f90
Build Enterprise Ready: true
then append
Should look like
Reload service
Verify
Google lead me here, where I read a rightly disgruntled conversation and I wanted to stand in agreement for what little this may matter. I also wanted to provide intricate details for those who are either new to self hosting mattermost and aren't yet quite acquainted/familiar with
the service. I appreciate those who shared the Docker env variables.
This will enable you to execute
Hope this helps.
This resolves the issue for me being just a dude hosting MM on my home lab so I can collaborate with my children; being forced to pay for a pre-existing service is quite mind blowing to me. I must admit that I'm new to Mattermost. But to my surprise, trying to do a group call yielded "Only available in DM Channel" or whatever had me scratching my noggin thinkin to myself "What? This is like, basic functionality..."
FIX IT (Difficulty: Easy)
For those who compile manually (useful to users new to self hosting/home-labbing); this replicates the docker fix. Works on the following build.
Mattermost
Version: 10.6.1
Build Number: 13860096928
Build Date: Fri Mar 14 15:43:33 UTC 2025
Build Hash: 0572f0e376faaa63702aba05e6579a69f32e0f90
Build Enterprise Ready: true
Code:
sudo nano /etc/systemd/system/mattermost.service
then append
Code:
Environment="MM_CALLS_GROUP_CALLS_ALLOWED=true"
Should look like
Code:
[Unit]
Description=mattermost
After=network.target
After=postgresql.service
BindsTo=postgresql.service
[Service]
Type=notify
ExecStart=/opt/mattermost/bin/mattermost
TimeoutStartSec=3600
KillMode=mixed
Restart=always
WorkingDirectory=/opt/mattermost
User=mattermost
Group=mattermost
LimitNOFILE=49152
Environment="MM_CALLS_GROUP_CALLS_ALLOWED=true"
[Install]
WantedBy=multi-user.target
Reload service
Code:
sudo systemctl daemon-reload
sudo systemctl restart mattermost
Verify
Code:
sudo systemctl show mattermost | grep Environment
sudo journalctl -u mattermost --no-pager | grep MM_CALLS_GROUP_CALLS_ALLOWED
Google lead me here, where I read a rightly disgruntled conversation and I wanted to stand in agreement for what little this may matter. I also wanted to provide intricate details for those who are either new to self hosting mattermost and aren't yet quite acquainted/familiar with
the service. I appreciate those who shared the Docker env variables.
This will enable you to execute
/call start` in group channelsHope this helps.
Last edited:

