Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Node.js, PHP and APIs

Postman in the browser cannot send a request to your local API

ErrorCould not send request

Short answer

Postman in the browser sends requests through an agent. The Cloud Agent cannot reach private or local resources, and the Browser Agent is limited by CORS. For a server on localhost, install and run the Postman Desktop Agent, select it in the footer, and send again.

  • Applies to Postman web, Postman Desktop Agent, Express 5, Node.js 22
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Open the address in a normal browser tab or with curl. If the API answers there, the server is fine and the problem is the Postman agent.

    curl -i http://localhost:3000/
  2. 2Match what you see, then jump to its fix

    1. 1curl works, but Postman Web fails only for localhost or private addressesThe Cloud Agent or Browser Agent is selected, not the Desktop AgentFix
    2. 2Console shows proxy details, and the error appears for every hostA proxy setting intercepts the requestFix
    3. 3The URL is https with a local or self-signed certificateSSL certificate verification fails for an https URLFix
    4. 4Works from the browser tab, fails from Postman only on a managed networkA firewall blocks non-browser connectionsFix

What does the error look like?

  • Could not send request
  • Could not get response

Cause 1 of 4

The Cloud Agent or Browser Agent is selected, not the Desktop Agent

1Check

The Cloud Agent cannot access private or local resources on your network. The Browser Agent is subject to browser CORS limits. The Desktop Agent routes requests through your local machine and network.

# Postman footer: look at the selected agent name

2Fix

Install the Postman Desktop Agent, keep it running, and select it from the footer, or turn on Auto-select, which tries Desktop first.

# Postman footer > Agent > Desktop Agent

3Verify

Send the request again. A response appears.

curl -i http://localhost:3000/

Confirmed by learning.postman.com

Did this fix it?

Cause 2 of 4

A proxy setting intercepts the request

1Check

By default Postman uses your operating system's proxy settings, and the Postman Console shows the proxy details.

# Postman: View > Show Postman Console

2Fix

Correct the proxy configuration, or turn the proxy off in Postman settings for local calls.

# Postman Settings > Proxy

3Verify

The request returns a response.

curl -i http://localhost:3000/

Confirmed by learning.postman.com

Did this fix it?

Cause 3 of 4

SSL certificate verification fails for an https URL

1Check

Postman verifies certificates by default. A local certificate it does not trust fails the request.

curl -vk https://localhost:3443/

2Fix

Turn off SSL certificate verification in the app settings for local testing, or add the client certificate under Certificates if the server needs one.

# Postman Settings > General > SSL certificate verification: off

3Verify

The https request now returns a response.

curl -vk https://localhost:3443/

Confirmed by learning.postman.com

Did this fix it?

Cause 4 of 4

A firewall blocks non-browser connections

1Check

Some firewalls are configured to block non-browser connections.

curl -i http://localhost:3000/

2Fix

Ask the network administrator to allow the connection.

# Network policy change by your administrator

3Verify

Postman gets a response.

curl -i http://localhost:3000/

Confirmed by learning.postman.com

Did this fix it?

How do I stop it coming back?

  • Use the Desktop Agent or the desktop app for anything on localhost.
  • Check the Postman Console when a request fails; it shows the final URL after variables resolve.
  • Test with curl first to split server problems from tool problems.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.