Postman in the browser cannot send a request to your local API
Could not send requestShort 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.
Fix it fast
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/2Match what you see, then jump to its fix
- 1
curl works, but Postman Web fails only for localhost or private addressesThe Cloud Agent or Browser Agent is selected, not the Desktop AgentFix - 2
Console shows proxy details, and the error appears for every hostA proxy setting intercepts the requestFix - 3
The URL is https with a local or self-signed certificateSSL certificate verification fails for an https URLFix - 4
Works from the browser tab, fails from Postman only on a managed networkA firewall blocks non-browser connectionsFix
- 1
What does the error look like?
Could not send requestCould 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 name2Fix
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 Agent3Verify
Send the request again. A response appears.
curl -i http://localhost:3000/Confirmed by learning.postman.com
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 Console2Fix
Correct the proxy configuration, or turn the proxy off in Postman settings for local calls.
# Postman Settings > Proxy3Verify
The request returns a response.
curl -i http://localhost:3000/Confirmed by learning.postman.com
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: off3Verify
The https request now returns a response.
curl -vk https://localhost:3443/Confirmed by learning.postman.com
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 administrator3Verify
Postman gets a response.
curl -i http://localhost:3000/Confirmed by learning.postman.com
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
Back end
Angular app shows 'Cannot GET /' when served by a Node.js server
Cannot GET /dashboard
Cannot GET / is Express saying no route or file matches the request.
3 causes, each with a fixBack end
Axios call from a React app comes back 404
404 (Not Found)
Status code 404 means a server answered, but it has nothing at that path.
3 causes, each with a fixBack end
bcrypt.hash throws 'data and salt arguments required'
Error: data and hash arguments required
The bcrypt package throws this when hash gets null or undefined for the password or for the salt.
4 causes, each with a fixBack end
bcryptjs rejects hash() or compare() with Illegal arguments
Error: Illegal arguments: string, undefined
bcryptjs checks the types of its two arguments and, when either is wrong, throws Illegal arguments followed by the typeof of the first and the second.
3 causes, each with a fixBack end
Express warns 'body-parser deprecated undefined extended'
body-parser deprecated undefined extended
The warning appears because urlencoded() was called without the extended option, which body-parser 1.x has warned about since version 1.4.0.
3 causes, each with a fixBack end
Browser blocks a stylesheet or script: MIME type mismatch with nosniff
The Network tab shows the asset URL answered with Content-Type text/html
With X-Content-Type-Options: nosniff the browser accepts a stylesheet only as text/css and a script only as a JavaScript type.
3 causes, each with a fix