DeepL plugin telling: "Connection failed!"

Plugins
1

I signed up for free deepl API and got a key. Entering this into the updated DeepL plugin gives message “Connection failed!”. I’ve tried a few things. Deactivating Windows cerficate revocation and deactivating my firewall changes nothing. Upon manually entering the key into deepL.js selected text appears to be sent for translation, but the only response remains “Connection failed!”.

2

(This is for Onlyoffice DesktopEditors in version 9.1.0.167)

4

Hello @weal

What the version of DeepL plugin is being currently used? There was an issue indeed, but it has been fixed in version 1.0.4.

5

As mentioned, I updated the plugin. It’s in version 1.0.4 indeed

6

We have recently released new version of Desktop Editors. Please update your app and test the connection from DeepL again.

7

I now am running the Windows ONLYOFFICE Desktop Editors Community version 9.2.0.100 (x64 msi) with Deepl plugin version 1.0.4. I am still getting “Connection failed!” when entering my API key.
Any suggestions for what I can check on my side?

8

Since you have already mentioned changes to deepL.js, you can also try following:

Make sure to apply these changes to deepL.js with closed plugin.

9

Been trying a range of edits to deepL.js. API_URL_PRO/API_URL_FREE; URL with and without /v2, KEY with and without suffix “:fx”, reinstallation … all I get is “Connection failed!”

11

That is unusual. Can you make sure that either https://api.deepl.com/v2 or https://api-free.deepl.com/v2 is accessible from the browser? Probably having signed in to the account could be required to access the page.

12

I am getting error code 403 for both urls, also some 429. Logging into deepl + stopping my firewall did not get me a different response. I tried on opera and firefox.

14

We are running some tests from our end according to the results that you’ve provided. I’ll update the topic once any news comes up.

16

A possibility is that the user has the free plan (as written by the OP) while OnlyOffice expects another plan. The endpoints are different in both cases, as explained in the documentation and as demonstrated below:

$ curl -X POST https://api.deepl.com/v2/translate \
  --header "Content-Type: application/json" \
  --header "Authorization: DeepL-Auth-Key $API_KEY" \
  --data '{
    "text": ["Hello world!"], 
    "target_lang": "DE"
}'
{"message":"Wrong endpoint. Use https://api-free.deepl.com. You can find more info in our docs: https://developers.deepl.com/docs/getting-started/auth"}

$ curl -X POST https://api-free.deepl.com/v2/translate \
  --header "Content-Type: application/json" \
  --header "Authorization: DeepL-Auth-Key $API_KEY" \
  --data '{
    "text": ["Hello world!"], 
    "target_lang": "DE"
}'
{"translations":[{"text":"Hallo Welt!","detected_source_language":"EN"}]}
17

Hello @ebuchlin

I’d like to point out that the plugin connects to mentioned endpoint as per this line:

API_URL_CURRENT by default is API_URL_FREE, which is https://api-free.deepl.com/v2, thus results in https://api-free.deepl.com/v2/translate endpoint being used as per your note.

We keep investigating the issue.

19

I support this. I am getting the same errors, thow on the deepl page its consuming tokens.

I did all you explained above an cannot get it working.

20

@here, we have registered a bug number 79474 in our internal bug-tracker on this issue for for further investigation. I am keeping you posted on the news.