dial tcp: connect: no route to host
I am seeing a lot of these errors pop up randomly. sometimes my instance just can't reach a host for some reason. I tried to rebuild and disable some proxies the app was using. But things are still breaking intermittently.
Is there a way to check if this is a platform issue or something else?
90 Replies
Project ID:
30eb2ca4-aa10-44f8-b252-96cf312185bd
30eb2ca4-aa10-44f8-b252-96cf312185bd
hosts the app is trying to reach
do you happen to have static IPs enabled?
I am not sure, so I am assuming I do not. At least it's not something I ever looked into/needed
can you check in your service settings just to be sure please?
Ah it's a Pro feature - I do not
thanks, discord says you have a Pro badge so I thought id ask
raising your thread directly to the team now
an incident was just called #π¨ο½incidents
Here is a full log as well
The IPs are different, but it has been randomly happening for around a week now
you may not have static IPs enabled but static IPs would still be shared, so you could have ended up with a service being given the same IP
I don't think I have enough knowledge on networking :D
My setup is running 1 replica at a time that is trying to reach this, though some requests are made in parallel. The services I am trying to reach are from a 3rd party as well. Is there a way for static ip to cause an issue here?
Not sure how relevant this is, but same errors occured when I had an http proxy enabled for those request
well it doesn't explain why you have had issues for the past week, the incident description says it started today
but we can reassess this after the incident has been resolved
Here is the first log I am able to find on my end
interesting, that's from quite a while ago
yeah, I though this is an issue with the 3rd party service as their servers sometimes error out, so I did not report and tried to debug on my own
gotcha, we will come back to this once the team has confirmed the incident has been resolved
the incident has been marked as resolved, let me know if you continue to see this issue