starred/webvirtmgr

Fork 0

mirror of https://github.com/retspen/webvirtmgr.git synced 2026-04-26 08:05:54 +03:00

[GH-ISSUE #180] webvirtmgr-novnc: [Errno 111] Connection refused #140

New issue

Closed

opened 2026-02-27 16:38:06 +03:00 by kerem · 10 comments

kerem commented

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

Owner

Originally created by @drakulavich on GitHub (Dec 23, 2013).
Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/180

Pre-conditions:
RHEL 6.5 with webvirtmgr and novnc package.
KVM host on RHEL 6.4 (192.168.116.194), vnc_listen is enabled in /etc/libvirt/qemu.conf.

How to reproduce the problem:

Run webvirtmgr-novnc script and try to open VM console:

python /var/www/webvirtmgr/console/webvirtmgr-novnc
WebSocket server settings:
  - Listen on 0.0.0.0:6080
  - Flash security policy server
  - No SSL/TLS support (no cert file)
  - proxying from 0.0.0.0:6080 to ignore:ignore

  1: 192.168.117.163: Plain non-SSL (ws://) WebSocket connection
  1: 192.168.117.163: Version hybi-13, base64: 'False'
  1: connecting to: 192.168.116.194:5900
  1: handler exception: [Errno 111] Connection refused

Could you explain, please, is it a bug or broken configuration?

Originally created by @drakulavich on GitHub (Dec 23, 2013). Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/180 Pre-conditions: RHEL 6.5 with webvirtmgr and novnc package. KVM host on RHEL 6.4 (192.168.116.194), vnc_listen is enabled in /etc/libvirt/qemu.conf. How to reproduce the problem: - Run webvirtmgr-novnc script and try to open VM console: ``` python /var/www/webvirtmgr/console/webvirtmgr-novnc WebSocket server settings: - Listen on 0.0.0.0:6080 - Flash security policy server - No SSL/TLS support (no cert file) - proxying from 0.0.0.0:6080 to ignore:ignore 1: 192.168.117.163: Plain non-SSL (ws://) WebSocket connection 1: 192.168.117.163: Version hybi-13, base64: 'False' 1: connecting to: 192.168.116.194:5900 1: handler exception: [Errno 111] Connection refused ``` Could you explain, please, is it a bug or broken configuration?

kerem closed this issue

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

kerem commented

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

Author

Owner

@k3oni commented on GitHub (Dec 23, 2013):

/etc/init.d/webvirtmgr-novnc start

@k3oni commented on GitHub (Dec 23, 2013): /etc/init.d/webvirtmgr-novnc start

kerem commented

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

Author

Owner

@retspen commented on GitHub (Dec 23, 2013):

Use https ?

@retspen commented on GitHub (Dec 23, 2013): Use https ?

kerem commented

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

Author

Owner

@drakulavich commented on GitHub (Dec 24, 2013):

@retspen
No, Apache config grabbed from wiki, no https.

I see another error on client side:

Failed to connect to server (code: 1006)

@drakulavich commented on GitHub (Dec 24, 2013): @retspen No, Apache config grabbed from wiki, no https. I see another error on client side: ``` Failed to connect to server (code: 1006) ```

kerem commented

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

Author

Owner

@retspen commented on GitHub (Dec 24, 2013):

Connected ?

$ telnet x.x.x.x 5900

@retspen commented on GitHub (Dec 24, 2013): Connected ? $ telnet x.x.x.x 5900

kerem commented

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

Author

Owner

@drakulavich commented on GitHub (Dec 24, 2013):

Yes, I could connect 5900 and 6080 via telnet.

@drakulavich commented on GitHub (Dec 24, 2013): Yes, I could connect 5900 and 6080 via telnet.

kerem commented

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

Author

Owner

@retspen commented on GitHub (Dec 24, 2013):

Are you have vncviewer, can you connect via vncviewer to port 5900 ?

@retspen commented on GitHub (Dec 24, 2013): Are you have vncviewer, can you connect via vncviewer to port 5900 ?

kerem commented

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

Author

Owner

@drakulavich commented on GitHub (Dec 24, 2013):

Sorry, I found my mistake.
VNC port for KVM host is 5901. If I run:

websockify 6080 192.168.116.45:5901

I could open VNC session via browser.

Is there a place to change port number for each server on webvirtmgr side?

@drakulavich commented on GitHub (Dec 24, 2013): Sorry, I found my mistake. VNC port for KVM host is 5901. If I run: ``` websockify 6080 192.168.116.45:5901 ``` I could open VNC session via browser. Is there a place to change port number for each server on webvirtmgr side?

kerem commented

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

Author

Owner

@retspen commented on GitHub (Dec 24, 2013):

You can set port in instance xml manual but webvirtmgr get port from libvirt auto. Hover mouse on button Console and you can see instance VNC port.

@retspen commented on GitHub (Dec 24, 2013): You can set port in instance xml manual but webvirtmgr get port from libvirt auto. Hover mouse on button Console and you can see instance VNC port.

kerem commented

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

Author

Owner

@drakulavich commented on GitHub (Dec 24, 2013):

Thanks for help.

I understood why VNC was not working with VMs. It seems like vnc_listen in /etc/libvirt/qemu.conf does't enable listening for external IP addresses.
I've added listen='0.0.0.0' to the graphics section of VM's config. It works after that.

@drakulavich commented on GitHub (Dec 24, 2013): Thanks for help. I understood why VNC was not working with VMs. It seems like `vnc_listen` in /etc/libvirt/qemu.conf does't enable listening for external IP addresses. I've added `listen='0.0.0.0'` to the `graphics` section of VM's config. It works after that.

kerem commented

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

Author

Owner

@retspen commented on GitHub (Dec 24, 2013):

If VM create before you change section "vnc_listen" in file /etc/libvirt/qemu.conf all vm not response to public interface. In next time try simple test:

$ netstat -ant | grep 590

Any time!

@retspen commented on GitHub (Dec 24, 2013): If VM create before you change section "vnc_listen" in file /etc/libvirt/qemu.conf all vm not response to public interface. In next time try simple test: $ netstat -ant | grep 590 Any time!

kerem referenced this issue

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

[PR #293] [MERGED] Add VNC keymap support and allow password clear #606