daily: libcurl-errors.html

[Pedalman]

*ERROR*     2019/01/03 - 00:01:10: cURL error 52: Empty reply from server (see http://curl.haxx.se/libcurl/c/libcurl-errors.html) at line 185 in file vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php

 

Im agetting this error in the logs daily at roughly the same time. Does it need fixing?

[datakick]

I don't think this is tb related. That's probably problem with your server configuration (firewall, connection timeout limit, etc...) or with the server your server is trying to communicate with.

[Pedalman]

Oh, ok. Thank you Petr. Than I suppose I will not have to dig into it since I know I would not understand what is going on. Perhaps I am going to inform my host: HETZNER

[Pedalman]

Hetzner Europe, my host, answered:

They ask me wheather I know which URL over which port I try to reach. Normally Hetzner allows port 80 and 443.

 

Well, as expected, I do not know. That is the reason I asked in this forum. Looking at the file in concern I see at line 185:

        // Create a connection exception if it was a specific error code.
        $error = isset($connectionErrors[$easy->errno])
            ? new ConnectException($message, $easy->request, null, $ctx)
            : new RequestException($message, $easy->request, $easy->response, null, $ctx);

        return \GuzzleHttp\Promise\rejection_for($error);
    }

I think it might be a ThirtyBees issue nevertheless?

[datakick]

There is some code that's trying to communicate with some external service. You need to figure out where that code is, and what url it tries to access. Since you wrote that it happens roughly at the same time, I would start by looking at the module with some cron support.

[lesley]

What payment gateways are you using @Pedalman ?