Why is DeepL Translation Provider plug-in suddenly not accepting my correct API key after the recent update?

Hello.

I recently updated the DeepL Translation Provider plug-in and now it no longer accepts my API key, even though it is valid (I've checked several times!) - can anyone shed some light?

Many thanks

Susan

Parents Reply Children
  • Hi Andrea

    Here you go. I'm using the plug-in for French into English in this instance. But I also use it for Russian into English. I'm using Studio 2021.

    I hope this is helpful! 

    All the best

    Susan

  • Hi ,

    Thank you for providing the log file. 

    It seems the errors logged there are old and it has nothing to do with the Authorization message which you are seeing. I assume somehow in Studio are save some incorrect credentials because that message which appears we are receiving it from DeepL when we are trying to validate the key.

    Can you please go to the following path and delete the TranslationProviderCredentialStore files?

    C:\Users\[your user]\AppData\Roaming\SDL\SDL Trados Studio\Studio16

    Once you delete these files you'll have to add the DeepL key again in the translation provider.

    Kind regards,

    Andrea Ghisa

  • Hello Andrea

    I followed your instructions but Authorisation is still failing. 

    It's strange, because I have Studio 2021 Freelance Plus and I haven't noticed the problem on my laptop. It only occurred since the last update of the plug-in.

    All the best

    Susan

  • I have the same problem as Susan McDonald. I updated and am told that the API key is wrong. I also followed the instructions, but the problem has not been resolved.

    Any help would be much appreciated.

    Best regards,

    Donna

  • Hi

    We found the problem and we'll release a new version in a couple of hours. Sorry for the inconvenience.

    Have a nice day,

    Andrea Ghisa.

  • We just released the new version on AppStore. Can you please update the plugin to see if the problem persists?

  • We just released the new version on AppStore. Can you please update the plugin to see if the problem persists?

  • Thanks for the info! So far I only see the old plugin in the store (5.8.22.0). Guess it takes a while until the new version shows up?