Connecting to AutoCast takes about ten seconds. Open the TuneTracker Go! shell, log in once, click the CastAway tab, and you're on the air.
https://www.tunetrackersystems.com/ttgo.WXGZ) and PIN, then click Log In.The Connect button does double duty — it establishes the live audio stream and unlocks browser audio (browsers require a user click before playing sound). That's why CastAway doesn't auto-connect on tab open.
The TuneTracker Go! shell remembers your station code and PIN. The next time you visit tunetrackersystems.com/ttgo, the shell loads straight to the tabs — no login screen. Click the CastAway tab and then click the Connect button. You're back in business.
The status bar at the bottom of the screen shows your connection state:
| Indicator | Meaning |
|---|---|
| Green dot | Connected to AutoCast and authenticated |
| Gray dot | Disconnected — click Connect to retry |
| "Connecting..." | Establishing the connection — wait a moment |
| "Authentication failed" | Wrong PIN — log out of the shell and log back in with the correct PIN |
If your internet connection drops — or even if the relay restarts — CastAway automatically reconnects and rebuilds the full session. That means both the WebSocket control channel and the WebRTC audio stream are re-established automatically. No page reload needed. You don't have to click anything or re-enter your credentials.
CastAway retries every few seconds in the background. When the connection comes back, everything resumes — decks, buttons, program log, audio monitoring. It's designed for the reality of remote broadcasting, where WiFi hiccups at a county fair are just part of the job.
AutoCast keeps running at the station regardless of CastAway's connection state. Your station never goes silent because of a network hiccup on your end.
You don't have to think about this to use CastAway, but it's nice to know what's happening under the hood. When you log in to TuneTracker Go!, your browser opens an encrypted connection to TuneTracker's relay server. Meanwhile, the TuneTracker Go! helper running at the station has its own outbound connection to that same relay. The relay introduces the two — your browser and the station's helper — and from then on, messages and audio flow back and forth between them with the relay in the middle.
Because both sides are making outbound connections, neither side needs port forwarding, a static IP, or any router configuration. It works on home WiFi, hotel WiFi, cellular data — anything that can reach the public internet.