Duh, too long a day.

I disabled the spice proxy in the console options.

Still doesn't explain why it also fails when using the userportal console.

Regards,

Jorick Astrego

Hi,

Having a spice console issue on our new 4.3.8 cluster. The console stays blank and with the cli and debug on, I get the following error "main channel: failed to connect HTTP proxy connection not allowed"

We have a userportal through haproxy so this is configured in ovirt engine

engine-config -g SpiceProxyDefault
SpiceProxyDefault: http://userportal.*.*:****/ version: general

But the same setting works fine on our 4.2 cluster.

I can telnet to the ports on the 4.3.8 hosts without issue.

Non working console on newer cluster:

remote-viewer -v --debug console.vv
(remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.697: Opening display to console.vv
(remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.700: Guest (null) has a spice display
Guest (null) has a spice display
(remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.789: Spice foreign menu updated
(remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.790: After open connection callback fd=-1
(remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.790: Opening connection to display at console.vv
Opening connection to display at console.vv
(remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.791: fullscreen display 0: 0
(remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.791: app is not in full screen
(remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.792: New spice channel 0x55704bf70d40 SpiceMainChannel 0
(remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.793: notebook show status 0x55704b820280
(remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.969: main channel: failed to connect HTTP proxy connection not allowed
(remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.969: Destroy SPICE channel SpiceMainChannel 0
(remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.969: zap main channel

(remote-viewer:29267): virt-viewer-WARNING **: 16:24:24.969: Channel error: HTTP proxy connection not allowed

Working console on older cluster:

remote-viewer -v --debug console.vv
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.111: Opening display to console.vv
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.111: Guest (null) has a spice display
Guest (null) has a spice display
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.209: Spice foreign menu updated
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.209: After open connection callback fd=-1
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.209: Opening connection to display at console.vv
Opening connection to display at console.vv
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.211: fullscreen display 0: 0
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.211: app is not in full screen
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.212: New spice channel 0x556a03f7e820 SpiceMainChannel 0
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.212: notebook show status 0x556a03c7a280
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.397: main channel: opened
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.397: notebook show status 0x556a03c7a280
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.404: virt_viewer_app_set_uuid_string: UUID changed to a2d64ffe-7583-45b6-92f3-87661039388c
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.404: app is not in full screen
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.502: app is not in full screen
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.514: New spice channel 0x556a043bb660 SpiceDisplayChannel 0
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.514: New spice channel 0x556a0422b570 SpiceCursorChannel 0
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.515: New spice channel 0x556a0422c000 SpiceInputsChannel 0
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.515: new inputs channel
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.661: creating spice display (#:0)
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.661: Insert display 0 0x556a03ca29e0
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.699: creating spice display (#:1)
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.699: Insert display 1 0x556a03ca2830
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.699: creating spice display (#:2)
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.700: Insert display 2 0x556a03ca2680
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.700: creating spice display (#:3)
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.700: Insert display 3 0x556a03ca24d0
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.701: Found a window without a display, reusing for display #0
(remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.701: notebook show display 0x556a03c7a280
(remote-viewer:29334): virt-viewer-DEBUG: 16:26:00.074: Allocated 1024x768
(remote-viewer:29334): virt-viewer-DEBUG: 16:26:00.074: Child allocate 1024x768
(remote-viewer:29334): virt-viewer-DEBUG: 16:26:04.846: Allocated 1024x768
(remote-viewer:29334): virt-viewer-DEBUG: 16:26:04.846: Child allocate 1024x768