You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue Summary:
Encountering issues with Mumble server on AWS installation.
Installation Details:
Used the zero-touch installer for FreeTAKServer on a T3 medium instance with 30 GiB.
Problem Description:
While FreeTAKServer is running, Mumble server appears to be disabled.
Connection issues observed despite opening all ports on AWS (both inbound and outbound).
Checked configuration settings in config.py and FTSConfig.yaml.
Verified that necessary ports are open on AWS and Ubuntu.
Troubleshooting Steps:
Attempted advanced installer for Mumble (wget -qO - bit.ly/ftsadvancedinstall | sudo bash -s -- --mumble).
Restarted service, checked firewall, and tried without firewall.
Used WireGuard to confirm the device is attempting to communicate with the server.
Additional Information:
Able to connect Android devices to the FreeTAKServer.
WireShark shows phone attempting to communicate via Mumble server port, but no response.
Attempts to Resolve:
Mumble service remained disabled despite attempts to enable it (sudo systemctl enable mumble-server.service).
Outcome:
Mumble server remains disabled, and connection issues persist.
Next Steps:
Requesting assistance in resolving the Mumble server issue.
Opened all ports on AWS and Ubuntu, but issue persists.
Screenshots:
Environment Details:
Operating System: Ubuntu
FreeTAKServer Version: latest as of 24/01/2024
AWS Instance Type: T3 medium
Other relevant details: Ubuntu 22.04
The text was updated successfully, but these errors were encountered:
Issue Summary:
Encountering issues with Mumble server on AWS installation.
Installation Details:
Problem Description:
Commands Used:
Configuration Details:
Troubleshooting Steps:
Additional Information:
Attempts to Resolve:
Outcome:
Next Steps:
Screenshots:
Environment Details:
The text was updated successfully, but these errors were encountered: