-
Notifications
You must be signed in to change notification settings - Fork 139
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
nut-client - "Connection Refused" despite being able to connect inside dnsutils, and router detects no connection attempt #618
Comments
You could test with |
Pod can still connect in hostNetwork, "nut-client" still reporting "connection refused". |
is this with a dns name or an ip, maybe the dns resolution of nut-client is broken |
what does |
Apologises for the delay, was at university all day.
|
Exactly as the title says. I can confirm that I can connect to the Network UPS Tools server from inside a container (which uses the IP of the host), the inter-network router sitting between my node and the NUT server can detect this connection. Yet when running the nut-client extension, it reports "Connection refused", yet the router reports no connection. Seems like the extension is broken at the moment, I sincerely doubt Cilium or Multus is causing this issue, as a connection from inside the container is working correctly.
Pod used to test:
The text was updated successfully, but these errors were encountered: