I am using the desktop version of Postman at a client site to test an API. However, I am unable to access any SSL sites in Postman, such as the Git Hib API: https://api.github.com/users/karlgjertsen
However, I can make the same API call through Chrome, so this is Postman specific.
I assume it is down to proxy settings, but I am not sure how to view or update these in Postman. Has anyone had any experienced something similar?
asked Jul 6, 2017 at 9:57
Karl GjertsenKarl Gjertsen
4,6908 gold badges41 silver badges64 bronze badges
1
I turned OFF both Global Proxy Configuration and Use System Proxy in Settings->Proxy tab in Postman and it started to work.
answered May 6, 2019 at 0:01
1
This solved my issue :
The option «Respect HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables.» was selected by default in the proxy settings. I turned off this option and it worked for me.
answered Jul 13, 2020 at 9:38
0
Follow these steps on postman —
Go to file=>Settings => Proxy (Tab) and uncheck the «Use System Proxy» checkbox. That should work
answered Dec 2, 2020 at 10:41
2
Posting as the other solutions presented in this thread did not work in our corporate environment. We have a proxy configured on the network which uses Windows Default Credentials (username and password) for authentication. For whatever reason the browser knows how to pass these details with each request but postman does not by default.
Solution was to update the Default Proxy Configuration under settings -> proxy -> Default Proxy Configuration -> Tick ‘This proxy requires authentication’ then enter Windows Username and Password. Leave Use the system proxy and Add a custom proxy configuration settings disabled.
From the Windows start menu go to Change proxy settings and configure the host and port there.
Kannan K
4,4111 gold badge11 silver badges26 bronze badges
answered Jan 22, 2021 at 8:33
This turned out to be a local security policy that was applied to the machine in use. The local SSL proxy had a policy applied and it would not allow me to make a secure connection unless it was through a web browser.
answered Jul 17, 2017 at 13:07
Karl GjertsenKarl Gjertsen
4,6908 gold badges41 silver badges64 bronze badges
4
In my case I turned off the ‘Add a custom proxy configuration’ in File -> Settings -> Proxy tab and it solved the issue. No idea why it was on.
answered Apr 7 at 11:55
Guy_g23Guy_g23
3162 silver badges7 bronze badges
On Postman desktop version, setting is required to be updated.
Turn off «Use System Proxy» in the settings area.
Go to Settings (Gear Icon, Beside Invite Button)
Then go to Proxy menu item and TURN OFF Use System Proxy
See screenshot of the desktop version
On Newer Version of Postman
answered Aug 8 at 7:35
ShabiShabi
12 bronze badges
1
I am using the desktop version of Postman at a client site to test an API. However, I am unable to access any SSL sites in Postman, such as the Git Hib API: https://api.github.com/users/karlgjertsen
However, I can make the same API call through Chrome, so this is Postman specific.
I assume it is down to proxy settings, but I am not sure how to view or update these in Postman. Has anyone had any experienced something similar?
asked Jul 6, 2017 at 9:57
Karl GjertsenKarl Gjertsen
4,6908 gold badges41 silver badges64 bronze badges
1
I turned OFF both Global Proxy Configuration and Use System Proxy in Settings->Proxy tab in Postman and it started to work.
answered May 6, 2019 at 0:01
1
This solved my issue :
The option «Respect HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables.» was selected by default in the proxy settings. I turned off this option and it worked for me.
answered Jul 13, 2020 at 9:38
0
Follow these steps on postman —
Go to file=>Settings => Proxy (Tab) and uncheck the «Use System Proxy» checkbox. That should work
answered Dec 2, 2020 at 10:41
2
Posting as the other solutions presented in this thread did not work in our corporate environment. We have a proxy configured on the network which uses Windows Default Credentials (username and password) for authentication. For whatever reason the browser knows how to pass these details with each request but postman does not by default.
Solution was to update the Default Proxy Configuration under settings -> proxy -> Default Proxy Configuration -> Tick ‘This proxy requires authentication’ then enter Windows Username and Password. Leave Use the system proxy and Add a custom proxy configuration settings disabled.
From the Windows start menu go to Change proxy settings and configure the host and port there.
Kannan K
4,4111 gold badge11 silver badges26 bronze badges
answered Jan 22, 2021 at 8:33
This turned out to be a local security policy that was applied to the machine in use. The local SSL proxy had a policy applied and it would not allow me to make a secure connection unless it was through a web browser.
answered Jul 17, 2017 at 13:07
Karl GjertsenKarl Gjertsen
4,6908 gold badges41 silver badges64 bronze badges
4
In my case I turned off the ‘Add a custom proxy configuration’ in File -> Settings -> Proxy tab and it solved the issue. No idea why it was on.
answered Apr 7 at 11:55
Guy_g23Guy_g23
3162 silver badges7 bronze badges
On Postman desktop version, setting is required to be updated.
Turn off «Use System Proxy» in the settings area.
Go to Settings (Gear Icon, Beside Invite Button)
Then go to Proxy menu item and TURN OFF Use System Proxy
See screenshot of the desktop version
On Newer Version of Postman
answered Aug 8 at 7:35
ShabiShabi
12 bronze badges
1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
Assignees
Comments
Describe the bug
After the 7.28 update, I am unable to use a custom proxy, while connecting to any URL. Each call ends with an error:
Error: tunneling socket could not be established, statusCode=407
The rollback to 7.27 does not fix the problem. This was tested on several different machines, and the proxy stops working the moment when the 7.28 update is applied.
App information (please complete the following information):
- App Type Native App
- Postman Version 7.28
- OS: Windows 10
Hi,
I’m getting exactly the same error since the update to v7.28.0. I’ve also tried removing the custom proxy config completely and setting it once again, but it didn’t helped.
Other colleagues with v7.27.1 and the same proxy configuration can access still fine. Also executing a curl with that proxy worked fine.
Well, I expected at least some kind of response.
Since 7.28 you have started to encode the proxy password. The workaround is to stick to numbers/digits passwords only.
Mac 10.15.6 and PostMan v7.26 (upgraded to v7.28)
Ubuntu 20.04 and Postman v7.28
I have same problem.
Confirming this problem (macOS 10.14.6). Also experiencing the issue since updating to v7.28.
@orlowski-ra’s workaround of sticking to numbers/digits in the password is unfortunately not an option for me, as I am depending on my corporate environment’s password policy.
Same thing here, we’re stuck with calling APIs through VPN (proxy is needed and every call results in 407), and we cannot set the password as we want, due to password policy.
I am also facing same problem. I tried by setting proxy configuration manually but still it didn’t work. In the logs I can see
Error: tunneling socket could not be established, statusCode=407
Proxy
authenticate: true
disabled: false
host: «proxy-host»
match: {…}
password: «password»
port: 8080
tunnel: false
username: «username»
Postman for Mac
Version 7.29.1
OS X 19.6.0 / x64
macOs Catalina: version 10.15.6
Dear Postman maintainers, @DannyDainton, @codenirvana,
Is there any progress on this regression? Not only is this bug a major annoyance but it renders the program unusable for me and others in our proxy-bound environments at the moment.
Let us know if we can help squashing this problem, e.g. by providing logs or anything.
Thanks,
Manfred
As mentioned in #8783 (comment), is everyone facing this issue because of any special character in the username or password field?
@orlowski-ra @m-urban @stephan-tho @Rikysonic Can you provide the following details:
- Proxy Setting: Custom or System
- Proxy Type: HTTP, HTTPS or BOTH
- Any special character in username or password:
I am not able to reproduce this issue locally so I must be missing the character set to test with.
Hi @codenirvana,
Thank you for looking into this. Regarding your question:
Proxy Setting: System
Proxy Type: BOTH
Any special character in username or password: Yes, a hash character #
This only recently became a problem with v7.28, evidently on both macOS and also Windows (as mentioned by @orlowski-ra)
Hi @codenirvana,
below you find the requested information:
Proxy Setting: Custom
Proxy Type: BOTH
Any special character in username or password: Yes «_» character
Unfortunately the workaround (setting password without special characters) doesn’t work for me, because my corporate environment requires special characters.
Edit:
Sorry, forgot to mention it: Also my Username contains a backslash (DOMAIN\User)
Hi @codenirvana,
I can confirm that the problem is related to special characters, because if I remove the domain from username, and so the backslash (from DOMAIN\USERNAME to only USERNAME), then the 407 error disappears and everything works normally.
Here’s my configuration:
Proxy Setting: Custom
Proxy Type: BOTH
Any special character in username or password:
- Username has a backslash (DOMAIN\USERNAME);
- Password has no special characters, only uppercase, lowercase and numbers.
Thanks,
Riccardo
@codenirvana, were you able to reproduce this issue? Anything we can do to support?
I can confirm I’m experiencing the same problem when the password contains the # symbol.
Going through cURL works, but getting error 407 in postman
Are there already news related to that topic?
I’m still facing the same error in v7.34.0
Please let me know in case you need any additional information, in order to reproduce that issue. Thanks!
Is there any update on this bug, as I have changed the password and removed special characters. I am still facing the same issue
Hey everyone 👋
It took us a while to reproduce this issue locally and identify the root cause but finally, this issue will be fixed in the next app release (releasing this week).
We had to delay the release of the app, I’m reopening this issue for now and will close it again once 7.35 is widely available. 🙂
Loading
App Details:
Postman helps you develop APIs faster
Postman for Mac
Version 5.3.2
OS X 15.6.0 / x64
I have just switched to the Desktop app and was setting up some oauth endpoints. I was constantly getting ‘Could not get any response’.
With the resultant error:
Error: tunneling socket could not be established, statusCode=407 Proxy: host:"PROXY" port:8080 match:"http+https://*/*" Request Headers: cache-control:"no-cache" postman-token:"xxxxx-xxxxx-xxxxx-xxxxx-xxxxx" content-type:"application/json" Request Body:"{"grant_type": "password", "email": "xxxxxxxxxxx@xxxxxxxxxx.com", "password": "xxxxxxxxxxxxxxxxxxxx"}"
This appeard to be related to authentication over our corporate proxy. If I copy the setup as curl it works perfectly fine.
Is there any workaround to fix this, as of now I will have to take it off the network to do these requests. Strangely a GET for a google.co.uk has no problems but I think that is likely to be down to our proxy rules.