- Newest
- Most votes
- Most comments
The Security Group will not return a "connection refused" error. Security Groups act like firewalls. If the rules in the Security Group don't allow the traffic, then no response is returned, the packets will be dropped, and requests usually time out. "Connection Refused" generally means that you reached the host, on a particular network port, but the service you attempted to reach on that port is not listening on that port. For example, if you were trying to access HTTP on port 80, but the service was actually listening on port 8080, and nothing else was listening on port 80, then the attempt to request on port 80 would be refused by the host.
Additional troubleshooting should include trying to access the host:port from another host, preferably in the same network segment and affected by the same Security Groups. This troubleshooting document might help as well.
Relevant content
- asked 3 years ago
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
In addition to what @jimmyray suggested, I would recommend reading https://learnk8s.io/kubernetes-network-packets#inspecting-pod-to-service-traffic. It will help you diagnose the issue you're having.
Thanks @Jimmyray and @Jeremy.
I was able to deploy internal Loadbalancer which let me access the ansible AWX instance from premises environment. Now, I want to manage target hosts on premises. How to open the needed flow?