Native Postman returns 503 when posting to localhost but Chrome Postman extension works
I am trying to post simple Get commands to my service running on localhost using the Windows native Postman application (V4.8.0) but they fail. The Postman Console shows
Error: tunneling socket could not be established, statusCode=503
An example of the Get command is the following request for simple status message.
https://localhost/api/admin/status
The same commands work when directed to the identical service running on an external server.
They also work posting to localhost directly from Chrome and when using the Chrome Postman extension (also V4.8.0).
SSL certificate verification is turned off.
postman
asked Oct 27 '16 at 9:21
sdmorrissdmorris
144214
add a comment |
I am trying to post simple Get commands to my service running on localhost using the Windows native Postman application (V4.8.0) but they fail. The Postman Console shows
Error: tunneling socket could not be established, statusCode=503
An example of the Get command is the following request for simple status message.
https://localhost/api/admin/status
The same commands work when directed to the identical service running on an external server.
They also work posting to localhost directly from Chrome and when using the Chrome Postman extension (also V4.8.0).
SSL certificate verification is turned off.
postman
asked Oct 27 '16 at 9:21
sdmorrissdmorris
144214
add a comment |
I am trying to post simple Get commands to my service running on localhost using the Windows native Postman application (V4.8.0) but they fail. The Postman Console shows
Error: tunneling socket could not be established, statusCode=503
An example of the Get command is the following request for simple status message.
https://localhost/api/admin/status
The same commands work when directed to the identical service running on an external server.
They also work posting to localhost directly from Chrome and when using the Chrome Postman extension (also V4.8.0).
SSL certificate verification is turned off.
postman
asked Oct 27 '16 at 9:21
sdmorrissdmorris
144214
I am trying to post simple Get commands to my service running on localhost using the Windows native Postman application (V4.8.0) but they fail. The Postman Console shows
Error: tunneling socket could not be established, statusCode=503
An example of the Get command is the following request for simple status message.
https://localhost/api/admin/status
The same commands work when directed to the identical service running on an external server.
They also work posting to localhost directly from Chrome and when using the Chrome Postman extension (also V4.8.0).
SSL certificate verification is turned off.
postman
postman
asked Oct 27 '16 at 9:21
sdmorrissdmorris
144214
asked Oct 27 '16 at 9:21
sdmorrissdmorris
144214
asked Oct 27 '16 at 9:21
sdmorrissdmorris
144214
asked Oct 27 '16 at 9:21
sdmorrissdmorris
144214
asked Oct 27 '16 at 9:21
sdmorrissdmorris
144214
144214
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
I had the same problem.
In my case env variables HTTP_PROXY, HTTPS_PROXY and NO_PROXY where set in my envirionment.
But in NO_PROXY the value for localhost was missing and that caused the 503 error.
After adding localhost to NO_PROXY env variable, postman worked for my localhost adresses as well.
answered Dec 15 '16 at 14:06
WalterWalter
614
add a comment |
For test localhost turn off proxy configuration.
answered Jan 3 at 13:30
Luiz Fernando Corrêa LeiteLuiz Fernando Corrêa Leite
635
add a comment |
I tried to add the NO_PROXY env. var. to no avail.
Instead I changed the proxy setting (File - Settings), and add a global proxy configuration.
I put 127.0.0.1, and for the port, it has to be the port where our web app is located. (I found that the port number cannot be overridden through the URL). In your case, I suppose it is 80.
Might not be the best workaround, nevertheless it worked.
(Postman ver: 6.7.3)
answered Feb 26 at 0:15
Leonard ABLeonard AB
11112
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f40280814%2fnative-postman-returns-503-when-posting-to-localhost-but-chrome-postman-extensio%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had the same problem.
In my case env variables HTTP_PROXY, HTTPS_PROXY and NO_PROXY where set in my envirionment.
But in NO_PROXY the value for localhost was missing and that caused the 503 error.
After adding localhost to NO_PROXY env variable, postman worked for my localhost adresses as well.
answered Dec 15 '16 at 14:06
WalterWalter
614
add a comment |
I had the same problem.
In my case env variables HTTP_PROXY, HTTPS_PROXY and NO_PROXY where set in my envirionment.
But in NO_PROXY the value for localhost was missing and that caused the 503 error.
After adding localhost to NO_PROXY env variable, postman worked for my localhost adresses as well.
answered Dec 15 '16 at 14:06
WalterWalter
614
add a comment |
I had the same problem.
In my case env variables HTTP_PROXY, HTTPS_PROXY and NO_PROXY where set in my envirionment.
But in NO_PROXY the value for localhost was missing and that caused the 503 error.
After adding localhost to NO_PROXY env variable, postman worked for my localhost adresses as well.
answered Dec 15 '16 at 14:06
WalterWalter
614
I had the same problem.
In my case env variables HTTP_PROXY, HTTPS_PROXY and NO_PROXY where set in my envirionment.
But in NO_PROXY the value for localhost was missing and that caused the 503 error.
After adding localhost to NO_PROXY env variable, postman worked for my localhost adresses as well.
answered Dec 15 '16 at 14:06
WalterWalter
614
answered Dec 15 '16 at 14:06
WalterWalter
614
answered Dec 15 '16 at 14:06
WalterWalter
614
answered Dec 15 '16 at 14:06
WalterWalter
614
614
add a comment |
add a comment |
For test localhost turn off proxy configuration.
answered Jan 3 at 13:30
Luiz Fernando Corrêa LeiteLuiz Fernando Corrêa Leite
635
add a comment |
For test localhost turn off proxy configuration.
answered Jan 3 at 13:30
Luiz Fernando Corrêa LeiteLuiz Fernando Corrêa Leite
635
add a comment |
For test localhost turn off proxy configuration.
answered Jan 3 at 13:30
Luiz Fernando Corrêa LeiteLuiz Fernando Corrêa Leite
635
For test localhost turn off proxy configuration.
answered Jan 3 at 13:30
Luiz Fernando Corrêa LeiteLuiz Fernando Corrêa Leite
635
answered Jan 3 at 13:30
Luiz Fernando Corrêa LeiteLuiz Fernando Corrêa Leite
635
answered Jan 3 at 13:30
Luiz Fernando Corrêa LeiteLuiz Fernando Corrêa Leite
635
answered Jan 3 at 13:30
Luiz Fernando Corrêa LeiteLuiz Fernando Corrêa Leite
635
635
add a comment |
add a comment |
I tried to add the NO_PROXY env. var. to no avail.
Instead I changed the proxy setting (File - Settings), and add a global proxy configuration.
I put 127.0.0.1, and for the port, it has to be the port where our web app is located. (I found that the port number cannot be overridden through the URL). In your case, I suppose it is 80.
Might not be the best workaround, nevertheless it worked.
(Postman ver: 6.7.3)
answered Feb 26 at 0:15
Leonard ABLeonard AB
11112
add a comment |
I tried to add the NO_PROXY env. var. to no avail.
Instead I changed the proxy setting (File - Settings), and add a global proxy configuration.
I put 127.0.0.1, and for the port, it has to be the port where our web app is located. (I found that the port number cannot be overridden through the URL). In your case, I suppose it is 80.
Might not be the best workaround, nevertheless it worked.
(Postman ver: 6.7.3)
answered Feb 26 at 0:15
Leonard ABLeonard AB
11112
add a comment |
I tried to add the NO_PROXY env. var. to no avail.
Instead I changed the proxy setting (File - Settings), and add a global proxy configuration.
I put 127.0.0.1, and for the port, it has to be the port where our web app is located. (I found that the port number cannot be overridden through the URL). In your case, I suppose it is 80.
Might not be the best workaround, nevertheless it worked.
(Postman ver: 6.7.3)
answered Feb 26 at 0:15
Leonard ABLeonard AB
11112
I tried to add the NO_PROXY env. var. to no avail.
Instead I changed the proxy setting (File - Settings), and add a global proxy configuration.
I put 127.0.0.1, and for the port, it has to be the port where our web app is located. (I found that the port number cannot be overridden through the URL). In your case, I suppose it is 80.
Might not be the best workaround, nevertheless it worked.
(Postman ver: 6.7.3)
answered Feb 26 at 0:15
Leonard ABLeonard AB
11112
answered Feb 26 at 0:15
Leonard ABLeonard AB
11112
answered Feb 26 at 0:15
Leonard ABLeonard AB
11112
answered Feb 26 at 0:15
Leonard ABLeonard AB
11112
11112
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f40280814%2fnative-postman-returns-503-when-posting-to-localhost-but-chrome-postman-extensio%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
