When running a similar command trying to use tls as indicated in the
documentation, the server side doesn't seem quite right, though no error,
and the client just fails with a "Protocol not found" error.
On Fri, Jul 31, 2015 at 12:24 AM, Moritz Barsnick <[hidden email]> wrote:
> On Thu, Jul 30, 2015 at 14:46:30 -0700, Rony Pony wrote:
> > What am I doing wrong?
> You're not showing us the complete, uncut console output from your
> If I try to reproduce the, the server seems fine, and the client shows
> h264 errors, but certainly not an unknown protocol.
> ffmpeg-user mailing list
> [hidden email] > http://ffmpeg.org/mailman/listinfo/ffmpeg-user >
Ok so finally figured things out. Protocol not found indeed was happening
because TLS was not supported in the ffmpeg version I was using (2.6.3).
Once I updated to the latest snapshot, it then worked good (except video
goes slow for a few seconds, and then all starts going well as expected).
Am 19.07.2016 um 14:40 schrieb mohamed:
> hello, I using the same method and I've generated the .crt and .key file
> using openssl but it's not working, could you tell me how generated these
> files please
nobody has a clue what you are talking about
what about provide input and uncutted output of what you are doing
I am sorry about that, but I've already generated these files using openssl
here is my ffmpeg cmd :
$ ffmpeg -r 24 -s 800x600 -f video4linux2 -i /dev/video0 -c:v libx264 -f
flv "tls://192.168.1.11:1234?listen&cert=server.crt&key=server.key" -tune
It generates this error:
assign requested address"
It works only with localhost.
another question please, are there any way to use tls/ssl with ffserver ?
(google wasn't helpful)