Hi, I encountered a weird bug – when streaming to two custom-added RTMP channels/destinations (one on my home network and one remote), the tcUrl in connect RTMP message was invalid: rtmp://[address]:1935//[stream key] (notice missing app between //). Also, flashVer field was missing from this message. This makes the whole message non-compliant with the RTMP spec, so the server rejects the connection.
Interestingly, this problem does not occur when streaming to a single destination (disabling either of them).
I'll be happy to help with investigating the issue further and hopefully getting it fixed.
Edit: I've tried to append /app to server address manually when configuring the channel, but this in turn results in PRISM not appending the stream key to tcUrl 👀
Hi, I encountered a weird bug – when streaming to two custom-added RTMP channels/destinations (one on my home network and one remote), the
tcUrlinconnectRTMP message was invalid:rtmp://[address]:1935//[stream key](notice missingappbetween//). Also,flashVerfield was missing from this message. This makes the whole message non-compliant with the RTMP spec, so the server rejects the connection. Interestingly, this problem does not occur when streaming to a single destination (disabling either of them). I'll be happy to help with investigating the issue further and hopefully getting it fixed.Edit: I've tried to append
/appto server address manually when configuring the channel, but this in turn results in PRISM not appending the stream key totcUrl👀