[GH-ISSUE #596] not connected ([Errno 111] Connection refused) #451

New issue

Open

opened 2026-02-27 16:39:20 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 16:39:20 +03:00

Owner

Originally created by @balakrishnanvbs on GitHub (Jan 19, 2016).
Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/596

not connected ([Errno 111] Connection refused) in WebVirtMgr.Anyone plz help

Originally created by @balakrishnanvbs on GitHub (Jan 19, 2016). Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/596 not connected ([Errno 111] Connection refused) in WebVirtMgr.Anyone plz help

kerem commented

2026-02-27 16:39:20 +03:00

Author

Owner

@Azendale commented on GitHub (Sep 6, 2016):

You gave very few details, so I'm having to guess, but it sounds like webvirtmgr can't connect to your hypervisor. What kind of connection do you have to the hypervisor? SSH? TCP? Local Socket? TLS? If it is anything other than local socket, see if you can ping the hypervisor from the webvirtmgr server.

Depending on how you are connecting, the port number will vary, but I know it's 22 for SSH (by default of course, if you have changed the SSH port on your hypervisor then it will be different). You can test to see if the port is open from the webvirtmgr by installing nmap, and then doing something like 'nmap -p22 192.168.7.23' (Assuming that you are using SSH on the default port (22) and the hypervisor IP is 192.168.7.23, adjust as necessary). If it doesn't say the port is open, investigate the network between the two: there may be a firewall (or even a firewall running on the hypervisor).

@Azendale commented on GitHub (Sep 6, 2016): You gave very few details, so I'm having to guess, but it sounds like webvirtmgr can't connect to your hypervisor. What kind of connection do you have to the hypervisor? SSH? TCP? Local Socket? TLS? If it is anything other than local socket, see if you can ping the hypervisor from the webvirtmgr server. Depending on how you are connecting, the port number will vary, but I know it's 22 for SSH (by default of course, if you have changed the SSH port on your hypervisor then it will be different). You can test to see if the port is open from the webvirtmgr by installing nmap, and then doing something like 'nmap -p22 192.168.7.23' (Assuming that you are using SSH on the default port (22) and the hypervisor IP is 192.168.7.23, adjust as necessary). If it doesn't say the port is open, investigate the network between the two: there may be a firewall (or even a firewall running on the hypervisor).