Yes we have noticed the exact same issue with the latest version of Wowza Server (4.7.3.01 (build 21295)). I have a open ticket with Jermaine Hemby (#267966). We’ve been going back and forth for about 3 weeks and sent tons of logs to Wowza. From his last email it sounds like Wowza has identified this as a bug and it will be fixed in the next version. Hopefully soon.
We have two time critical broadcasts to FB that use Stream targets to bounce the stream to FB and they often (70-80%) of the time error when the incoming stream shows up, and YES – other than one time when it did not work at all – the edit/save trick seems to re-request a new token from facebook which makes the target work properly for a while.
The worst part of it is that we have not been able to figure out a pattern here. Sometimes the edit/save thing works and all subsequent start/stops keep working. Sometimes the edit/save works once and when the stream stops and restarts the target goes into error mode again – requiring a edit/save kick.
Also worth mentioning is the fact that through some voodoo (literally) this process has been running flawlessly without error for the past 3 days (knock on wood)…but I’ve seen enough “error” states on the FB stream target for the past 3-4 weeks to know that there is a serious bug in the code somewhere…hopefully a fix will be released soon…getting really tired of baby sitting stream targets to make sure they don’t error.
Thanks for sharing, even though you don’t have a contract…atleast I now know I’m not the only one having the issue.
P.S. Just noticed that Server 4.7.4 is out…going to give it a try now…cross your fingers :-).