Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ffmpeg: tls: Creating security context failed (0x80090302) #4605

Closed
nexional opened this issue Jul 13, 2017 · 20 comments
Closed

ffmpeg: tls: Creating security context failed (0x80090302) #4605

nexional opened this issue Jul 13, 2017 · 20 comments

Comments

@nexional
Copy link

nexional commented Jul 13, 2017

mpv version and platform

mpv-x86_64-20170708-git-7c1db05.7z, Windows 7 Professional 64 bit

Reproduction steps

Open any video stream link using command line -
mpv [streaming-file-link]
e.g.
mpv -v -v -v --log-file=log.txt "https://server.ferrante.me/shared/index.php?dir=iTunes/Home%20Videos/&file=35017Ferrante.m4v"

Expected behavior

It's supposed to open the stream.

Actual behavior

Fails with error -
ffmpeg: tls: Creating security context failed (0x80090302)
(I can play the movie directly in the browser but mpv fails to load it giving the "tls" error)
Also tried mpv with --no-config option but still the same error.

Log file

log.txt

Sample files

attached mpv.conf file as well in zip form -
mpv.zip

@mc4man
Copy link

mc4man commented Jul 13, 2017

@nexional
Copy link
Author

nexional commented Jul 14, 2017

Same error with "--ytdl=no" or "--no-ytdl" as well :(

/cygdrive/c> mpv --ytdl=no https://server.ferrante.me/shared/iTunes/Home%20Videos/35017Ferrante.m4v
cplayer: Auto-loading profile 'protocol.https'
cplayer: Playing: https://server.ferrante.me/shared/iTunes/Home%20Videos/35017Ferrante.m4v
ffmpeg: tls: Creating security context failed (0x80090302)
stream: Failed to open https://server.ferrante.me/shared/iTunes/Home%20Videos/35017Ferrante.m4v.
cplayer:
cplayer:
cplayer: Exiting... (Errors when loading file)

@wiiaboo
Copy link
Member

wiiaboo commented Jul 14, 2017

FFmpeg can't read it either, nor curl, so it seems like an issue with the server.

@CounterPillow
Copy link
Contributor

@nexional Your server's certificate chain appears to be incomplete, according to the Qualys SSL test

@nexional
Copy link
Author

I can open the media on browser. Is there a way to bypass certificate problem?

@CounterPillow
Copy link
Contributor

you can use --tls-verify=no to bypass certificate verification, but the real solution here is to fix your server's certificate chain.

@mc4man
Copy link

mc4man commented Jul 14, 2017

Plsys back just fine here
mpv --ytdl=no https://server.ferrante.me/shared/iTunes/Home%20Videos/35017Ferrante.m4v
Auto-loading profile 'protocol.https'
Playing: https://server.ferrante.me/shared/iTunes/Home%20Videos/35017Ferrante.m4v
(+) Video --vid=1 () (h264 594x480 29.963fps)
(+) Audio --aid=1 --alang=und (
) (aac 2ch 48000Hz)
Audio --aid=2 --alang=und (ac3 2ch 48000Hz)
AO: [pulse] 48000Hz stereo 2ch float
Using hardware decoding (vaapi).
VO: [opengl] 594x480 => 594x540 vaapi[nv12]
AV: 00:00:26 / 00:04:37 (9%) A-V: 0.000 Cache: 9s+39MB

@wiiaboo
Copy link
Member

wiiaboo commented Jul 14, 2017

Plays fine here too now.

Only ytdl complains:
[ytdl_hook] ERROR: Unable to download webpage: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)> (caus ed by URLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)'),))

@CounterPillow
Copy link
Contributor

Since it plays fine for @mc4man, could it be that this is a case of a certificate in the chain not yet being in our trust stores or something, but in the private trust stores of web browsers?

@mc4man
Copy link

mc4man commented Jul 14, 2017

If I were you I'd be thinking about wtf you're doing rather than an apparent inability to truncate a url to suit mpv (or likely any other player.
I don't know what country you're in but if US then probably a bad idea to advertise a wide open server of content for anyone to play (and a frickin dl button to boot

Edit; removed url examples as no sense compounding this..

@nexional
Copy link
Author

Thanks guys but I still am not able to play with individual options or any combination of --tls-verify=no, --ytdl=no, --no-config.

@mc4man I don't own the server :). Just stumbled upon for some free content. It was working fine so far but suddenly started getting "tls" errors.

@mc4man
Copy link

mc4man commented Jul 15, 2017

Assumed it was yours based on 1st vid, i.e. home photos from the 50's
Have you actually tried removing index.php?dir= and &file= from any of those server urls?

https://server.ferrante.me/shared/iTunes/Home%20Videos/35017Ferrante.m4v

@nexional
Copy link
Author

nexional commented Jul 15, 2017

@mc4man yeah, no luck :(

I tried from cygwin as well as cmd prompt. CMD doesn't show "Creating security context failed" error but fails nonetheless.

@wiiaboo
Copy link
Member

wiiaboo commented Jul 15, 2017

Still works fine here. Whatever it is doesn't seem to be mpv's fault, but probably something wrong with your system's certificates.

@nexional
Copy link
Author

nexional commented Jul 15, 2017

Anything I can do to clear my system certificates mainly for this site?

@wiiaboo
Copy link
Member

wiiaboo commented Jul 15, 2017

Try browsing it with IE or Edge and see if there's any error.

@nexional
Copy link
Author

nexional commented Jul 15, 2017

I can play the movie directly on any browser (chrome/IE) like I mentioned in original post. Also there's no certificate error that browser browser reports. Somehow mpv fails to load it.

@nexional
Copy link
Author

Anything on this problem. Is there a way to ignore the certificate error/chain?

@CounterPillow
Copy link
Contributor

@nexional

you can use --tls-verify=no to bypass certificate verification

werks 4 me

@nexional
Copy link
Author

Apparently it started working again with the latest build of either MPV (mpv-x86_64-20170722-git-2378acc.7z) or youtube-dl (2017.07.23). Don't even need the flag. I have to add, it's probably something done at the server end to fix the certificate chaining. Nonetheless I hope it doesn't break again. Fingers crossed :). BTW thanks guys for all your inputs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants