CODEWITHSUNDEEP
phpsymfonyguzzle
Ris
Ris

Reputation: 1912

curl (7): Failed to connect to localhost port 8000: Connection refused

Hello I am testing the endpoint and when I run php testing.php I get this error. Any help would be appreciated it.

Fatal error: Uncaught exception 'Guzzle\Http\Exception\CurlException' with message '[curl] 7: Failed to connect to localhost port 8000: Connection refused [url] http://localhost:8000/api/programmers' guzzle\guzzle\src\Guzzle\Http\Curl\CurlMulti.php:359 ...

I've tried 127.0.0.1 as well and it didnt work

here is testing.php

<?php

require __DIR__.'/vendor/autoload.php';

use Guzzle\Http\Client;

// create our http client (Guzzle)
$client = new Client('http://localhost:8000', array(
    'request.options' => array(
        'exceptions' => false,
    )
));

$nickname = 'ObjectOrienter'.rand(0, 999);
$data = array(
    'nickname' => $nickname,
    'avatarNumber' => 5,
    'tagLine' => 'a test dev!'
);

$request = $client->post('/api/programmers', null, json_encode($data));
$response = $request->send();

echo $response;
echo "\n\n";

Upvotes: 8

Views: 70307

Answers (6)

Helia
Helia

Reputation: 1

Step 1: Check and remove Git's proxy settings To check the current proxy configuration, use the following command:

git config --global --get http.proxy

If it returns a proxy address like ''http://localhost:8000/docs'', it means a proxy is configured. You can remove the global proxysettings by running the following command:

git config --global --unset http.proxy

This will remove Git's proxy configuration and allow it to connect directly to the network.

Step 2: Check proxy settings in system environment variables Run the following command to check for proxy configurations in the system environment variables:

set | findstr /i proxy

If it outputs variables like ''http_proxy'' or ''https_proxy'', it means a proxy is configured at the system level. You can remove these environment variables with the following command:

setx https_proxy ""

This will remove the system-level proxy settings, preventing them from affecting Git's network connection.

Upvotes: 0

cabralpinto
cabralpinto

Reputation: 2068

For anybody running into this issue when running Wordpress with wp-env start on Windows or Mac, Docker Desktop provides a special DNS name host.docker.internal, which you can use to refer to the host machine from within a Docker container. If this is your case, then you should be able to fix the issue by simply replacing localhost with host.docker.internal.

Upvotes: 1

Rahul Rahatal
Rahul Rahatal

Reputation: 658

Check if your localhost:8000 server is running.

If it is not then start it using following command from terminal.

Go to root folder of your project & type,

php -S localhost:8000 -t .\public

Upvotes: 1

shoeab
shoeab

Reputation: 314

I was facing the same, when http://localhost:8000 or http://127.0.0.1:8000 neither worked. I solved it using my network IP like

192.168.0.3:8000

Upvotes: 6

Matt Doran
Matt Doran

Reputation: 2153

If you are running localhost like so:

php -S localhost:8000

and then running curl from a different environment like vagrant then localhost on your vagrant is not the same as localhost on your local machine.

Upvotes: 1

Ahmed H. Saab
Ahmed H. Saab

Reputation: 413

if you are using linux, make sure the server is running using 

/etc/init.d/httpd status

Upvotes: 1

Related Questions