Mollie API calls time out with cURL error 28 in the PHP client

Not specified by the original author.

Problem

Users of mollie-api-php v2 hit cURL error 28: Resolving timed out on payment creation, even though Mollie reported no availability issues. The default Guzzle client in the SDK used a 10 second timeout, which was too short on connections with slow DNS resolution. A maintainer suggested passing a custom Guzzle client into the MollieApiClient constructor with a longer timeout. The reporter did exactly that, setting 60 seconds, and confirmed payments started working immediately. The same advice resolved the issue for other users with webshops on slow networks.

Verified fix

The SDK's bundled Guzzle client uses a short default timeout, so slow DNS resolution makes payment creation time out with cURL error 28. Fix: construct your own Guzzle client with a longer timeout and pass it to the MollieApiClient constructor. Something like new Client(['timeout' => 60]) injected at construction works. The reporter who hit this did exactly that and confirmed requests started succeeding right away. If timeouts persist after that, check your server's DNS resolver, since that was the underlying cause here. Source: https://github.com/mollie/mollie-api-php/issues/492

Question: Users of mollie-api-php v2 hit cURL error 28: Resolving timed out on payment creation, even though Mollie reported no availability issues. The default Guzzle client in the SDK used a 10 second timeout, which was too short on connections with slow DNS resolution. A maintainer suggested passing a custom Guzzle client into the MollieApiClient constructor with a longer timeout. The reporter did exactly that, setting 60 seconds, and confirmed payments started working immediately. The same advice resolved the issue for other users with webshops on slow networks.

Verified resolution: The SDK's bundled Guzzle client uses a short default timeout, so slow DNS resolution makes payment creation time out with cURL error 28. Fix: construct your own Guzzle client with a longer timeout and pass it to the MollieApiClient constructor. Something like new Client(['timeout' => 60]) injected at construction works. The reporter who hit this did exactly that and confirmed requests started succeeding right away. If timeouts persist after that, check your server's DNS resolver, since that was the underlying cause here. Source: https://github.com/mollie/mollie-api-php/issues/492

Thread: https://vectle.com/threads/thr_wkZHpCTSpaPCE-qyzf0PqA