[subdomain] "Could not get any response" response when using postman with subdomain

I am using postman to test an API I have, all is good when the request does not contain sub-domain, however when I add a sub-domain to URL I am getting this response.

Could not get any response

There was an error connecting to http://subdomain.localhost:port/api/

Why this might have happened:

The server couldn't send a response:Ensure that the backend is working properly

Self-signed SSL certificates are being blocked:Fix this by turning off 'SSL certificate verification' in Settings > General

Proxy configured incorrectly Ensure that proxy is configured correctly in Settings > Proxy

Request timeout:Change request timeout in Settings > General

If I copy the same URL from postman and paste it into the browser I get a proper response, is there some kind of configurations I should do to make postman work with sub-domains?

For me what worked was to add 127.0.0.1 subdomain.localhost to my host file. On OSX that was /etc/hosts. Not sure why that was necessary as I could reach the subdomain from chrome.

In my case it was a misconfigured subnet. Only one of the 2 subnets in the ELB worked.

I figured this out by doing a nslookup and trying to curl the returned IPs directly. Only one worked. Postman just kept using the misconfigured one.

In my case it was invisible spaces that postman didn't recognize, the above string of text renders as without spaces in postman. I disabled SSL certificate Validation and System Proxy even tried on postman chrome extension(which is about to be deprecated), but when I downloaded and tried Insomnia and it gave those red dots in the place where those spaces were, must have gotten there during copy/paste

In my case, I forgot to set the value of the variable in the "CURRENT VALUE" field.

When getting the following error,

you need to do the following.

Step 1: In Postman, click the wrench icon, go to settings, then go to the Proxy tab.

Step 2: Create a custom Proxy. This article explains how to create a custom proxy. After you create the custom Proxy, make sure you turn the Proxy toggle button to off. I put 61095 in for the proxy server and it worked for me.

Step 3 :

Success

You mentioned you are using a CER certificate.

According to the Postman page on certificates.

Choose your client certificate file in the CRT file field. Currently, we only support the CRT format. Support for other formats (like PFX) will come soon.

The name of the extension CER, CRT doesn't make the certificate that type of certificate but, these are the excepted extensions names.

CER is an X.509 certificate in binary form, DER encoded.

CRT is a binary X.509 certificate, encapsulated in text (base-64) encoding.

You can use OpenSSL to change a CER file into a CRT file. I have not had good luck with it but it looks like this.

openssl x509 -inform PEM -in certificate.cer -out certificate.crt

or

openssl x509 -inform DER -in certificate.cer -out certificate.crt

For anyone who experienced this issue with real domain instead of localhost and couldn't solve it using ANY OF THE ABOVE solutions.

Try changing your Network DNS (WIFI or LAN) to some other DNS. For me, I used Google DNS 8.8.8.8, 8.8.4.4 and it worked!

In my case, The issue was that for UAT environment, API URL will start with Http instead of https. Also, the backend assigns different ports for both Http and https.

for example,

http://10.12.12.31:2001/api/example. - is correct for me

https://10.12.12.31:2002/api/example. - is wrong for me

Because I was using https and 2002 port for hitting the UAT environment. So I am getting could not get any response error in postman.

We got this confusing error when a user accidentally copy/pasted a leading space character in an environment variable used to build the URL:

Example:

The request's URL was set to: http://{URL}/blah

The {URL} environment variable had a value of " hostname" (**notice the leading space character**)

This caused Postman to try to access http:// hostname/blah which gave this error message.

solution is very simple if you are using asp.net core 2 application . Inside ConfigureServices method inside startup.cs file all this line

services.AddMvc()
                .SetCompatibilityVersion(CompatibilityVersion.Version_2_1)
                .AddJsonOptions(x => x.SerializerSettings.ReferenceLoopHandling = Newtonsoft.Json.ReferenceLoopHandling.Ignore);

Unchecking proxy and SSL Certificate Verification didn't work for me.

Unsetting PROXY environment variables did the trick.

