Bug 1671147

Summary: RHEL 8 Cockpit - "Launch Remote Viewer" in Virtual Machines section does not work remotely
Product: Red Hat Enterprise Linux 8 Reporter: Robert McSwain <rmcswain>
Component: cockpitAssignee: Martin Pitt <mpitt>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.0CC: chayang, jinzhao, juzhang, michen, nanliu, rbalakri, ribarry, virt-maint, zhguo
Target Milestone: rc   
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-31 19:42:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot of remote-viewer window after lauching Remote Viewer from Firefox none

Description Robert McSwain 2019-01-30 21:30:57 UTC 
Created attachment 1525148 [details]
Screenshot of remote-viewer window after lauching Remote Viewer from Firefox

Description of problem:
When accessing https://FQDN:9090/machines and clicking "Launch Remote Viewer" this fails to open a console. It seems to want a localhost connection to the server through a locally hosted browser, not a remote session from elsewhere on the network. 

Version-Release number of selected component (if applicable):
qemu-kvm-2.12.0-57.module+el8+2683+02b3b955.x86_64
cockpit-185-1.el8.x86_64

How reproducible:
100% thus far

Steps to Reproduce:
0. Disable firewalld to ensure open connectivity
1. Visit https://FQDN:9090/machines 
2. Choose a VM
3. Click "Launch Remote Viewer" 

Actual results:
Receive error "Unable to connect to the graphic server /tpm/mozilla_$USER0/[unique string] 
Could not connect to 127.0.0.1: Connection refused"
This does not occur when using `ssh -Y root@fqdn` and then launching firefox through with x-forwarding enabled. Console access is then available. Same is true with virt-manager through x-forwarding

Expected results:
VM console access available from any browser cockpit can be accessed by.

Additional info:
Comment 1 Rick Barry 2019-01-31 18:53:21 UTC 
Cockpit team, can you take a look at this?
Comment 2 Martin Pitt 2019-01-31 19:42:08 UTC 

*** This bug has been marked as a duplicate of bug 1558219 ***