Stuck on "Connecting..."
Symptom: The app shows a connecting state that never resolves.
Check Internet
Open a web browser and verify you have internet access. If not, fix your network connection first.
Check Server Status
The CrewTalk relay servers may be undergoing maintenance. Check for any service announcements.
Force Restart
Close CrewTalk completely (remove from app switcher), then reopen it. Navigate to your hub.
Check Network Restrictions
If you're on a corporate/hotel/school network, it may block non-standard ports. Try switching to cellular data.
Repeated Disconnects
Symptom: You connect but keep getting disconnected every few minutes.
Common Causes
Battery Optimization (Android)
The most common cause. Android kills background apps to save battery.
- Go to Settings > Apps > CrewTalk > Battery > Unrestricted
- See Background Operation for detailed instructions
Unstable Network
Frequent network changes (Wi-Fi to cellular, weak Wi-Fi zones) trigger disconnects.
- Stay on one network when possible
- Move closer to your Wi-Fi access point
- Consider a dedicated Wi-Fi network for the production
Token Expiration
Firebase auth tokens expire after 1 hour. CrewTalk normally refreshes them proactively, but if the refresh fails:
- Sign out and sign back in to get a fresh token
- This is rare but can happen if the device clock is significantly wrong
Make sure your device's date and time are set to automatic. Firebase authentication tokens are time-sensitive, and a wrong device clock can cause auth failures.
Firewall Blocking
Symptom: Can't connect at all on certain networks (works fine on cellular).
CrewTalk's Network Requirements
| Service | Protocol | Port | Notes |
|---|---|---|---|
| Audio relay | TLS/TCP | 8888 | May be blocked on restrictive networks |
| Messages | WSS | 443 | Usually allowed (standard HTTPS port) |
| Firebase | HTTPS | 443 | Usually allowed |
Solutions
- Switch to cellular — Most reliable if available
- Request port access — Ask IT to whitelist outbound TCP port 8888
- Use a different network — Personal hotspot or production Wi-Fi
- VPN — A VPN can bypass port restrictions (but may add latency)
VPN Interference
Symptom: Audio or messaging stops working when VPN is active.
Why VPNs Can Cause Issues
- VPNs route traffic through additional servers, adding latency
- Some VPNs block non-standard ports
- Split tunneling configurations may route CrewTalk traffic incorrectly
Solutions
- Disable VPN when using CrewTalk (preferred)
- Configure split tunneling to exclude CrewTalk traffic
- Use a VPN that allows port 8888 outbound
VPNs add at least 20-50ms of latency. For PTT audio, this can push connection quality from Good to Fair. If real-time audio is critical, disable VPN while using CrewTalk.
WebSocket-Only Issues
Symptom: PTT audio works but messages don't arrive (or vice versa).
Audio and messaging use separate connections:
- Audio = TLS/TCP to port 8888
- Messages = WebSocket to port 443
If only one is failing:
- The other connection's port may be blocked
- One server may be temporarily down while the other is fine
- Try leaving and re-entering the hub to reset both connections