I'm having the same issue since yesterday on a fresh 2021 installation.
Tried to solve it alone, but no luck with this one.

btw. I just noticed that the problem is also present on my 2019 version.

I'm having the same issue since yesterday on a fresh 2021 installation.
Tried to solve it alone, but no luck with this one.

btw. I just noticed that the problem is also present on my 2019 version.

Hi Hans, hi everyone,

After a few investigations on my own, I tried reverting to the previous version of the Deepl plugin (version 5.8.16.0) and I am no longer experiencing this problem.

The problem seems to come from the last version of the Deepl plugin (5.8.17.1), which could explain that you are facing the same problem with Studio 2019 with this plugin.

Hope this helps,

Thanks Paul for your kind reply and investigations, and best of luck

Regards,

Gilles

Gilles DONATI

Thanks for your investigation.  I actually believe the problem is related to the API key provided by DeepL not supporting the use of the languages endpoint provided by DeepL in their AP documentation. The last update we released, among other things, changed the way we get the languages to avoid having to release new versions every time DeepL add a new language which is better for you, and for us.  They provided an endpoint we can use for this and it works with the API key they provided to us for developing the plugin.

However, this morning (out of desperation because we could not reproduce this problem you are all having at all) I purchased a Pro subscription with DeepL so I went through the same process as you do.  With my new API key the integration fails and I get the same error as you.

So, good that we now know where the problem is coming from.  We have reported this to DeepL and are awaiting their response.  I'm hopeful they will be able to resolve this at their end by allowing the keys to access the same endpoints available in their API.  If they can't then we will change the plugin again and release a new version.  We don't want to roll back because there are other important changes in this release that are needed by some users.

Hi and everyone,

Thanks for your investigations. Is the previous version of the PlugIn (version 5.8.16.0) still available somewhere? The AppStore only has the most recent one.

Best

Annette

Hi Paul Filkin, hi everyone

Thanks for this quick update on the problem.

I can see clearly why you could not reproduce the error.

Of course rolling back is not an ideal solution (that's why I did not consider that it "solved" the problem), but a (hopefully) temporary workaround for those of us on tight deadlines...

I'll stay tuned for more information and, of course, remain available should you (or anybody else) need more details...

Looking forward to downloading the latest version of the plugin!

Many thanks again for your support,

Regards,

Gilles

Hi , I also have a case with christina.dewinne@mobilit.fgov.be that is having the same issue.

Looking forward to your feedback and maybe a fix on the issue.

Hi Paul,

any news from DeepL? I've got the same problem here and I think that it would be great to let users have version 5.8.16.0 again (maybe via a side-channel ) meanwhile as Annette (Manfred Altmann) already suggested.

Best

Olaf

Jens Olaf Koch, Paul Tudoran, Gilles DONATI, Manfred Altmann, Hans Widemann, Thilo Pawelka

An update.  We now know what the problem is, so here's a little history of how we got there so you will understand why we will have to undo some things we added and won't be able to achieve some things you have asked for in the past until DeepL make some changes:

• Because DeepL are quite active and add new languages from time to time we used this feature in the last update to dynamically get the languages in the supported list:
  https://www.deepl.com/docs-api/other-functions/listing-supported-languages/
  That recommendation came from DeepL
  
  
• The API call here is this:
  https://api.deepl.com/v2/languages
  Note that it is v2.
  
  
• This morning DeepL pointed out for me that v2 is actually not available for CAT tools:
  https://www.deepl.com/docs-api/accessing-the-api/api-versions/
  
  
• So it seems that it's possible for them to generate different API keys depending on which API will be used v1, or v2.  The API key DeepL provided us with for developing this plugin supports both v1 and v2.  The API key they provide users with who purchase the professional subscription only supports v1.
  
  
• The effect being everyone has a problem apart from us... the developers ;-)

As a result of this, we will undo some of the changes and go back to a hard coded language support using only v1. of their API.  This will be done next week and we'll release an update as soon as possible.

Thanks, Paul, for investigating and for letting us know the details. I hope DeepL will make v2 available for CAT tool users so you don't have to update the plugin every time they come out with a new language variant.

Thilo Pawelka Paul Tudoran Gilles DONATI Manfred Altmann Jens Olaf Koch Hans Widemann

We have released an update for 2019 and 2021 which is available on the appstore and via the 2021 appstore integration.  This should solve the problems reported.

Thilo Pawelka said:

I hope DeepL will make v2 available for CAT tool users so you don't have to update the plugin every time they come out with a new language variant.

In fact we managed to do this without using the endpoint they provided :-)

Hi ,

That's great news! I tested it immediately and it works.

Thanks so much, you made my day...

Best

Annette (from Manfred's account)