This comment suggest that the way we are exposing the turn server is not the optimal one: #11 (comment)

We should think about the option to ask for a secondary domain for the turn server, and maybe, if it is not provided, use this trick. Or maybe we can make it mandatory.

First step in the process listed here: https://docs.mattermost.com/install/installing-mattermost-omnibus.html results in an error for me on a fully up-to-date copy of Ubuntu 20.04. I recently removed a standard enterprise edition from my /opt directly via sudo rm -rf mattermost/, if that makes a difference.

I ran this command: curl -o- https://deb.packages.mattermost.com/repo-setup.sh | sudo bash and it seemed to not download anything. I tried it multiple times (showed no progress), and switched broke it into 2 steps:
- curl -o- https://deb.packages.mattermost.com/repo-setup.sh
- sudo bash repo-setup.sh

This downloaded the file, but when executing the repo-setup.sh script, I get this error:

bash: line 88: curl: command not found

Full execution printout:

Executing: /tmp/apt-key-gpghome.5dT6ekYCDY/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys ABF5BD827BD9BF62
gpg: key ABF5BD827BD9BF62: "nginx signing key <[email protected]>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
Hit:1 https://updates.signal.org/desktop/apt xenial InRelease
Get:2 http://packages.microsoft.com/repos/code stable InRelease [10.4 kB]                     
Get:3 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]                     
Hit:4 http://us.archive.ubuntu.com/ubuntu focal InRelease                                     
Hit:5 https://repo.protonvpn.com/debian stable InRelease                                      
Get:6 https://packages.microsoft.com/repos/vscode stable InRelease [3,959 B]                  
Get:7 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]                    
Get:8 http://packages.microsoft.com/repos/code stable/main arm64 Packages [77.7 kB]           
Get:9 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB]                  
Hit:10 https://nginx.org/packages/ubuntu focal InRelease         
Get:11 https://packages.microsoft.com/repos/vscode stable/main amd64 Packages [292 kB]
Fetched 720 kB in 1s (558 kB/s)    
Reading package lists... Done
N: Skipping acquire of configured file 'nginx/binary-i386/Packages' as repository 'https://nginx.org/packages/ubuntu focal InRelease' doesn't support architecture 'i386'
'universe' distribution component is already enabled for all sources.
repo-setup.sh: line 88: curl: command not found

Very odd, considering I just used curl to download the file :S

Hoping it was just a non-breaking glitch, I tried running the next step:

sudo apt install mattermost-omnibus

But this results in the following error:

E: Unable to locate package mattermost-omnibus

How do I address this curl command not found issue?

Summary

Updating a Mattermost-Omnibus install on a bare-metal server with multiple subdomains deletes the (edited) default.conf in nginx conf.d folder, changing the default forward from www to the mattermost subdomain.

Steps to reproduce

Updating Mattermost using "apt upgrade"

Expected behavior

Other configurations should not be altered, not to mention removed without asking.

Observed behavior (that appears unintentional)

Ansible update script seen using "absent" state after new cert was requested.
Relevant syslog:
Jul 19 21:13:46 machinename python3[1071217]: ansible-file Invoked with path=/etc/nginx/conf.d/default.conf state=absent recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S _original_basename=None _diff_peek=None src=None modification_time=None access_time=None mode=None owner=None group=None seuser=None serole=None selevel=None setype=None attributes=None content=NOT_LOGGING_PARAMETER backup=None remote_src=None regexp=None delimiter=None directory_mode=None unsafe_writes=None
Jul 19 21:13:46 machinename python3[1071242]: ansible-systemd Invoked with name=nginx state=restarted daemon_reload=False daemon_reexec=False no_block=False enabled=None force=None masked=None user=None scope=None

Possible fixes

Remove/change "absent" keyword for default.conf or alternatively give option to select.
https://github.com/mattermost/mattermost-omnibus/blob/2c593aac57d4c8e0af5275cc4dcd88c7d78b5cd1/mmomni/ansible/playbooks/reconfigure.yml#L61C8-L61C8

I spent hours trying to get my Docker based MM deployment to work (cert.pem error, like many, but I followed your instructions to the letter on a fresh Ubuntu) and then I found the references to Omnibus as a quicker and more reliable path.

Unfortunately, the Install instructions at don't explains steps needed to do this. The only other MM article I could find on it includes a bash command that fails for me (bash: line 74: add-apt-repository: command not found). Where can I find a documentation that I can use?

Hey guys,

I suddenly have the following error on my omnibus installations:

─➤  apt update
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://apt.postgresql.org/pub/repos/apt focal-pgdg InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:4 https://nginx.org/packages/ubuntu focal InRelease
Hit:5 http://archive.ubuntu.com/ubuntu focal-security InRelease
Hit:6 https://deb.packages.mattermost.com focal InRelease
Err:6 https://deb.packages.mattermost.com focal InRelease
  The following signatures were invalid: EXPKEYSIG F8F2C31744774B28 Mattermost Build <[email protected]>
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.packages.mattermost.com focal InRelease: The following signatures were invalid: EXPKEYSIG F8F2C31744774B28 Mattermost Build <[email protected]>
W: Failed to fetch https://deb.packages.mattermost.com/dists/focal/InRelease  The following signatures were invalid: EXPKEYSIG F8F2C31744774B28 Mattermost Build <[email protected]>
W: Some index files failed to download. They have been ignored, or old ones used instead.

Did you change you signing key?
I tried to run the https://deb.packages.mattermost.com/repo-setup.sh again, but same is happening.

Our install using the Omnibus deployment asks us to upgrade to release 6.1, saying it's 'easy' and 'takes 5 minutes', but this seems incorrect as we'd need to redeploy entirely to upgrade to 6.1 as there's no update on the Omnibus packages.

The latest automated build failed. Is this project and mattermost omnibus still being maintained? I was really impressed by the promised setup and maintenance simplicity. But now I'm a bit worried I might invest in deploying a deprecated and inactive solution. #92 also suggests that install documentation is not up-to-date.

I don't want to sound demanding, I just want to know if mattermost omnibus is still a viable way to deploy mattermost with an upgrade path for the foreseeable future.

One of the lines in the installation script deletes all directories that are not part of the standard build. If you put something important there, it will be quietly lost during an upgrade. Instead the offending files could at least be moved to /tmp and the user warned.

Does it cause the missing 8.1.6 package?

I tried the following origin, but it doesn't seem to work:

# /etc/apt/apt.conf.d/50unattended-upgrades
Unattended-Upgrade::Allowed-Origins {
        "${distro_id}:${distro_codename}";
        "${distro_id}:${distro_codename}-security";
        // Extended Security Maintenance; doesn't necessarily exist for
        // every release and this system may not have it installed, but if
        // available, the policy for updates is such that unattended-upgrades
        // should also install from here by default.
        "${distro_id}ESMApps:${distro_codename}-apps-security";
        "${distro_id}ESM:${distro_codename}-infra-security";
//      "${distro_id}:${distro_codename}-updates";
//      "${distro_id}:${distro_codename}-proposed";
//      "${distro_id}:${distro_codename}-backports";
        "deb.packages.mattermost.com:${distro_codename}";
};

Hi,
I have 2 mattermost servers running with mattermost-omnibus on ubuntu.
The last update was for 6.4.0. But the https://deb.packages.mattermost.com repo does not give any more updates.

From your website critical security fixes were released within 6.4.2 and 6.5.0.

apt update always says mattermost is up to date. Do you guys still release new versions using omnibus+deb?

Hello,

Doing curl -o- https://deb.packages.mattermost.com/repo-setup.sh | sudo bash
as suggested ends up in time out

I guess it has to do with being behind a firewall; doing
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys ABF5BD827BD9BF62 works, but gets me nowhere...

Help!!! thanks.

The repo key ( https://deb.packages.mattermost.com/pubkey.gpg ) expired yesterday and the repo needs a resign.

/etc/apt/trusted.gpg.d/mattermost.gpg
-------------------------------------
pub   rsa2048 2017-03-27 [SC] [expired: 2024-04-06]
      A1B3 1D46 F0F3 A10B 02CF  2D44 F8F2 C317 4477 4B28
uid           [ expired] Mattermost Build <[email protected]>

While following the https://docs.mattermost.com/install/installing-mattermost-omnibus.html instructions on installing Omnibus. The packages pulled with mattermost doesn't include postgresql auto-magically.

I had to run '$ apt install postgresql' manually to get the package.

BACKGROUND:
We have MariaDBl installed with previous MM source code installation. After finding out that postgresql is required, we backed away from Omnibus installation/upgrade process. Discovered that upgrade path is not clean from MariaDB.)

Does it cause the missing 8.1.13 package?