Hi. I am a Korean user studying with Language Reactor.
since this morning, The message “자막 로딩 중입니다” (which mean “loading subtitles, please wait” in korean) appears and the language reactor does not work.
Netflix and YouTube all don’t work.
I did my own research and did everything I could.
Visit netflix and toggle off “Include me in tests and previews”
I’ve tried logging out and logging back in, turning it off and back on again.
But still not working.
I guessed that the free pro version upgrade provided a while ago was the problem, so I tried to restore it back to free version, but that was also impossible.
at least I want to know how to undo it.
Please solve my problem and I hope you have a nice day
This issue has just started happening for me yesterday (2024-09-07) for the Korean language only. Other languages like Italian are working fine for me right now.
I’m using youtube. If you turn the extension off, the subtitles exist on youtube as they normally would and work properly, once the extension is enabled it just gets stuck on the loading subtitles message: “Loading subtitles, please wait…”
I have tested on a few different chromium based browsers and it’s the same issue in all of them.
This problem has been happening again since 2024-09-20, I haven’t been able to load subtitles when using the Korean language only (other languages are working for me). I have tried the same troubleshooting as last time with no luck. I’m guessing this has to be a server side issue because I’ve changed nothing in my browser configuration. I submitted a ticket last week when it started happening but I haven’t heard back yet.
Bumping this as this same, exact issue has been ongoing for me as well since last Friday, 9/20. I see that the LR site status shows Reactor Under Construction, hoping this bug can be fixed so we can keep learning c: Thank you!
The problem is back again, it started happening a few days ago. Apologies for bumping this thread so many times but the app isn’t loading the subs for Korean, other languages are working for me. It’s the exact same issue as the last few times this has happened.