-
Notifications
You must be signed in to change notification settings - Fork 191
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
Something went wrong, please contact the application owner. #248
Comments
Seeing this as well. What's strange is that restarting the Heroku dyno allows it to start working again, but then after awhile this message appears again. |
Here's a gist from the logs when the requests are failing. https://gist.github.com/jabeler/1b99fd5eae49ab7b6ebecae42e8ed719 I've testing under Ruby 2.4.6, 2.5.5, and 2.6.3 with the same results. |
I get this after restarting dynos:
Assuming the app needs to be upgraded? |
Unfortunately I am facing the same issue. Did you find a way to resolve that @jabeler ? |
I just deployed boarding to Azure but when I try to add a new tester, I get an error:
Looks like something went wrong with boarding trying to talk to ITC.
The text was updated successfully, but these errors were encountered: