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

First Go to Settings in Postman:

1. Off the SSL certificate verification in General Tab:

2. Off the Global Proxy Configuration and Use System Proxy in Proxy Tab:

3. Make Request Timeout to 0 (Zero)

Configure Apache:

If the above changes resulted in a 404 response, then continue reading ;-)

Users that host their site locally (like with XAMP and/or WAMP), may be able to visit their virtual sites using https:// prefixed address, but it's a lie, and to really enable SSL (for each virtual-site), configure Apache like:

• Open httpd-vhosts.conf file (from Apache's conf/extras directory), in your preferred text editor.

• Change the virtual site's settings, into something like:

<VirtualHost *:80 *:443>
    ServerName my-site.local
    ServerAlias *.my-site.local
    DocumentRoot "C:\xampp\htdocs\my-project\public"

    SSLEngine on
    SSLCertificateFile "path/to/my-generated.cert"
    SSLCertificateKeyFile "path/to/my-generated.key"

    SetEnv APPLICATION_ENV "development"

    <Directory "C:\xampp\htdocs\my-project\public">
        Options Indexes FollowSymLinks
        AllowOverride All
        Order allow, deny
        Allow from all
    </Directory>
</VirtualHost>

But of course, generate a dummy-SSL-certificate, and change all file paths, like from "path/to/my-generated.cert" into real file addresses.

• Finally, test by visiting the local site in the browser, but using http:// (without S) prefixed address; Apache should now give error like:

Bad Request

Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.

Hi This issue is resolved for me.

setting ->general -> Requesttimeout in ms = 0

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

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)