https://docs.whmcs.com/9-1/tags/curl-errors/Recent content in curl-errors onHugo -- gohugo.iohttps://docs.whmcs.com/9-1/troubleshooting/troubleshoot-ssl/certificate-subject-mismatch-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-ssl/certificate-subject-mismatch-errors/Covers the cURL “SSL: certificate subject name does not match target host name” error, gives the curl test command used to reproduce it, and attributes the issue to a cURL connection mismatch to resolve with the hosting provider.https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/curl-couldnt-connect-to-host-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/curl-couldnt-connect-to-host-errors/Addresses “Curl Error - Couldn’t connect to host (7)” and “Curl Error: Connection refused - Code 7” messages caused by a firewall blocking port 443 or an IP address not whitelisted with the domain registrar, with fixes to open inbound/outbound ports and whitelist the WHMCS server IP found under License Information for the domain sync task.https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/curl-couldnt-resolve-host-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/curl-couldnt-resolve-host-errors/Covers “Curl Error - Couldn’t resolve host (6)” and the server command variant, caused by DNS failing to resolve the WHMCS licensing server or a product lacking an associated hosting server, with checks of the server/server group settings under Products/Services and Servers plus DNS and zone file verification.https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/curl-timeout-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/general-troubleshooting/curl-timeout-errors/Covers “Curl Error - 28 connect() timed out” and “cURL error 28: Operation timed out” during server provisioning (busy server, 150-second provisioning limit, IP mismatch) or the Automatic Updater downloading from releases.whmcs.com, with fixes for firewalls, SSL mode under Servers settings, and retrying updates via the browser or command line.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-domains/enom/enom-api-curl-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-domains/enom/enom-api-curl-errors/Resolves cURL connection errors with the Enom domain registrar module by confirming the server can reach resellertest.enom.com (Demo Mode) or reseller.enom.com (Live Mode) via cURL.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-domains/openssl-registrar-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-domains/openssl-registrar-errors/Fixes Registrar Error and CURL Error 56 OpenSSL SSL_read messages caused by EasyApache 4 updates (2019-11-20 and 2020-4-1) on cPanel servers, via the workaround yum downgrade ea-libcurl ea-libcurl-devel plus an Apache restart, or by updating cURL and EasyApache 4 to a fixed version.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-invoices/tcpdf-image-size-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-invoices/tcpdf-image-size-errors/Covers the TCPDF ERROR: Unable to get the size of the image message caused by the server’s cURL function failing to load the logo, with steps to test via curl -v and fixes involving firewall configuration or editing invoicepdf.tpl to use a relative image path.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/undefined-curl_init-function-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/undefined-curl_init-function-errors/Covers the Error: Call to undefined function curl_init() message, attributes it to a missing or disabled PHP cURL extension checkable with the php -m command, and gives the fix of installing and enabling the cURL extension.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-payments/unsupported-protocol-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-payments/unsupported-protocol-errors/Documents unsupported SSL/TLS protocol error messages, including Error code 35, sslv3 alert handshake failure, and tlsv1 alert protocol version, and lists steps to update PHP, cURL, and the SSL library to resolve outdated TLS negotiation with payment gateways.