-
Notifications
You must be signed in to change notification settings - Fork 34
Client times out #2
Comments
"times out"? There is no timeout when running one-off dynos (except the 24 hours cycling). |
host could not be reached (since it was restarting). Sorry the exact message is gone from my history. I updated line 76 of |
To be clear, my production app could not be reached. |
If your app takes longer than 20 seconds to boot, that could indeed cause issues. |
Agreed on needing to boot faster. That being said I'd also like to use Heroku preboot. I believe this would need to wait ~3-5 minutes for it to work with preboot. Would you accept a pull request that takes a custom sleep time? |
Sure. When adding it to app.json, could you add a mention about long boot time and the risk of H12s in the description? |
Sounds good. Time to learn some Go :) |
We had this problem today: We used preboot, so env vars take ~3 minutes to update. When Sabayon checked |
@apeckham set |
When I run the
sabayon
command it updates theACME_KEY
andACME_TOKEN
config vars of my production app, thus restarting it.Then it tries to validate against the validation URL, but the app is restarting and sabayon times out.
The text was updated successfully, but these errors were encountered: