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 unable to look up things or thing graphs since update #2223

Closed
grace-spitzer-wong opened this issue Aug 3, 2016 · 8 comments
Closed

Comments

@grace-spitzer-wong
Copy link

Hi

I've been using Postman to look up thing graphs and things but for an unknown reason since the recent update, I'm getting this error message and it takes a long time to send and get the error:

Could not get any response
There was an error connecting to xxx
Why this might have happened:
The server couldn't send a response: - Server is working
Ensure that the backend is working properly - all correct
Self-signed SSL certificates are being blocked: - certificates all fine
Fix this by turning off 'SSL certificate verification' in Settings > General - done
Request timeout:
Change request timeout in Settings > General - done

My colleague has no problems.

Any ideas?

Thanks

@TTN-js
Copy link

TTN-js commented Aug 3, 2016

I have this issues as well (Using to test API). It looks like its only a problem on the packaged app. I tested things on the chrome extension and things seem to work fine.

Has your colleague updated?

@mayken
Copy link

mayken commented Aug 3, 2016

i have the same problem. v4.5.0

@TTN-js
Copy link

TTN-js commented Aug 3, 2016

Probably related to issue #2217 and #2214. Looks like they are working on it.

@grace-spitzer-wong
Copy link
Author

Wanted to test on Chrome extension but for some reason when I try to get the extension, it won't let me as I have the app installed.

@grace-spitzer-wong
Copy link
Author

@TTN-js thanks for flagging the associated issue.

@TTN-js
Copy link

TTN-js commented Aug 3, 2016

@Grace-W That's weird. Maybe uninstall the packaged app and get the chrome extension for the time being?

@a85
Copy link
Contributor

a85 commented Aug 4, 2016

Thanks for the report. We are working hard on fixing these asap.

@shamasis
Copy link
Member

shamasis commented Aug 5, 2016

This is addressed in 4.5.1. Closing as duplicate.

@shamasis shamasis closed this as completed Aug 5, 2016
@abhijitkane abhijitkane removed the bug label Aug 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants