Endpoint Error – does not respond with 200

  • Resolved FeralReason

    (@feralreason)


    1 year, 9 months ago

    FYI: Using version 1.4.2.1, WordPress 6.2.2, php 8.1. Running debug for unrelated reasons, this came up in the Debug log:

    [22-Jun-2023 19:37:09 UTC] Burst Statistics: Endpoint error, does not respond with 200. Response given: 301

    Thanks,

    Glen

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Hessel de Jong

    (@hesseldejong)

    Hi @feralreason,

    This means that for some reason the endpoint could not be reached. This could’ve happened just once.

    Does the tracking for Burst still work? You can check this in the dashboard. If the tracking still works there should be nothing to worry about.

    Some context: Tracking with the endpoint is the most accurate and the fastest. So we always try to use the endpoint first, but for some server configurations the endpoint does not work. That’s when we try to use the REST API for tracking. When that does not work we show a plus one and an error in the dashboard.

    Kind regards,
    Hessel

    Thread Starter FeralReason

    (@feralreason)

    No problem. Just passing on what I found. I’ll mark this as closed. (Our server situation is Azure – running nginx.)

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Endpoint Error – does not respond with 200’ is closed to new replies.