Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Authorization failure (insecure option?) #59

Open
JuGuSm opened this issue Apr 10, 2024 · 3 comments
Open

Authorization failure (insecure option?) #59

JuGuSm opened this issue Apr 10, 2024 · 3 comments

Comments

@JuGuSm
Copy link

JuGuSm commented Apr 10, 2024

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 JuGuSm changed the title Support insecure option Authorization failure (insecure option?) Apr 11, 2024
@JuGuSm
Copy link
Author

JuGuSm commented Jun 6, 2024

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

@soerenuhrbach
Copy link
Owner

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
Copy link
Author

JuGuSm commented Jun 9, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants