connect() failed (113: No route to host) while connecting to upstream #4266
Unanswered
CodeWithCJ
asked this question in
Q&A
Replies: 1 comment
-
workaround I found is to add below code to NPM. Then I was able to use curl ip:port inside docker console of nginx proxy manager. This is the only way I can make things work. But for some reason,. without this it works in my another home server. I spent already 6+ hours on this stupid issue. So going to leave this though it is risk to mape nginx proxy manager as host network mode.
|
Beta Was this translation helpful? Give feedback.
0 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.
-
I am getting below error suddenly
2024/12/29 23:37:49 [error] 198#198: *3 connect() failed (113: No route to host) while connecting to upstream, client: MYIP, server: home.mydomain.buzz, request: "GET / HTTP/1.1", upstream: "http://10.0.0.10:3000/", host: "home.mydomain.buzz"
also "curl ip:port" also not working. basically npm unable to connect to my other services running in docker or inside the server.
below is my compose file and i am running npm via portainer.
my portainer compose:
With the same setup., I have another server in which "curl IP:PORT" works inside docker console of NPM. But in my oracle server, it is not working. I tried removing npm including the volume directories and re-created but still didn't work.
Beta Was this translation helpful? Give feedback.
All reactions