Adrian's Blog

Tag: downloader

  • Error 500 applying upgrades in Magento Downloader

    Inspecting the error log, the 500 error embedded in the downloader console is the result of a php timeout:

    mod_fcgid: read data timeout in 45 seconds, referer: https://www.<omitted>
(110)Connection timed out: mod_fcgid: ap_pass_brigade failed in  handle_request_ipc function, referer: https://www.

    According to Plesk Article ID: 127621, FcgidIOTimeout should be the same as PHP’s max_execution_time unless the latter is set to 0.

    From Plesk 12.5 control panel for a domain use Apache & nginx Settings to add the following directive to both http and https, which increases the FcgidIOTimeout from 45 to 120 seconds :

    <IfModule mod_fcgid.c>
    FcgidIOTimeout 120
</IfModule>

    Simply OK this and re-run the Magento Downloader again.

    Note: at the time of writing the Magneto Connect site is very slow, which may be the cause of this timeout.

  • After upgrade to Magento Downloader to 1.9.2 no upgrades are available

    Following an upgrade to Magento Downloader 1.9.2 I found that the Magento Connect (Downloader) “check for upgrades” returned nothing (quickly) and the mage upgrade community [package name] gave the following error:
    Error:
    upgrade: Package community/[package name] failed: Unknown cipher in list: TLSv1
    This is caused by the OpenSSL library being out of date, so either update it, or comment out line 377 in downloader/lib/Mage/HTTP/Client/Curl.php like so:
    //$this->curlOption(CURLOPT_SSL_CIPHER_LIST, ‘TLSv1’)

    Adendum: for 1.9.3.2 and 1.9.3.3 the fix is different:

    in /downloader/lib/Mage/HTTP/Client/Curl.php line 371

    change:
    protected function makeRequest($method, $uri, $params = array(), $isAuthorizationRequired = false, $https = true)

    to:
    protected function makeRequest($method, $uri, $params = array(), $isAuthorizationRequired = false, $https = false)

    (Changing the connection method to HTTP in Magento Connect Manager does NOT work.)
    If the downloader is itself updated, this “fix” will need to be repeated.