I am trying to embed the Cockpit into our web application. When opening on Firefox,
it shows the expected warning about self signed certificate, however you cannot trust
the self signed certificate there, so is it possible to get around the exception as I
want the users to stay on this page ?
Hi, I did not find any information regarding the use of a http reverse
proxy (e. g. nginx) in front of the cockpit http server.
Specifically I want nginx to do all the TLS stuff while it connects to
cockpit via plain http.
I got this to work by changing the "Origin" Http-Header from https to
http. Otherwise cockpit complains about a "bad Origin".
I included the nginx config sample as attachment.
I hope this can help others trying to set this up with nginx and maybe
it can be added to the wiki on github.
As you may have noticed with previous releases, you could only add
servers with identical versions of Cockpit to the dashboard.
Our WebSocket based message protocol  for interacting from the Web
code with the server was not yet stable.
Going forward we'd like to guarantee that you can add servers to the
dashboard even if they run a different version of Cockpit.
This backwards-compatibility starts with version 0.48.
Versions of Cockpit later than 0.48 can be added to each others' dashboards.
We still reserve the right to change the protocol in the coming months,
as long as we don't break the above guarantee. In addition we have not