Ecamm can't connect to the Twitch destination, or Go Live fails

Updated

If Ecamm cannot start streaming to the Twitch destination, the usual cause is that Ecamm is not reaching CommentMuxer.

Steps

  1. Is CommentMuxer open and running? Check the menu bar icon, and that the App line says "Running". Ecamm cannot reach it if the app is not running.
  2. Is Muxing on? The Mac setup line must say "Ready: Twitch names point here and the certificate is trusted". If not, press Start Muxing. See The one-time Mac setup.
  3. Quit and reopen Ecamm once after the setup. Ecamm reads the Mac's settings when it opens.
  4. Choose the right server. In the Twitch destination, pick the single server named CommentMuxer Local.
  5. Sign in to Twitch in Ecamm again if Ecamm asks. A Twitch sign-in can expire, and Ecamm handles it with Twitch. See Add the Twitch destination in Ecamm.
  6. Is the app locked? If it shows a lock card, Ecamm may not get an answer. See What the lock messages mean.
  7. Press Recheck in Status and read the lines.

What Ecamm needs from us

When Go Live is pressed, Ecamm asks the local Twitch addresses for a stream key, sets the channel title and publishes video to a local address. Without a working local endpoint, Ecamm reports a failure to start streaming. We saw this early in testing when no local endpoint existed.

Real Twitch

If you want to use the real Twitch in Ecamm, press Stop Muxing. While Muxing is on, real Twitch is not reachable from this Mac.

Other causes

  • Port 443 is held by something else. See Port 443 is already in use.
  • Your Mac's security software or a VPN rewrites network traffic. We have not tested with these.

If that didn't work

Contact support with the exact words Ecamm shows and what the three Status lines say.

Was this helpful?

Still need help? Contact support

Related articles

Back to support