tolgee-platform icon indicating copy to clipboard operation
tolgee-platform copied to clipboard
verified publisher icon tolgee

Machine translation consistently fails

Open DDespo opened this issue 6 months ago • 2 comments

Describe the bug Machine translation using Tolgee fails consistently. Regardless of which or how many translation keys are selected, all translation attempts fail. The log does not provide any additional information. The translation feature uses the DeepL API, which had previously worked without issues. For testing purposes, a second DeepL API key from another account was used, but the result was the same. After initiating the translation, it takes a while before the message "Translation failed" appears.

To Reproduce

  1. Go to the Tolgee translation interface.
  2. Select one or more keys.
  3. Start the machine translation process.
  4. Wait for the process to complete.
  5. Error message "Translation failed".

Expected behavior The selected translation keys should be successfully translated using the DeepL API, and the translated content should appear in the interface without any errors. Alternatively, a meaningful error message should be displayed that indicates where the failure occurred, to help identify and resolve the issue.

Screenshots

Image

Versions and environment

  • Tolgee Platform version: v3.120.0 (self-hosted)
  • Browser: reproduced in the lasted desktop versions of Edge (Win), Chrome (Win & macOS) and Safari (macOS)

Additional context We had this issue before but updating on the latest version of Tolgee solved it the last time.

DDespo avatar Jun 06 '25 06:06 DDespo

Hey! Thanks for the query. Can you please provide the server logs?

This usually happens due to misconfiguration.

JanCizmar avatar Jun 06 '25 07:06 JanCizmar

It might be related to "stuck" batch jobs slowing down the server as I describe here: https://tolgeecommunity.slack.com/archives/C03ATFF5Y8Y/p1747970129211539

jdimeo avatar Jun 16 '25 13:06 jdimeo

Hey everyone,

@JanCizmar, please find attached the server logs around the 6th of June when the incident supposedly happen according to @DDespo.

Thank you so much for looking into this.

Best regards, Niko

logs around the 6th of June.zip

nikolamirkov avatar Jun 20 '25 12:06 nikolamirkov

Hi everyone! @DDespo @nikolamirkov I had a look at the issue. I can see a lot of 403 Forbidden: "{"message":"Forbidden. You can find more info in our docs: https://developers.deepl.com/docs/getting-started/auth"}" errors in the logs, but I don't see any clear reason for it to be happening, so let's try to narrow it down a bit:

  • Is the issue still happening? (If not, I suspect something was wrong with the DeepL API.)
  • Did it start to happen after you updated your Tolgee instance to a new version? (If so, please let me know from which version to which version you updated. There have been no significant changes to how the DeepL translations have been handled since 2023.)
  • Can you share your server configuration file? Please redact all sensitive information, and feel free to send it in DMs in Tolgee Slack if you'd like.
  • Are you using the API key for the free DeepL API? (https://api-free.deepl.com/v2/translate vs https://api.deepl.com/v2/translate)

Anty0 avatar Jul 17 '25 12:07 Anty0