Closed tonizombie closed 1 year ago
Hey, were you able to fix it? I encounter the same issue - newly created DeepL account and fully verified it.
Hey, were you able to fix it? I encounter the same issue - newly created DeepL account and fully verified it.
Sadly no, reinstalled, reconfigured and still authentication error.
I suspect this is on deepL side as i can see my api key on their website anymore, when i try Sign Up again it just says
"Something went wrong. Please try again or contact [DeepL Support](https://support.deepl.com/hc/requests/new)."
Hmm, I have no issues with registering/logging in directly at deepL so maybe worth checking again. I would assume they changed the API which is not reflected in the plugin, but currently to busy to look into.
I'm having the same issue: To be on the safe side, I changed my authentication key in my Deepl account, but the extension still defaults to Google even though Deepl translation engine is selected.
I've looked a bit deeper into it - and it seems an issue with account creation on DeepL side. I pulled the code and ran the addon in dev-mode and was able to see requests made to DeepL which seemed fine.
How I have solved the issue? (can't verify no additional Credit Card for new account-verification)
So for me it was an account issue. Retested it (uninstalled, reinstalled) latest release from addons.mozilla.org with no issues now. If you can't solve it may write to DeepL support.
Generally, you can use DeepL with the following steps. https://github.com/sienori/simple-translate/wiki/How-to-register-DeepL-API It could be DeepL account issue.
When translating full page it goes to google even when deepl is selected. And when translating only parts of text it gives this error
I havent changed anything about the key or plan, but when i went to deepl site i cant see my api key anymore and instead i found this https://www.deepl.com/en/chrome-extension (Tho i cant use it as i dont use chrome)
Did something change on plugins side or deepl?