Great idea! It worked ! THANK YOU. I know of at least two other people who have “ given up” on importing UTUBE because we were all having the same issues. I just had a discussion about this today with someone and whether we should change change apps for this very reason. Perhaps here along, it was this simple fix. I don’t recall ever seeing it any where to not use a VPN. Would it not be a great service to let users know? Thanks for the prompt and helpful service.
The import from YouTube into LingQ also doesn’t work for me.
I am using Firefox 148.0 (64-bit) on Linux Mint.
@jrernst Thanks, looks like you are on the latest browser version. Did you try to install the LingQ extension? Are you on the latest version there? Do you have the same problem with any video you try to import?
I removed the LingQ extension and installed version 2.3.39.
Then I tested it with an english video on Youtube and it worked.
Then I tested it with the problematic turkish video and the issue occured again.
This is the video: https://www.youtube.com/watch?v=lrV7V11uCeI
PS: Sorry. I just noticed that the video has no transcript.
EDIT - see my post below, issue resolved.
Same problem, can’t import YT vids using desktop import function with error that captions aren’t available. However, I was able to successfully import the very same vide using the iOS phone app.
FWIW this is the vid: https://www.youtube.com/watch?v=9jwDFGxTKgc
@jrernst Great, thanks for the update! @HighSnows Are you on the latest extension version? Did you try to reinstall it?
Discovered the problem. If you’re importing YouTube you MUST use the import pathway of “Streaming platforms / Youtube” instead of “do it yourself / web links”. If you use “DIY / web links” it fails with “importing failed - no captions found”.
Are you using the import pathway “Streaming platforms / Youtube” instead of the DIY URL pathway? That was my problem.
It worked today. But it stopped. Opera browser, Brave. Windows and Macos systems. Extension version 2.3.39
Error: No appropriate captions found. Make sure to turn on subtitles before importing.
Quick update - I paused my VPN and now it works. But still, I am interested in answers because I didn’t need to pause my VPN the last week when I have been using it and I’d rather not have to turn off my VPN every time I import and I know I didn’t need to before. Thank you.
Hello - I am just joining this thread. My extension was working just fine yesterday. Then, this morning, I tried using it on a chinese language video and it was the first time I got the “no captions detected” message. So, I went back to import more German videos that I know have captions, the same channel I have been importing for a while, and now I am getting this message every time. I tried uninstalling and reinstalling. I tried restarting my computer. It is now not working on my phone either. Would love some assistance. Thank you.
@antonilin Can you please let me know if you still have the same issue now?
@juliegallivan Sounds like VPN did cause issues on your end. Unfortunately, not much we can do here since that problem is related to YouTube. You will need to turn VPN off for now when importing content.
Hello. Everything is fine now.
@zoran Any sense of why it wasn’t a problem a few days ago? I can continue to pause the VPN when using it, but it was fine before with it on. If there is always way to get back to that, its definitely preferable. Any sense of what changed? Thanks!
I’m having the same issue recently, although the problem seems to be limited to just one channel I’ve been watching. Specifically, there is an error when importing auto-generated captions, and only for the videos from one channel. Would this be a formatting issue? Would greatly appreciate some help troubleshooting this as I really benefit a lot from these particular videos.
@juliegallivan Can’t say for sure unfortunately, most probably it’s related to changes made on YT’s end.
@Pluvio_Phile That sounds like an issue with subtitles on that specific channel, yes. You can share one video with me and I will take a look.
Okay, thanks for following up on it.
