cockpit-ws — Cockpit web service
The cockpit-ws program is the web service component used for communication between the browser application and various configuration tools and services like cockpit-bridge(8).
Users or administrators should never need to start this program as it automatically started by systemd(1) on bootup.
To specify the TLS certificate the web service should use, simply
drop a file with the extension
.cert in the
/etc/cockpit/ws-certs.d directory. If there are
multiple files in this directory, then the highest priority one
is chosen after sorting.
.cert file should contain at least two
OpenSSL style PEM blocks. First one or more
blocks for the server certificate and intermediate certificate authorities
and a last one containing a
BEGIN PRIVATE KEY or similar.
The key may not be encrypted.
If there is no TLS certificate, a self-signed certificate is
automatically generated using openssl and stored in
0-self-signed.cert file. To check which certificate
cockpit-ws will use run the following command.
$ sudo remotectl certificate
When started via systemd(1) then cockpit-ws will exit after 90 seconds if nobody logs in, or after the last user is disconnected.
Show help options.
Normally cockpit-ws uses
cockpit-session and PAM to authenticate the user and start a
user session. With this option enabled, it will instead authenticate via SSH at
Serve HTTP requests
Bind to address
Don't use TLS.
The cockpit-ws process will use the
environment variable from the
basedir spec to find its
In addition the
XDG_DATA_DIRS environment variable from the
can be used to override the location to serve static files from. These are the files that
are served to a non-logged in user.
Please send bug reports to either the distribution bug tracker or the upstream bug tracker.
Cockpit has been written by many contributors.