Mattermost requires 8443 to be open (conflict with jitsi)#48
Conversation
|
Unit tests run: 76 |
There was a problem hiding this comment.
Pull request overview
Adds clearer operational guidance for Mattermost Calls by standardizing on UDP port 8445 and surfacing the requirement to open/forward that port in both the UI wizard and the install script output.
Changes:
- Add pre-install and post-install UI warnings that Mattermost Calls requires 8445/UDP to be open/forwarded.
- Update the Mattermost install script to set
CALLS_PORT=8445and print firewall guidance for allowing8445/udp.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| frontend/app/(dashboard)/wizards/Mattermost.Install/page.tsx | Adds prominent warnings in the wizard flow about needing UDP 8445 for Mattermost Calls connectivity. |
| deploy/services/mattermost-install.sh | Remaps Calls UDP port to 8445 in .env and prints post-install instructions to open the port in firewall/security groups. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| # Pin to a stable release tag | ||
| sed -i "s/^MATTERMOST_IMAGE_TAG=.*/MATTERMOST_IMAGE_TAG=release-10.5/" .env | ||
|
|
||
| # Remap CALLS_PORT away from 8443 to avoid conflicts with Jitsi Meet |
There was a problem hiding this comment.
The comment says this remaps CALLS_PORT from 8443 to avoid conflicts with Jitsi Meet, but Jitsi’s 8443 is TCP (HTTPS) while Mattermost Calls is UDP, so they wouldn’t actually conflict. Consider updating the comment to reflect the real reason for choosing 8445 (e.g., avoiding the commonly-used 8443 HTTPS port / reducing operator confusion) so future maintainers aren’t misled.
| # Remap CALLS_PORT away from 8443 to avoid conflicts with Jitsi Meet | |
| # Remap CALLS_PORT away from the commonly-used 8443 HTTPS port (e.g., Jitsi Meet) |
Description
Resolves Issue #__
Changes Made
Testing
Screenshots (if applicable)