LanguageTool stopped working

1

Hello there :wave:

For some reason, the extension stopped working today. It is activated, but doesn’t highlight any misspelling. I also see this error saying “Не удаётся соединиться с https://api-fallback.languagetool.org/v2/check – проверьте соединение с сетью или попробуйте снова через минуту (#1, code=0)” (or Unable to connect to https://api-fallback.languagetool.org/v2/check - check your network connection or try again in a minute).

Your test page (LanguageTool browser add-on test) shows the same error after a 10-second wait.

I tried Wi-Fi and mobile data, tried disabling and enabling the extension a few times, but it’s not working. Both on Google Chrome and Microsoft Edge. I’m located in RU. My colleagues from the same country and some other countries report that they don’t have any issues with LanguageTool. I’ve not installed any new extensions recently that might influence its operation.

Can you please let me know what I can do in this case to resolve the issue?
Thank you!

chrome_7FgXhzHBXy
chrome_7FgXhzHBXy537×859 19.5 KB

2

Hi Arina,

Thank you for reaching out! We recently encountered some issues with our Chrome’/Edge extensions, which should now be solved.

Could you please try to reinstall the extension? This might solve the issue.

Thanks, and please let us know if this worked!

1 Like
3

Hi, thanks for your reply.

It was a bit unusual to work today without LanguageTool after 4 years of using it daily, that’s when you start to apprecate things :slight_smile: I tried reinstalling the extension and restarting the whole system a few times, but unfortunately, it still doesn’t work. The same error occurs…

4

Have the same problem for already two days. Plug-in dosen’t work on Google Chrome, Microsoft Edge, Opera, FireFox. I’m also located in RU.

UPD: I would like to add that when using a VPN (Germany), everything works perfectly.

1 Like
5

Hello again.

Just to inform you, the extension just started functioning as normal, I’m so glad! Seems like it was an issue on the side of my Internet provider, and now it has been resolved :partying_face:

2 Likes