I know I'm late to the upgrade game, as this is a Wowza Media Server 2.2.4 item.
I had an ORIGIN server running on Amazon EC2. I received a notification of degrading hardware, so I launched a new server and copied files over to the new server... swapped out the IP address, terminated the failing server, and all seemed to be running well. Over a dozen live streams, with auto-record, playing and load-balancing just fine across the ORIGIN and multiple EDGE instances.
But... about a week ago, all "cupertino" load balancing streams stopped. Load Balancing through my Flash modules seem to operate without issue. But I can not longer get anything to playback on iOS devices (or ROKU)... unless they have a direct path to the ORIGIN. The ORIGIN is also set up as an EDGE, for regular 24/7 access when I don't have extra EDGE servers running. So... direct m3u8 to the ORIGIN is not a problem with an iPhone -- but sending that iPhone through the load balancer produces nothing.
The church that I created this for just started using JWPlayer for Wednesday evenings... so all traffic through JWPlayer uses "cupertino" instead of RTMP... but I don't see how that could affect anything (they're not getting on the wowza server to change anything). So... the fault must be in something I did, or failed to do, when starting up the emergency replacement server. I know copy/pasting files from "conf" isn't always the best thing to do, but I was in a bind to get something else up and running.
Anyone have any ideas on what I should be looking at? I know that's a horribly open-and-wild question, but my brain is pretty fried right now so I'm just looking for any clues/pointers/suggestions that might point me somewhere to double-check the files.
Thanks! And sorry for posting an "old" server (2.2.4 - EC2) question on this 3.x forum.
David L Good