Replies: 2 comments 7 replies
-
A bit more information about this: I setup a test environment to experiment with some of the other cockpit.conf options. None seemed to do the trick, however I was able to get Cockpit running in an Organizr iFrame by using the Chrome extension "Ignore X-Frame headers". Not really an ideal solution, though I did limit its access to the host computer in the form http://hostname.localdomain. However, it is confirmation that the change in Cockpit's X-Frame Options are the likely issue. So, still looking for a better solution that will work with all browsers, and doesn't require an extension to be loaded. These are the cockpit.conf options I tried:
I used them as shown above, but I'm wondering if that's correct or if the values shown are just placeholders? |
Beta Was this translation helpful? Give feedback.
-
I have a similar issue. I am using Cockpit through a Custom New Tab Page firefox extension. Due to limitations of Firefox itself (as long as I understand it), it is forcing the pages that would appear in nte tab to be inside an iframe, although it tries its best at least to expose the external url on the taskbar. So, when I am using cokcpit, although I can go to the correct URL, I have to click on the URL bar, to set the focus, then press enter, to reload the page (and get rid of the iframe) and then login to cockpit. Is there any way to make things easier than this? Thank you! |
Beta Was this translation helpful? Give feedback.
-
Happy New Year! Big fan of Cockpit, and I've been using it successfully for several years in an Organizr iFrame with:
I recently attempted to upgrade from the version in the Debian 11 stable repository to bullseye-backports (v239 to v282), and although the AllowUnencrypted option still works, I can no longer load Cockpit in an iFrame. Is this still possible, or am I stuck on v239?
Beta Was this translation helpful? Give feedback.
All reactions