Wowza Community

Facebook stream targets no longer working (nov 2020)

Hello,
the title says it all.
We’re seeing the issue on three different Wowza servers, with about 15 different FB accounts.
Tested on wowza server versions: 4.7.7, 4.7.8, 4.8.5, 4.8.5.05 (linux ubuntu server 16.4, 18.4 )
The login to FB from the target works.
The target waits for a stream input fine; but as soon as a stream gets in, the target errors.
The log points at some deprecation issue with wowza implementation of FB api. Here are the relevant log messages in order of time received:
Warning message 1:
PushPublishFacebookUtil.detectAuthError[createLiveVideo]: Authentication issue. [OAuth “Facebook Platform” “invalid_request” “(#12) save_vod is deprecated”]
Warning message 2:
PushPublishFacebookUtil.detectAuthError[createLiveVideo]: Please Edit the stream target in WSEM and re-login to Facebook to acquire a new access token and then Save the target
Error message:
PushPublishFacebookHandler.FBMonitor.run(target-name:app_name/definst/StreamFB15) : com.wowza.wms.pushpublish.protocol.facebook.FacebookAuthorizationException|at com.wowza.wms.pushpublish.protocol.facebook.PushPublishFacebookUtil.a(PushPublishFacebookUtil.java:559)|at com.wowza.wms.pushpublish.protocol.facebook.PushPublishFacebookUtil.createLiveVideo(PushPublishFacebookUtil.java:468)|at com.wowza.wms.pushpublish.protocol.facebook.PushPublishFacebook.a(PushPublishFacebook.java:465)|at com.wowza.wms.pushpublish.protocol.facebook.PushPublishFacebook.f(PushPublishFacebook.java:15)|at com.wowza.wms.pushpublish.protocol.facebook.PushPublishFacebook$FBMonitor.run(PushPublishFacebook.java:185)|

We followed the pointers in the second warning message to no avail:

  • reconnecting the target to FB does not fix the issue;
  • creating a new target does not either.

I’ll open a ticket. But I expect the issue to be widespread since we’re 3 people who have the issue on 3 different servers.

Same problem here with PushPublishFacebookUtil.detectAuthError[createLiveVideo]: Authentication issue. [OAuth “Facebook Platform” “invalid_request” "(#12) save_vod is deprecated "]

The origin is a change in the Facebook’s API, so Wowza have to develop a fix.

I can’t find the workaround about how to send a rtmps to Facebook. At least not a tutorial step by step. Wowza Team should create that tutorial about it (I think that they have deleted the one that I saw time ago).

rtmps stream target works fine though
@Rub_Loz you have to add sendSSL true; see discussion here How to Streaming Facebook RTMPS in Next month

Thanks, that solved my problem with the rtmp to facebook.

Now wait until the wowza team launch a update that solve the stream target to facebook

Hi everyone, this issue was a result of FB deprecating a parameter that broke our stream target workflow and was not such an easy fix when so many variables and CDNs are involved, so thank you for your patience while the Engine team worked on this beta release.

The alert and workaround was posted on the wowza status alert page. If you have not subscribed to that, please do so you get an email when there is an issue that can affect you.

Just click on the top of the page in this link to subscribe.
https://wowza-streaming-engine.statuspage.io/

Having said that, the beta version to fix this FB issue is NOW AVAILABLE.

Updating to Wowza Streaming Engine 4.8.7b requires a custom packaged version of OpenJDK Java SE JRE 9.0.4. For more information, see Wowza Streaming Engine support for Java 9-12.

Please go HERE to to access the beta release.

This is an updater download. Click on Download

  • Please note: The installer version is in final testing and will also be available soon.
1 Like

Also, If you need to update your Java for this beta release, you can can configure it for Java 9-12 here:

https://www.wowza.com/docs/wowza-streaming-engine-update-to-java-9

The latest version of Engine does require a MINIMUM of Java 9, but it does support 9-12.

Fix applied. All good here. Thanks for the update @Rose_Power-Wowza_Com

@Rose_Power-Wowza_Com We here also updated and all good.

Great news! Appreciate the feedback.

I get a cannot validate installed version error:

Verifying running as administrative user
Verifying Java 9 or greater is available
Found valid ‘WMSJAVA_HOME’ value: ‘C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.7.7\jre’
Locating Wowza Streaming Engine installation directory
Running Wowza Streaming Engine update installer
Path: C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.7.7\updates\WowzaStreamingEngine-Update-4.8.7b\windows…

This will update your installation at: C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.7.7

Currently installed version : Wowza Streaming Engine 4.8.5.05 - Build 20201006161917

This will update your installation to : Wowza Streaming Engine 4.8.7b - Build 20201103113343

Are you sure you want to continue? (y/n)
y
Changes in Wowza Streaming Engine 4.8.7b Build 20201103113343

Press Enter to continue.

Detected operating system: windows
Checking file versions.
Cannot validate installed version. Check log for details. Stopping update process.

C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.7.7\updates\WowzaStreamingEngine-Update-4.8.7b\windows>

The log file entries are:
2020-11-06 16:32:40-main-com.wowza.updatetool.UpdateManager:Error: File C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.7.7\lib\commons-codec-1.14.jar Version (1.14) is incompatible with this update. Minimum required version: 3.4
2020-11-06 16:32:40-main-com.wowza.updatetool.UpdateManager:Error: File C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.7.7\lib\commons-logging-1.2.jar Version (1.2) is incompatible with this update. Minimum required version: 3.4

I renamed those two files to end in -3.4 and it worked…

scary!

Hi,
We did this:
we downloaded the Beta 487b version
after unpacking the wms-pushpublish.jar file we uploaded to the “lib” / replace /
Wowza restart
and … everything from FB works
best regards
D

After installing 4.8.7 beta, WowzaStreamingEngineManager is failing to start complaining about the packaged java version.

./startmgr.sh

Error: A JNI error has occurred, please check your installation and try again
Exception in thread “main” java.lang.UnsupportedClassVersionError: launch/Main has been compiled by a more recent version of the Java Runtime (class file version 53.0), this version of the Java Runtime only recognizes class file versions up to 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:495)

Going to attempt to use a later version of JAVA. Will report back.

UPDATE: This was an error in the installation path and was using the default WowzaStreamingEngine directory which contains the old JAVA Runtime for 4.8.5.05. Sorry about this post.