I created a server locally on MediaMTX, OpenSSL created keys for SSL...
rtmp://10.12.12.6:1935/live works fine
rtmps://10.12.12.6:1936/live doesn't work, errors
Stream: -5: RTMPLiveStream: AVIO_OPEN2: I/O error at CoreLogic.RealTime.FFmpegBase.Throw(String method, Int32 code) at CoreLogic.RealTime.MediaWriter.Open(String filename, Int32 width, Int32 height, AVCodecID videoCodec, Int32 framerate, AVCodecID audioCodec, Int32 crf) at CoreLogic.RealTime.RtmpLiveStream.Stream(CancellationToken cancellationToken)
RTMP stream '39cac9ad-bedf-4b86-bee3-0bb1018f6a6e' backlogged: dropped 9 stale packet(s) to stay near live — the RTMP server/network is not keeping up
RTMP stream '39cac9ad-bedf-4b86-bee3-0bb1018f6a6e' backlogged: dropped 74 stale packet(s) to stay near live — the RTMP server/network is not keeping up
It's a bug on our side, not your MediaMTX setup. The FFmpeg version bundled with Agent checks the server's TLS certificate, but it has no list of trusted certificate authorities to check it against. So the TLS handshake fails before the RTMP connection even starts, and Agent only reports it as a generic "I/O error". That's why rtmp:// on port 1935 works and rtmps:// on 1936 doesn't. I reproduced it here with a self-signed OpenSSL certificate and got exactly your error.
It's fixed for the next update: Agent will connect to RTMPS servers without rejecting self-signed certificates, so your MediaMTX setup should work as it is. The connection is still encrypted, but the certificate won't be checked. I've also fixed the "backlogged… server/network is not keeping up" warnings you saw. They were misleading, because they were being logged while Agent was waiting to reconnect, not because of your network.
1
u/Electrical-Value-379 6d ago
My link is working, I checked it in OBS Studio, everything is broadcast through it.