Error in debug log

  • Resolved gatta2

    (@gatta2)


    8 years, 6 months ago

    There are quite a few errors like this:
    [2017-11-01 21:30:17] ERROR: User Sync > Error subscribing or updating user 6950: cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received.
    [2017-11-01 21:31:16] ERROR: User Sync > Error subscribing or updating user 4152: cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received.
    [2017-11-01 22:30:11] ERROR: User Sync > Error subscribing or updating user 3143: cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received.
    [2017-11-01 22:30:24] ERROR: User Sync > Error subscribing or updating user 6488: cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received.
    [2017-11-01 23:30:12] ERROR: User Sync > Error subscribing or updating user 10928: cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received.
    [2017-11-01 23:30:22] ERROR: User Sync > Error subscribing or updating user 3375: cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received.
    [2017-11-02 00:30:11] ERROR: User Sync > Error subscribing or updating user 11205: cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received.
    [2017-11-02 09:31:07] ERROR: User Sync > Error subscribing or updating user 2942: cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received.
    [2017-11-02 09:32:12] ERROR: User Sync > Error subscribing or updating user 17159: cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received.
    [2017-11-02 12:30:16] ERROR: User Sync > Error subscribing or updating user 13338: cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received.

    How can we fix it?

Viewing 1 replies (of 1 total)
  • Plugin Contributor Lap

    (@lapzor)

    8 years, 6 months ago

    cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received.

    This error means there was some kind of network issue, anywhere between your server and the MailChimp API, causing the cURL request to timeout before receiving any response.

    You can ask your hosting provider to set the maximum response time a bit higher.

    Hope that helps!

    Kind regards,

Viewing 1 replies (of 1 total)

The topic ‘Error in debug log’ is closed to new replies.