Live stream OBS -> flashphoner -> twitch not working.

[KaranBhansali91]

Hi,

I am using https://docs.flashphoner.com/display/WCS52EN/Using+OBS+Studio link to setup live stream from OBS studio. The following screenshot shows error.

 

[Max]

Good day.
First, please make sure the stream is published on WCS using /stream/find REST API query: /stream/find
Then, please make sure you've set server parameters as described here: Periscope and Twitch
If all seems to be correct. please collect a report as described here and send using this form.

 

[KaranBhansali91]

Hi,

We publish stream from OBS to our platform. The live stream can be seen on our platform. As we call the REST API push/startup it shows 500 internal server error, the functionality stopped working on 30th April 2022

 

[Max]

Unfortunately, the logs you've provided contains no stream publising (via RTMP or WebRTC) and no /push/startup call. So the logs have no any useful information to detect the issue.
Please collect the report exactly as described in this doc: Collect debug logs and traffic dump
1. Enable client debug logging

client_log_level=DEBUG

and restart WCS
2. Reproduce a problem
3. Collect a report

cd /usr/local/FlashphonerWebCallServer/tools
sudo ./report.sh --sysinfo --conf --tar

4. Get the report file /usr/local/FlashphonerWebCallServer/report/report-2022-xx-xx-xx-xx-xx.tar.gz and send it using this form.
If you cannot collect a report properly, please provide SSH access to the server and RTMP republishing credentials (ingest point URL and stream key), and we try to reproduce the issue on your server. Use this form to provide all the required data.

 

[Max]

We checked the report. The problem is not reproducing with your /push/startup request parameters in the latest WCS build 5.2.1190:

POST /rest-api/push/startup HTTP/1.1
Host: localhost:9091
Content-Type: application/json
Content-Length: 154

{
 "rtmpUrl":"rtmp://*****.**********.live-video.net/app/live_*******_******************",
 "streamName":"test",
 "rtmpTransponderFullUrl":true
}

RTMP connection is successfully establishing and media traffic is sent to RTMP ingest point.
So we recommend to update WCS and test again.
Also, note that Twitch republishing requires the following server settings:

rtmp_transponder_full_url=true
rtmp_transponder_stream_name_prefix=
rtmp_flash_ver_subscriber=LNX 76.219.189.0
rtmp_transponder_send_metadata=true

Seems like you did not set the last parameter.
About your server configuration. You have 32 vCPUs and 130 Gb RAM, but using default Java heap settings of 1 Gb. This may be not enough because you're using stream mixer, so it may cause the problem mentioned in this topic. We recommend to allocate a half of RAM available:

-Xmx64g
-Xms64g

We also recommend to set up The Z Garbage Collector (you already have Java 14 where ZGC is supported, so you don't need to update JDK).