I’ve got a brand new mattermost installation, and I’m stuck after following the install guide. The “chat” interface (don’t have a better name for it) refuses to finish loading, while trying to use the domain name.
The cloud provider I’m on is set to block all connections, but allow :80, and :443 from Cloudflare IPs. Internal access is through overlay VPN. I can access the MM application & system console over the same VPN (i.e. by private ip address) on :8065. The failure seems to be limited only to accessing over the domain name over :80/:443 (which means: through cloudflare over SSL, using nginx as a reverse proxy).
A video demonstrating the behavior is available here:
I’ve followed the instructions available here: Installing Mattermost on Debian Buster — Mattermost documentation, only deviating where necessary for credentials; commands have been copy/pasted for the most part.
I’m installing this on a Debian-11 distribution. Host-to-cloudflare TLS is provided by let’s encrypt. Cloudflare’s SSL mode is set to strict.
The machine this is installed on is also hosting an instance of Akkoma, the Akkoma instance is hosted at: https://omglol.fun, and I would like the mattermost instance to be running from: https://mm.omglol.fun. Akkoma lived on the server first, and still works flawlessly.
One thing that may be confounding is the following routings:
https ://omglol.fun/api/v1… → should route to akkoma
https ://mm.omglol.fun/api/v[0-9]… → should route to mattermost
Honestly, I’m not entirely sure this is a mattermost issue, but maybe an issue were I don’t understand nginx perfectly.
MM’s nginx config
Akkoma’s nginx config
There is some extremely strange behavior visible in the error log.
- There are references to an ip (10.10.10.2) – I have no idea where this comes from
- It’s clear there’s some cross pollenation between mm.omglol.fun and omglol.fun resources
If someone wouldn’t mind throwing an idiot a bone; I would really appreciate it.