I know the cockpit.conf is loading properly because the other settings in there (LoginTitle, LoginTo, etc.) work properly.
Thanks!
Version of Cockpit
308-1~bpo12+1
Where is the problem in Cockpit?
Networking
Server operating system
Debian
Server operating system version
6.1.69
What browsers are you using?
Chrome
System log
Jan 10 20:29:02 terastation-1 cockpit-tls[3715]: cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received.
Jan 10 20:29:09 terastation-1 sudo[4598]: pam_unix(sudo:session): session closed for user root
Jan 10 20:29:10 terastation-1 sudo[4703]: ****** : TTY=pts/0 ; PWD=/home/****** ; USER=root ; COMMAND=/usr/bin/journalctl --since -1m
Jan 10 20:29:10 terastation-1 sudo[4703]: pam_unix(sudo:session): session opened for user root(uid=0) by ******(uid=1000)
I have the same problem. No matter what the 'Origins =' value in cockpit.conf is set to, appears to apply X-Frame-Options = sameorigin. Can anyone confirm this is actually a bug or did the handler change in someway?
Explain what happens
Hi, I have cockpit set up in an iframe on my server dashboard but cross-origin is getting in the way.
https://mysite.com
has an iframe pointing tohttps://192.168.0.2:9090
Updated my
cockpit.conf
to the following:I get a blocked connection and a server error if I attempt to open it directly (as is somewhat expected).
So, I updated my
cockpit.conf
to this:From what I understand, this should work, but I still get a blocked connection.
The cross-origin policy when I login directly (
https://192.168.0.2:9090
) is:The cross-origin policy given when loaded in the iframe (via
https://mysite.com
) is:I know the
cockpit.conf
is loading properly because the other settings in there (LoginTitle, LoginTo, etc.) work properly.Thanks!
Version of Cockpit
308-1~bpo12+1
Where is the problem in Cockpit?
Networking
Server operating system
Debian
Server operating system version
6.1.69
What browsers are you using?
Chrome
System log