Context deadline exceeded #213
Unanswered
dberrocal-git
asked this question in
Q&A
Replies: 2 comments 3 replies
-
Can you share your logs (hide credentials)? I checked the code (on my phone), it looks fine but I'll recheck tomorrow more in depth. Also you may want to use DNS as a way to get your IP address with |
Beta Was this translation helpful? Give feedback.
0 replies
-
Uh strange, I reviewed the code and it looks like it's applying the http timeout correctly. I'm going to refractor a lot of the configuration / env variables code soon (tomorrow I think) so that might squish out that issue, I'll get back to you. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The update is delayed for minuntes, until it eventually manages to get the IP address, resulting in every call to the address to get the IP, for example:
ERROR Get "https://api.ipify.org": context deadline exceeded
I have changed the option: HTTP_TIMEOUT=50s
But when I restart the environment it instantly jumps to context deadline exceeded
What could I be doing wrong?
Beta Was this translation helpful? Give feedback.
All reactions