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.

Sign up for GitHub

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

Jump to bottom

Heroku on starting instance returns empty response. #14

Open
accolasia opened this issue Nov 10, 2016 · 1 comment
Open

Heroku on starting instance returns empty response. #14

accolasia opened this issue Nov 10, 2016 · 1 comment
Labels
bug

Comments

@accolasia
Copy link
Contributor

I've seen this happen 2x now with generating API keys.

In one case the API key was generated, but no response was returned. Retry cause duplicate key.
In another case no API key was generated, no error, but no response was returned. Retry worked fine.
@accolasia accolasia added the bug label Nov 10, 2016
@p3nGu1nZz
Copy link

i have seen this on other projects using heroku. Maybe related, but we would touch a public service endpoint before requesting real data. Maybe has something to do with the NAT in the cloud architecture? Just a possible assumption to maybe investigate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@accolasia @p3nGu1nZz