403 response

  • Resolved fivemarketing

    (@fivemarketing)


    4 years, 3 months ago

    Hi,

    I get an Error 403 for the usage check.
    Translation is not working, instead the spinner animation is going on and on.

    Any idea of how to fix that?

    I saw the error logs of other users. The request method was GET in my log it says POST. Maybe a problem with that?

    LOG:
    Fichier ‘operation’ pour 08/2020
    a:7:{s:4:”date”;s:19:”10/08/2020 09:54:48″;s:5:”class”;s:17:”DeepLApiTranslate”;s:6:”uniqid”;s:32:”8a1a6be08683caccb80c9f9a284f09c2″;s:4:”type”;s:5:”fresh”;s:4:”mode”;s:4:”POST”;s:14:”response_error”;i:403;s:8:”response”;a:2:{s:4:”code”;i:403;s:7:”message”;s:9:”Forbidden”;}}

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author malaiac

    (@malaiac)

    That’s strange.

    The log line is for a translation request, not an Usage request.

    Does the Usage request ( triggered by viewing the page /wp-admin/admin.php?page=deepl_settings&tab=ids ) work ?

    a log line should look like this one :
    a:10:{s:4:”date”;s:19:”10/08/2020 10:30:58″;s:5:”class”;s:13:”DeepLApiUsage”;s:6:”uniqid”;b:0;s:4:”type”;s:5:”fresh”;s:4:”mode”;s:3:”GET”;s:17:”request_microtime”;d:0.19352412223815918;s:4:”args”;a:0:{}s:8:”response”;a:2:{s:15:”character_count”;i:0;s:15:”character_limit”;i:1000000;}s:15:”response_length”;i:47;s:12:”why_no_cache”;s:17:”Cache not allowed”;}

    Thread Starter fivemarketing

    (@fivemarketing)

    Hi,

    this is the log for the usage:

    a:7:{s:4:”date”;s:19:”10/08/2020 11:54:06″;s:5:”class”;s:13:”DeepLApiUsage”;s:6:”uniqid”;b:0;s:4:”type”;s:5:”fresh”;s:4:”mode”;s:3:”GET”;s:14:”response_error”;i:403;s:8:”response”;a:2:{s:4:”code”;i:403;s:7:”message”;s:9:”Forbidden”;}}

    It shows nothing under “Usage”.

    Could it be that the 403 is a response from our server? Not from the API?
    Maybe some server setting blocks the communication.

    Plugin Author malaiac

    (@malaiac)

    That does look like a miscommunication between servers.
    (the Usage log line I pasted was from this morning, plugin 1.4.0, on a regular shared host)

    You might ask DeepL for any known restrictions from your host

    Thread Starter fivemarketing

    (@fivemarketing)

    I tried enpoints directly via browser.

    The 403 is definetly coming from DeepL API v2.
    v1 is working just fine.

    https://api.deepl.com/v1/usage?auth_key=ourAuthKey -> {“document_count”:0,”document_limit”:20}

    https://api.deepl.com/v2/usage?auth_key=ourAuthKey -> 403

    Is your plugin using API v1 or v2?

    I found this: https://www.deepl.com/docs-api/accessing-the-api/api-versions/
    Version 2 (v2) of the DeepL API is not compatible with CAT tools and is not included in DeepL plans for CAT tool users.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘403 response’ is closed to new replies.