Running Mattermost?

Mattermost cluster drifting or plugins refusing to load? We fix it.

Mattermost pays off when a team needs real time chat without putting messages inside somebody else's SaaS, which is common in defence, regulated finance and government work. When the cluster nodes fall out of sync, the plugin marketplace returns errors on install, or push notifications silently stop reaching mobiles, the self hosted trade off starts showing.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

mattermost.log

still failing

What it is

Mattermost at a glance

Mattermost is an open source, self hosted messaging platform written in Go, originally created by a team at SpinPunch Studios and open sourced in 2015. It offers real time chat, threaded conversations, direct messages, file sharing, voice calls through plugins and integrations with the usual developer tools, deployed on your own infrastructure rather than as a SaaS.

The core is free and open source; the Team Edition and the Enterprise Edition add high availability clustering, LDAP and SAML authentication, compliance exports, advanced permissions and premium integrations. Mattermost is used heavily by organisations that cannot send messages to a third party service, including defence, intelligence and regulated finance.

Type
Self hosted messaging and collaboration platform
First released
2015 open source
License
Dual: MIT for core, commercial for Enterprise features
Maintained by
Mattermost, Inc.
Typically used for
Internal chat, DevOps ChatOps, regulated and air gapped environments, defence and public sector communications

The honest version

Mattermost pros and cons

No technology is all upside. This is where Mattermost earns its place and where it tends to cause trouble.

Where Mattermost is strong

  • Self hosted and open sourceThe core is MIT licensed and runs on infrastructure you control, so messages never leave your network, which is a hard requirement in many regulated environments.
  • Reasonable Slack like experienceChannels, threads, direct messages, mentions, emoji and basic search are present and familiar, which keeps user adoption low cost.
  • ChatOps integrationsIncoming webhooks, slash commands, bot accounts and plugins cover the DevOps use cases that are often why Mattermost was picked over SaaS alternatives.
  • Clustering for high availabilityThe Enterprise cluster mode distributes load and tolerates node failures, which keeps chat available during infrastructure events that would otherwise be noticed immediately.
  • LDAP, SAML and compliance exportsEnterprise features cover the authentication and audit requirements that regulated organisations need and that most SaaS chat tools do not expose.
  • On premise push notificationsA self hosted push proxy is available for organisations that cannot rely on the default Mattermost hosted push service, which matters in air gapped environments.

Where Mattermost bites

  • Operational burden is yoursUpgrades, backups, TLS certificates, database health, file storage and push servers are all on your team, which is work that a SaaS chat tool would absorb.
  • Plugin stability variesCommunity plugins are inconsistent in quality, and a panicking plugin can destabilise the server if auto restart is not configured carefully.
  • Mobile push setup is fiddlyApple and Google push credentials, certificate rotation and the proxy configuration are more involved than SaaS chat users expect, and silent push failures are common.
  • Search scale takes workThe default database search struggles with larger histories, and ElasticSearch integration is Enterprise only and introduces its own operational surface.
  • UI and feature polish trail SlackSome interactions, especially around workflows and automation, feel one generation behind Slack. For many regulated users this does not matter; for others it does.
  • Upgrades can break pluginsPlugin APIs evolve, and an upgrade to the next server version occasionally breaks plugins that have not been updated recently, which has to be rehearsed.

Sound familiar?

Common Mattermost problems we fix

The Mattermost problems that bring people to us, and what you have once each one is fixed.

plugin install failed: 403 Forbidden

Marketplace returns errors on install

Proxy blocking outbound HTTPS, a plugin that is only available on a higher licence, or a marketplace outage. We confirm the egress path and, where needed, install the plugin bundle from a local artifact.

Plugins installable in your environment

cluster: heartbeat missed

Cluster nodes drifting apart

Gossip is failing to converge, usually because of a firewall rule blocking the cluster port or a network blip that the health checks have not accounted for. We tighten the config and add alarms on heartbeat age.

Cluster converged and alerting

