Troubleshooting API requests
There might be cases when your API doesn’t work, or exhibits unexpected behavior. If you’re not getting any response, Postman will display a message that there was an error connecting to the server.
For more details about the possible causes of the error, open Postman Console, which has detailed information about the failure, which can substantially reduce the time required to troubleshoot. Consider the following issues as you’re troubleshooting API requests.
If Postman is unable to connect to your server, it shows the message above. Usually, the easiest way to check if there are connectivity issues is to open your server address in a browser, such as Chrome or Firefox. If opening it in the browser works, then the possible causes could be:
Some firewalls may be configured to block non-browser connections, in this case, you should talk to your network administrators in order for Postman to work.
If you are using a proxy server to make requests, make sure you configure it correctly. By default, Postman uses the proxy settings configured in your Operating System’s network settings. Postman Console will provide debug information about the proxy server.
SSL Certificate issues
When using HTTPS connections, Postman may show the error above. In this case, you can try turning off SSL verification in the Postman Settings. If that does not help, your server might be using a client-side SSL connection. This too can be configured in Postman Settings. Use the Postman Console to ensure that the correct SSL certificate is being sent to the server.
Client Certificate issues
Incorrect Request URLs
If you use variables in your request, make sure they are defined in your environment or globals. Unresolved request variables may result in invalid server addresses.
Using incorrect protocol
Check whether you’re accidentally using “https://” instead of “http://” in your URL (or vice versa).
Invalid Postman behavior
Very rarely, it is possible that Postman might be making invalid requests to your API server. You can confirm this by checking your server logs (if available). We’re always watching out for these cases, so get in touch with us if you believe Postman is misbehaving. Let us know on our GitHub issue tracker if you feel that Postman is not working as intended.
Very short timeouts
If you configure a very short timeout in Postman, the request may timeout before completing, resulting in the error block above. Try increasing the timeout to avoid this issue.
If your server sends incorrect response encoding errors, or invalid headers, Postman will fail to interpret the response, causing the error above.
If you’ve tried unsuccessfully troubleshooting the issue, search the Postman issue tracker on GitHub to check if someone has already reported the issue and whether there is a known solution that you can use. If you’re reporting a new issue, follow these guidelines. If you wish to include confidential data, you can file a ticket via our support center and include the app’s console logs in your report to provide some helpful data for troubleshooting.