cockpit-ws

cockpit-ws — Cockpit web server

Synopsis

cockpit-ws [--help] [--port PORT] [--no-tls] [--local-ssh]

DESCRIPTION

The cockpit-ws program is the web server 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.

AUTHENTICATION

Access to the com.redhat.Cockpit D-Bus service via the /socket URI requires authentication - this is implemented by asking for the root password. Static files from /usr/share/cockpit/static are served without requiring any authentication.

TRANSPORT SECURITY

To specify the TLS certificate the web server 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. If there is no TLS certificate, a self-signed certificate is automatically generated using the /etc/pki/tls/certs/make-dummy-cert command and stored in /etc/cockpit/ws-certs.d/~self-signed.cert.

TIMEOUT

When started via systemd(1) then cockpit-ws will exit after 10 minutes if nobody logs in, or after the last user is disconnected.

OPTIONS

--help

Show help options.

--local-ssh

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 127.0.0.1 port 22.

--port PORT

Serve HTTP requests PORT instead of port 9090. Usually Cockpit is started on demand by systemd socket activation, and this option has no effect. Update the ListenStream directive cockpit.socket file in the usual systemd manner.

--no-tls

Don't use TLS.

BUGS

Please send bug reports to either the distribution bug tracker or the upstream bug tracker.

SEE ALSO

systemd(1)