push notification server 502

Mobile push notifications silent

The proxy is misconfigured, the APNs certificate expired, or the push URL is pointed at the wrong environment. Users notice because messages do not wake them until they open the app.

Push notifications reliable on mobile

database migration failed: duplicate key

Upgrade fails on a migration

A unique constraint cannot be applied because historical data has duplicates, often from an older version that was less strict. We clean the duplicates in a controlled pass before re-running the migration.

Upgrades complete cleanly

LDAP sync completed with errors

LDAP sync is losing users

A duplicate email, a renamed user, or a group filter that no longer matches. Partial syncs leave orphaned accounts that confuse later audits.

LDAP sync clean and reconciled

SAML signature mismatch

SSO breaks after an IdP rotation

The identity provider rotated its signing certificate and Mattermost still trusts the old one. Logins start failing for everyone until the new certificate is loaded.

SAML trust restored

file storage error: s3 AccessDenied

File uploads failing

An IAM policy changed, a bucket was moved, or the Mattermost role lost a permission on a key prefix. Users see uploads fail without a clear message.

File storage reliable again

plugin panicked

A plugin takes the process down

An unchecked panic in a plugin bubbles up and the server restarts repeatedly. We disable the plugin, isolate the cause, and either patch it or pin to a known good version.

Server stable with plugins contained

What we do

Mattermost help, from rescue to platform upkeep

Call us for one broken cluster node, or let us own the Mattermost platform end to end.

Rescue
Clusters out of sync, plugins crashing the server, or mobile push gone quiet. We stabilise first and explain the root cause second.
Upgrade and migration planning
Server, database and plugin upgrades rehearsed on a copy of the cluster, with migrations reviewed against real data before the live run.
Cluster and HA setup
Multi node clusters configured with the right gossip, load balancing, session stickiness and database replication for the uptime target you actually need.
Authentication and SSO
LDAP, SAML and OIDC wired up with the tolerance for certificate rotation and group changes that long lived deployments need.
Push, search and storage
Push proxy, ElasticSearch and file storage configured so chat scales past the point where the default stack starts straining.
Managed Tech
Regular health checks on cluster state, plugin stability, SSO, push and storage, plus a hand on deck when an IdP rotation or an upstream bug takes chat down out of hours.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Mattermost alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Mattermost questions

Something else? Call+1 737 727 7327

Why would we pick Mattermost over Slack?

The honest answer is usually a compliance or sovereignty requirement that rules out sending messages to a third party service. Defence, intelligence, regulated finance, air gapped environments and large public sector tenders often require self hosted chat, and Mattermost is the mature open source option. For most other teams, Slack or Microsoft Teams will be easier to run.

Why are our mobile push notifications silent?

The common causes are an expired Apple push certificate, a push proxy pointed at the wrong environment, or firewall rules that block outbound traffic to the hosted push service. We check the certificate expiry, confirm the proxy is reachable from the server, and verify at least one test device receives a push before signing off.

How do we upgrade Mattermost safely?

Clone the production database and file store to a staging cluster, run the target version there, exercise the upgrade migrations and the plugins, and only schedule production once staging is clean. Skipping staging is where most of the painful Mattermost upgrade stories come from.

Can you take over an inherited Mattermost deployment?

Yes, and it is a common request. We document what is actually deployed, where the database and file storage live, which plugins are installed and from where, how authentication is wired, and bring the whole thing into a configuration we can review before changing anything.

How does Mattermost scale for a large user base?

Clustering, ElasticSearch for search, a tuned PostgreSQL or MySQL, a separate push proxy and object storage for files cover most deployments up to tens of thousands of users. Beyond that we look at read replicas, aggressive post retention and archive policies, which have operational implications you want to agree before enabling.

How much does Mattermost help cost?

The estimate is free. Tell us about the deployment, send us the server config and any failing logs, and we come back with a price and a short plan before anything is changed.

Free estimate

Mattermost cluster giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.