[GH-ISSUE #479] Console ( novnc ) assumes KVM is running vnc on 127.0.0.1 #355

New issue

Open

opened 2026-02-27 16:38:59 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 16:38:59 +03:00

Owner

Originally created by @davidlublink on GitHub (Dec 9, 2014).
Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/479

If I have a virtual machine ( kvm ) with the following as the VNC display, everything works fine 👍

<graphics type='vnc' port='5911' autoport='yes' listen='127.0.0.1'>
  <listen type='address' address='127.0.0.1'/>
</graphics>

However, if I specify a binding address other than 127.0.0.1, vnc fails to connect. For example :

Extract from log :

2: connecting to: localhost:5955
2: handler exception: [Errno 111] Connection refused

Originally created by @davidlublink on GitHub (Dec 9, 2014). Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/479 If I have a virtual machine ( kvm ) with the following as the VNC display, everything works fine :+1: ``` <graphics type='vnc' port='5911' autoport='yes' listen='127.0.0.1'> <listen type='address' address='127.0.0.1'/> </graphics> ``` However, if I specify a binding address other than 127.0.0.1, vnc fails to connect. For example : <graphics type='vnc' port='5955' autoport='no' listen='192.168.2.11' keymap='en-us'> <listen type='address' address='192.168.2.11'/> </graphics> Extract from log : 2: connecting to: localhost:5955 2: handler exception: [Errno 111] Connection refused

kerem commented

2026-02-27 16:38:59 +03:00

Author

Owner

@davidlublink commented on GitHub (Dec 9, 2014):

Work around : Don't change the listen address of your virtual machines to anything other than localhost.

@davidlublink commented on GitHub (Dec 9, 2014): Work around : Don't change the listen address of your virtual machines to anything other than localhost.

kerem commented

2026-02-27 16:38:59 +03:00

Author

Owner

@brenard commented on GitHub (Jan 24, 2015):

Hello,

The last version known how to deal with this kind of configuration. Support of graphic device using Unix socket, or listenning on localhost on a remote host is recently had. In case of graphic device listenning on another address than localhost, WebVirtMrg will try to directly connect so your firewall have to leave it openned. You mean upgrade your installation.

@brenard commented on GitHub (Jan 24, 2015): Hello, The last version known how to deal with this kind of configuration. Support of graphic device using Unix socket, or listenning on localhost on a remote host is recently had. In case of graphic device listenning on another address than localhost, WebVirtMrg will try to directly connect so your firewall have to leave it openned. You mean upgrade your installation.