• Hello,

    I just recently installed WordPress 4.6.1. When I try and install a plugin through the dashboard I receive the following error: Installation failed: Download failed. No working transports found

    I downloaded the zip file Core Control, unzipped, and FTP’d the plugin to the plugins directory, then went to the WordPress dashboard and Activated the Core Control plugin. I enabled all 5 modules of Core Control and when I go to the External HTTP Access module, it shows all 3 transports as Available (cURL, PHP Streams, and PHP fsockopen()). When I click the Test Transport link for any of the 3 transports, I receive the following error: An Error has occured: No working transports found

    The site is hosted on an old Solaris box running PHP v5.3.2 with cURL Enabled (v7.45.0).

    Is there something more I should be looking at? When I search for the error about no working transports, most solutions involve enabling the PHP_cURL extension on your Windows machine and then restarting the WAMP server.

    Thank you

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Dion Hulse

    (@dd32)

    Meta Developer

    Can you provide some extra information about the PHP configuration? What php extensions do you have installed?

    Can you install WordPress 4.5 and see if that works (out of curiosity, there were some changes in 4.6 to HTTP access).

    Thread Starter eyzae

    (@eyzae)

    Hi Dion,

    Thanks for replying so quickly.

    Here is the current ./config for PHP that is used on that server:

    ‘./configure’ ‘–with-apxs2=/usr/local/apache2/bin/apxs’ ‘–with-mysql=/usr/local/mysql’ ‘–with-mysqli=/usr/local/mysql/bin/mysql_config’ ‘–with-gd=/usr/local/lib’ ‘–with-jpeg-dir=/usr/local/lib’ ‘–with-zlib’ ‘–with-png-dir=/usr’ ‘–with-mcrypt=/usr/local/lib’ ‘–with-curl=/usr/local/lib’

    Sorry if the copy/paste formatted incorrectly.

    I downloaded WordPress 4.5.4 and installed Core Control (manually by FTPing it to the Plugins directory) and I’m still having the same issue (can’t install any Plugins through the Dashboard, nor can I use the Test Transport feature in Core Control).

    If there is anything you think I can do/try, please let me know. I’m thinking the next step might be to re-install PHP and see if that works.

    Thank you

    Plugin Author Dion Hulse

    (@dd32)

    Meta Developer

    @eyzae My apologies for the delay in replying.

    Unfortunately the configure line doesn’t give much information about the actual PHP environment.
    My assumption is that the server is misconfigured, and either doesn’t allow outbound HTTP connections or something else in cURL/streams is disabled on the server.

    If you’d like a better reason for it being broken, I’ll happily take a quick look at it if you want – I’d need FTP + an Admin account to the WordPress site though – If you’re interested you can contact me at dion [at] www.ads-software.com

    Hi,

    Having the same exact issue. Running on openSUSE Leap 42.1 (latest), apache2 with PHP5. FS_METHOD=direct.

    Oddvard

    Plugin Author Dion Hulse

    (@dd32)

    Meta Developer

    @oddvard Unfortunately posting that you’re also experiencing a similar problem isn’t going to help get any closer to the problem, unless you can diagnose it, or offer some details about your install that is unique.

    Hi,

    Can you please tell me how I can help you diagnose it? Can you explain what this error is caused by? What module prints it & under which circumstanses. I guess a search of for the error message in the PHP code will tell me if it is a WP error or a system call error. The error have a workaround:

    1. Download it from repository web page into your bowser download directory.
    2. On the Plugin page upload it to your WP installation.
    3. Install it when uploaded to WP installation.

    Let me know what I can do!

    Oddvard

    Oddvard

    Ok, did some legwork to debug this. Downloaded Netbeans & XDebug. Configured Netbeans with a PHP project from /srv/www/htdocks/wordpress & enabled Xdebug in /etc/php5/apache2/php.ini so the apache2 server can use it. Worked well & is a pretty slick way to debug wordpress..:-)

    NOTE: Had to: chmod -R g+w wordpress & chgrp -R users wordpress (as root) to enable my user to write to the source dir. Not the best of ways when all users have write priveliges to the wordpress dir, but I can live with it because it is a local system & I am alone using it. DO NOT USE THIS METHOD on a shared server…

    As I am new to the world of wordpress I was looking for a sensible place to look. A search for the error string in WP code was negative – so that indicated a system call error. Set a breakpoint in function get_error_message in class-wp-error.php & bingo…stack trace & here is the error;

    /**
    * Uses the GET HTTP method.
    *
    * Used for sending data that is expected to be in the body.
    *
    * @access public
    * @since 2.7.0
    *
    * @param string $url The request URL.
    * @param string|array $args Optional. Override the defaults.
    * @return array|WP_Error Array containing ‘headers’, ‘body’, ‘response’, ‘cookies’, ‘filename’. A WP_Error instance upon error
    */
    public function get($url, $args = array()) {
    $defaults = array(‘method’ => ‘GET’);
    $r = wp_parse_args( $args, $defaults );
    return $this->request($url, $r); <—!!! SSL not configured…..
    }

    Q: Is this a web server issue or a WP issue? (Pink Floyd —- Learning to fly)

    Oddvard

    Hi,

    Nobody in this thread could help. Dion was friendly enough but backed out. So the old saying; “If you want things to be done – do it yourself!” still hold water. As I did not know where the issue was I had to dig a little deeper into the source. I found the error string (what I wrote in my previous post was wrong) in WP &stepped into the code as described in earlier post. As “learning to fly” is a long process, it took me a while to figure this one out. The error is not caused by WP nor Web-server. It is caused by PHP. The reason is a missing module in the php installation. This module is the URL socket library found in the curl extension package (openSUSE). To fix it I had to:

    1. Install the php-curl package – using the Yast tool in OpenSUSE.
    2. Tell the Web-server (Apache2) to load it – using the sysinit tool in OpenSUSE
    3. Restart the Web-server.

    Then all was OK. It seems like the default installation of PHP does not include all the packages WP need. So a check tool could be saving a lot of time for people.

    Odd

    Thank you for the write up regarding the missing cURL module.

    @dd32 actually did mention that the server “either doesn’t allow outbound HTTP connections or something else in cURL/streams is disabled”.

    That clued me in about what might have broken.

    phpinfo() confirmed the missing module for me, so thank you again…:)

    Glad to be any good to somebody…BIG ??

    Oddvard

    Ohhh Thanks,
    I searched a long time over WEB for a solution for this problem and your answer solved it : my php-ini was just misconfigured, (curl not activated)

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Transports Available but not found’ is closed to new replies.