jonesfernandes

Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Forum: Plugins
    In reply to: [GoDaddy Payments for WooCommerce] Error response 429
    jonesfernandes

    (@jonesfernandes)

    1 year, 7 months ago

    Hi Amber !

    No, I am still seeing the same issues. I am not sure why there is no payment errors on the logs even though I have tried to pay multiple times with no success. The error on the console is always the same. 429 + CORS error.

    I am using version Version 8.4.0 of GoDaddy Payments which I believe is the latest.

    Best,

    Jones.

    Forum: Plugins
    In reply to: [GoDaddy Payments for WooCommerce] Error response 429
    jonesfernandes

    (@jonesfernandes)

    1 year, 7 months ago

    I’ve asked GPT to extract the most important info from this log file and that’s what he said.

    Here’s a summary of the key events from your log file to assist the GoDaddy Payments support team:

    1. Successful Request – Initial Attempt
    • Time: 2024-10-27 23:12:57 BRT
    • Method: GET
    • Endpoint: /businesses/0093aeb6-f74e-4ab6-8537-c6cdf1645773/stores
    • Response: 200 OK
    • Duration: 0.38773s
    • Details: Received a successful response with status 200, confirming access to business data for the store at this timestamp. The store details (address, devices, attributes, etc.) were returned.
    1. Unauthorized Request
    • Time: 2024-10-28 11:13:21 BRT
    • Method: GET
    • Endpoint: /businesses/0093aeb6-f74e-4ab6-8537-c6cdf1645773/stores
    • Response: 401 Unauthorized
    • Error Code: INVALID_ACCESS_TOKEN
    • Message: “Access token is missing or invalid. Token might have expired.”
    • Details: The system could not authenticate due to an invalid or expired token, suggesting the need for a new access token.
    1. Token Refresh Request
    • Time: 2024-10-28 11:13:21 BRT
    • Method: POST
    • Endpoint: /token
    • Request Body: grantType=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Ajwt-bearer&assertion=...
    • Response: 200 OK
    • New Access Token Issued: Successful token refresh, indicating the plugin automatically requested a new access token.
    1. Successful Request – Retry After Token Refresh
    • Time: 2024-10-28 11:13:22 BRT
    • Method: GET
    • Endpoint: /businesses/0093aeb6-f74e-4ab6-8537-c6cdf1645773/stores
    • Response: 200 OK
    • Duration: 0.34566s
    • Details: The request was retried immediately after obtaining the new token and received a successful 200 OK response, retrieving the same store data.

    Summary:

    • The GoDaddy Payments plugin experienced an authorization issue due to an expired or invalid access token. However, it successfully performed a token refresh and retried the request immediately, receiving a successful response with the required data.
    • The primary area for the support team to investigate might be ensuring tokens refresh before expiry to avoid unauthorized requests in between successful ones.

      Best,

      Jones
    Forum: Plugins
    In reply to: [GoDaddy Payments for WooCommerce] Error response 429
    jonesfernandes

    (@jonesfernandes)

    1 year, 7 months ago

    Hey Amber ! Thanks for the quick response !

    I’ve asked GPT to look for payment failures on the log file and that’s what it said:

    In the log provided, you can identify issues with GoDaddy Payments in the 401 Unauthorized error, indicating an invalid access token. Here’s a breakdown of what each segment suggests:

    1. First Request (2024-10-28T02:12:57): The request was successful with a 200 OK response code, confirming the API was accessible with a valid token at this point.
    2. Error Point (2024-10-28T14:13:21): This second request returned a 401 Unauthorized status, and the body message states:
      • INVALID_ACCESS_TOKEN
      • "Access token is missing or invalid." and "Token might have expired."
      This suggests that the token used in this request was either expired or invalid.
    3. Token Refresh (Immediately after the error): A POST request to the token endpoint retrieves a new token successfully with a 200 OK response.
    4. Resolution: The subsequent request (2024-10-28T14:13:22) reuses this new token and returns a 200 OK, indicating that the system properly handled the expired token by refreshing it.

    Recommended Actions

    • If these 401 errors occur frequently, implement a mechanism to check the token’s validity before each request.
    • For a more proactive approach, schedule token refreshes before expiry based on the token’s lifespan (expiresIn value).

    This flow shows the system self-recovering from an expired token, but if the 401 error persists at unusual frequencies, investigate the authorization handling further.

    Hope to hear from you soon. Thanks !

    Best,

    Jones

    Forum: Plugins
    In reply to: [GoDaddy Payments for WooCommerce] Error response 429
    jonesfernandes

    (@jonesfernandes)

    1 year, 7 months ago

    Hey Amber ! Thanks for answering !

    I am trying to integrate GoDaddy payments and trying to buy test products, but I always get this error. I still don’t know why.

    I am also not sure if there is a way to debug and check if my website is sending too many requests. I’ve checked the network tab on DevTools, but it looks ok, there’s no excessive API calls. Also there’s no timeout error. As soon as I click the checkout button the API call is made and less than 5 seconds later I get the 429 error.

    Best,

    Jones.

    Forum: Plugins
    In reply to: [GoDaddy Payments for WooCommerce] Error response 429
    jonesfernandes

    (@jonesfernandes)

    1 year, 7 months ago

    Heeey. I am getting this same error. Any solution ? I’ve checked all the things you asked us to check but I still see the same 429 + CORS error.

Viewing 5 replies - 1 through 5 (of 5 total)