export http_proxy=
export ftp_proxy=
export https_proxy=

Change to the directory where Postman is installed and then:

./Postman

In my case, MVC wasn't able to serialize the results (I accidentally used a model instead of DTO). I debugged down to passing a simple string, which worked. Once I fixed the serialization it all came up.

I got the same "Could not get any response" issue because of wrong parameter in header. I fixed it by removing parameter HOST out of header.

PS: Unfortunately, I was pushed to install the other software to get this information. It should be great to get this error message from Postman instead of getting general nonsense.

I had the same issue. It was caused by a newline at the end of the "Authorization" header's value, which I had set manually by copy-pasting the bearer token (which accidentally contained the newline at its end)

Postman for Linux Version 6.7.1 - Ubuntu 18.04 - linux 4.15.0-43-generic / x64

I had the same problem and by chance I replaced http://localhost with http://127.0.0.1 and everything worked.

My etc/hosts had the proper entries for localhost and https://localhost requests always worked as expected.

I have no clue why changing localhost for http with 127.0.0.1 solved the issue.

For me it was the http://localhost instead of https://localhost.

You just need to turn SSL off to send your request.

Proxy and others come with various errors.

For me, it was that route that I was calling in my node server wasn't returning anything. Adding

    return res.status(200).json({
        message: 'success!',
        response: 'success!'
    });//

to the route I was calling resolved the issue.

In my case the (corporate) proxy was using a self-signed SSL certificate which Postman disliked. I discovered it by activating View->Show Postman console and retrying the request. The console then showed the certificate error. In Settings->General I disabled SSL certificate verification.

I came up with this solution

1. In postman go to setting --> proxy
2. And off Global Proxy Configuration

3. on the Use System Proxy

4. And go to windows host configure file 'C:\Windows\System32\drivers\etc\hosts'

5. Open that file in administrator mode
6. And add the sub domain to hosts file

For me the issue was that the Content-Length was too big. I placed the content of the body in NotePad++ and counted the characters and put that figure in PostMan and then it worked.

I know it does not directly answer why the op's sub-domain was not working but it might help out someone.

If you get a "Could not get any response" message from Postman native apps while sending your request, open Postman Console (View > Show Postman Console), resend the request and check for any error logs in the console.

Thanks to numaanashraf

The solution for me, as I'm using the deprecated Postman extension for Chrome, to solve this issue I had to:

1. Call some GET request using the Chrome Browser itself.
2. Wait for the error page "Your connection is not private" to appear.
3. Click on ADVANCED and then proceed to [url] (unsafe) link.

After this, requests through the extension itself should work.

If all above methods doesn't work check your environment variables, And make sure that the following environments are not set. If those are set and not needed by any other application remove them.

HTTP_PROXY
HTTPS_PROXY

Reference link

Hi This issue is resolved for me.

setting ->general -> Requesttimeout in ms = 0

My issue was by putting wrong parameters in the header, the requested parameters was

Authorization: Token <string>

and is was trying

Authorization Token: <string>

None of these solutions works for me. Postman is not sending any request to the server because postman is not finding the host. So, if you modify your /etc/hosts to 127.0.0.1 localhost 127.0.0.1 subdomain.localhost

It works for me.

After all the above methods like turning OFF SSL certificate verification, turning ON only Use System Proxy and removing HTTP_PROXY and HTTPS_PROXY system environment variables, it worked.

Note: Had to restart the Postman app, since the environment variables were changed.

I had the same issue.

Turned out my timeout was set too low. I changed it to 30ms thinking it was 30sec. I set it back to 0 and it started working again.

1. In postman go to setting --> proxy
2. And off Global Proxy Configuration

I just experienced this error. In my case, the path was TOO LONG. So url like that gave me this error in postman (fake example)

http://127.0.0.1:5000/api/batch/upload_import_deactivate_from_ready_folder

whereas

http://127.0.0.1:5000/api/batch/upld_impt_deac_ready_folder

worked fine.

Hope it helps someone who by accident read that far...