soerenuhrbach / vscode-deepl

DeepL for Visual Studio Code
MIT License
32 stars 7 forks source link

Authorization failure (insecure option?) #59

Open JuGuSm opened 3 months ago

JuGuSm commented 3 months ago

Hi,

I get the following error message: Authorization failure, check auth_key

and I think it's because of the absence of insecure option because when I use DeepL API with curl command I get these results:

without insecure option (KO):

curl.exe -X POST "https://api-free.deepl.com/v2/translate" --header "Authorization: DeepL-Auth-Key $deepl_key" --data-urlencode "text=$text" --data-urlencode "target_lang=FR"

curl: (60) SSL certificate problem: self signed certificate in certificate chain
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

with insecure option (OK):

curl.exe -X --insecure POST "https://api-free.deepl.com/v2/translate" --header "Authorization: DeepL-Auth-Key $deepl_key" --data-urlencode "text=$text" --data-urlencode "target_lang=FR"

{"translations":[{"detected_source_language":"EN","text":"Bonjour le monde"}]}
JuGuSm commented 1 month ago

Any news on this issue? Is it a lot of work?

soerenuhrbach commented 1 month ago

Hi @JuGuSm,

Do you any proxy? Or why do you need the insecure option?

I would not recommend to communicate with third party services if the certificate can't be verified.

JuGuSm commented 1 month ago

Hi @soerenuhrbach,

Even when I test a translation with curl command, I get "SSL certificate problem".

Maybe it's because I'm in a specific professional environment with a VPN always activated.

I know insecure is not the better option but it seems to be the only way to make it works.