Skip to content
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

Postman couldn't connect to the internet #8921

Closed
erlendl opened this issue Aug 12, 2020 · 5 comments
Closed

Postman couldn't connect to the internet #8921

erlendl opened this issue Aug 12, 2020 · 5 comments
Labels
support How do I ... ? Can I ... ?

Comments

@erlendl
Copy link

erlendl commented Aug 12, 2020

Describe the bug
Postman desktop client (Mac) reports "Postman couldn't connect to the internet".
Screenshot 2020-08-12 at 11 23 06

I am successfylly authenticating with "Sign in with Google". All request succeeds. All other internet activity works as expected from the computer. Hence, the internet connection is up and running, but Postman is not able to connect to its cloud services and sync workspaces.

To Reproduce
Steps to reproduce the behavior:

  1. Start Postman and sign in
  2. Observe sync button in toolbar is red
  3. Click browse in bottom toolbar
  4. Postman states "Looks like you're offline"

Expected behavior
We expect Postman to be online with its cloud services and sync successfully.

Screenshots
The console viewed from menu item "Developer | Show Dev Tools (Shared)" shows an error "Failed to load resource: net: ERR_CER_COMMON_NAME_INVALID"
Screenshot 2020-08-12 at 11 30 47

Screenshot 2020-08-12 at 11 43 07

App information (please complete the following information):

  • Desktop app for Mac
  • Postman Version 7.30.1 and PostmanCanary 7.30.0-canary02
  • OS: macOS Catalina 10.15.5

Additional context
From the developer console log it seems that the request to https://bifrost-v4.getpostman.com/ws/connect fails due to an invalid certificate. When the URL https://bifrost-v4.getpostman.com/ws/connect is put in Safari, Safari reponds with this message.
Screenshot 2020-08-12 at 11 55 54

Chrome agrees with certificate problems:
Screenshot 2020-08-12 at 11 56 34

Old Postman Chrome Extensions successfully connects with an enabled sync button, but workspaces are upgraded to newer versions and does not work with the extension.

@DannyDainton
Copy link
Contributor

Hey @erlendl

That's interesting? I'm not seeing this on my side for either the Production or Canary app. 🤔

Hate to be that guy...have you tried quitting the app and restarting it again to try and establish the connection?

Are you currently on a VPN, behind a firewall or using some sort of proxy on your machine?

You could head over to web.postman.co and use Postman's web version to see if that's going to unblock you in the short term?

@DannyDainton DannyDainton added the support How do I ... ? Can I ... ? label Aug 12, 2020
@erlendl
Copy link
Author

erlendl commented Aug 12, 2020

Hey @erlendl

That's interesting? I'm not seeing this on my side for either the Production or Canary app. 🤔

Hate to be that guy...have you tried quitting the app and restarting it again to try and establish the connection?

Are you currently on a VPN, behind a firewall or using some sort of proxy on your machine?

You could head over to web.postman.co and use Postman's web version to see if that's going to unblock you in the short term?

Hi @DannyDainton

Thanks for your reply.

I have done the basics - and then some :-). Quitted app, updated to latest version, unistalled and installed multiple times, restarted pc and so on.
I am not on a VPN, do not use any sort of proxy but is behind a standard router firewall which is not configured besides ordinary configurations.
I haven't noticed that there are any requirements to open any special ports in firewall for Postman (?).

I have already used web.postman.co as a workaround - thanks for the tip.

@erlendl
Copy link
Author

erlendl commented Aug 12, 2020

I updated firmware on the router, and the certificate error accessing https://bifrost-v4.getpostman.com/ws/connect is no gone. This case may be closed.

@DannyDainton
Copy link
Contributor

So you're all good and running on the native app now?

@DannyDainton
Copy link
Contributor

I'm going to close this for now.

If you run into any other Network issues, you can open a support ticket and send logs/a network profile to help@postman.com, so we can look further into the issue. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support How do I ... ? Can I ... ?
Projects
None yet
Development

No branches or pull requests

2 participants