Netflix Imports Failing W/"No Appropriate Captions Found"...

brandon.lee.detty

United States

Netflix Imports Failing w/"No appropriate captions found"

July 12 at 21:51

I tried posting in another user's thread, but think my comments got overlooked. I get "no appropriate captions found" when trying to import from Netflix. Yes, subtitles are enabled in the target language before attempting the import. I've tried multiple Netflix shows in Dutch, and one in Italian. All of them give the same error message after a long pause. I tried importing both to a new playlist and to an existing list. It failed on Chrome 103 with both Windows and Linux, as well as Firefox 102 on Linux. I reinstalled the Chrome plug-in and the Firefox plug-in was installed for the first time. I even tried using it through a VPN while connected to a Belgian server.

zoran

Serbia

December 12 at 15:20

Hi everyone, we are looking into the issue and we hope to find a solution soon. Thanks for your patience!

ruthenium

United States

February 24 at 01:40

Any updates? My husband just subscribed for the year, finally convinced by me that it's useful and now I can't import from Netflix.

zoran

Serbia

February 24 at 10:41

@ What did you try to import? Are you sure that subtitles are available in your study language? Netflix importing should work properly at the moment.

rkarjala

Finland

December 11 at 08:48

Has this been solved yet? This netflix plugin was the sole reason why I subscribed to this service. Doesn't work on Firefox, Chrome. "Error: No appropriate captions found."

bankeinanin

United States

December 08 at 12:57

So if it's an issue of LingQ having to keep up with netflix updates, do we need to report this every time it happens so that LingQ's IT can work on it or does LingQ's team know of this everytime it happens.

I use LingQ for primarily netflix transcripts but I'm fine grinding the flashcards until the importer works again.

noxialisrex

United States

December 08 at 13:43

Unfortunately, Netflix has not had a public API in a long time, and I don't even think they are issuing API keys anymore for affiliates and partners. This means anyone building tools that interact with Netflix will be at the mercy of Netflix updating something that breaks what they built.

bankeinanin

United States

December 07 at 21:58

In the meantime is there some other way to get the transcripts from netflix until this bug decides to disappear again?

noxialisrex

United States

December 08 at 03:15

Also experiencing this bug again (in FF and Chrome). The workaround I am using is Tamper Monkey with Chrome and this Script to manually download the VTT file.

https://greasyfork.org/sv/scripts/26654-netflix-subtitle-downloader

As an edit: If you name the VTT the name of your Course in LingQ, it will add it to that Course. Naming won't be ideal (Subtitles 1,2,3,4...), but it works.

robertbiggar

Canada

December 08 at 05:07

side note: you can use tamper monkey and the disney plus version too since the plugin doesn't work on that platform anyway

bankeinanin

United States

December 08 at 12:58

Does it work on Amazon prime or HBO max?

noxialisrex

United States

December 08 at 13:16

It looks like HBO Max splits their subtitles, so you need a script that downloads all the files and, ideally, combines them. Some quick Googling and I found this:

https://greasyfork.org/en/discussions/requests/75196-peacock-and-hbo-max-subtitle-downloaders

But they use a Mega link so download at your own peril.

I found this for Amazon Prime:

https://greasyfork.org/en/scripts/34885-amazon-video-subtitle-downloader/code

noxialisrex

United States

December 08 at 13:13

Yes, I also use tamper monkey scripts for all of the services that the LingQ importer doesn't work with :), including Disney+ (which dubs nearly everything into 20-30 languages).

bankeinanin

United States

December 08 at 12:50

Thank you

maciejprzybylak

Poland

December 07 at 20:04

It still doesn't work for me on chrome and firefox, sorry to hear that because that's why I bought the premium version

llclub

United States

October 04 at 22:37

Chrome importer doesn't work at all for me. Safari one imports only a description (in English...) also adds the movie image to all the other lessons in the folder...

CyranoSteve

Sweden

October 03 at 13:56

It seems this has not been resolved yet, I am still getting this error in Chrome.

Also tried Firefox, same error "Error: No appropriate captions found."

I also tried Safari where the import is said to succeed but it only seems to import the description text and only in English instead of the target language.

Is there a workaround for this problem?

zoran

Serbia

October 03 at 23:39

We are looking into it and trying to figure out what's going on. Thanks for your patience.

CyranoSteve

Sweden

October 04 at 15:01

Ok... have to ask, though: there's a thread on this forum that's 3 years old about this problem. Did it break again or has it never worked?

zoran

Serbia

October 04 at 15:28

@CyranoSteve It's a new issue, of course. Netflix import worked properly, but sometimes, due to changes made on Netflix's end, we have to deal with those changes on our end too to make it work again.

BMD77

United States

September 30 at 05:02

I'm having the same issue, and there seems to be no solution.

PeterBormann

Germany

September 30 at 05:07

Same here:

I tried it with Chrome / Firefox for English, French, Portuguese, and Spanish.

The LingQ plugins don't seem to work anymore for Netflix...

zoran

Serbia

July 13 at 02:02

Thanks, we are investigating the issue.

brandon.lee.detty

United States

July 13 at 23:03

Debug info in case they're having trouble recreating the error:

In particular, 117 failing means that the div with id "LQNFXSUB" isn't created, and that's relied upon for extracting the subtitles later on.

document.body.insertBefore(configElem, document.body.firstChild);

is failing because this is running before the body is ready (document.body is null). This likely has to do with a change to sync/async behaviour on Netflix's side. Before, something was probably blocking the plugin from running until the body was ready. It could also be a race condition, but I'm guessing not.

A company as big as Netflix rolls out changes conservatively, not to everyone at once. That explains why not everyone is affected yet.

zoran

Serbia

July 14 at 01:41

Perfect, thanks for this!

JessicaKent

United States

August 31 at 21:11

Any updates on this?

zoran

Serbia

September 01 at 01:51

There's still an issue with Netflix import from Chrome. It works through Firefox, Edge and Safari. We are looking into finding solution for Chrome extension and we hope to solve it soon.

Page 1 of 1

WANT TO LEARN A NEW LANGUAGE?