1COCKPIT.CONF(5)                  cockpit.conf                  COCKPIT.CONF(5)
2
3
4

NAME

6       cockpit.conf - Cockpit configuration file
7

DESCRIPTION

9       Cockpit can be configured via /etc/cockpit/cockpit.conf. That file has
10       a INI file syntax and thus contains key / value pairs, grouped into
11       topical groups. See the examples below for details..
12
13       Note: The port that cockpit listens on cannot be changed in this file.
14       To change the port change the systemd cockpit.socket file.
15

WEBSERVICE

17       Origins
18           By default cockpit will not accept crossdomain websocket
19           connections. Use this setting to allow access from alternate
20           domains. Origins should include scheme, host and port, if
21           necessary.
22
23               [WebService]
24               Origins = https://somedomain1.com https://somedomain2.com:9090
25
26       ProtocolHeader
27           Configure cockpit to look at the contents of this header to
28           determine if a connection is using tls. This should only be used
29           when cockpit is behind a reverse proxy, and care should be taken to
30           make sure that incoming requests cannot set this header.
31
32               [WebService]
33               ProtocolHeader = X-Forwarded-Proto
34
35       LoginTitle
36           Set the browser title for the login screen.
37
38       LoginTo
39           When set to true the Connect to option on the login screen is
40           visible and allows logging into another server. If this option is
41           not specified then it will be automatically detected based on
42           whether the cockpit-ssh process is available or not.
43
44       RequireHost
45           When set to true cockpit will require users to use the Connect to
46           option to specify the host to log into.
47
48       MaxStartups
49           Same as the sshd configuration option by the same name. Specifies
50           the maximum number of concurrent login attempts allowed. Additional
51           connections will be dropped until authentication succeeds or the
52           connections are closed. Defaults to 10.
53
54           Alternatively, random early drop can be enabled by specifying the
55           three colon separated values start:rate:full (e.g. "10:30:60").
56           Cockpit will start refusing authentication attempts with a
57           probability of rate/100 (30%) if there are currently start (10)
58           unauthenticated connections. The probability increases linearly and
59           all connection attempts are refused if the number of
60           unauthenticated connections reaches full (60).
61
62       AllowUnencrypted
63           If true, cockpit will accept unencrypted HTTP connections.
64           Otherwise, it redirects all HTTP connections to HTTPS. Exceptions
65           are connections from localhost and for certain URLs (like /ping).
66           Defaults to false.
67
68       UrlRoot
69           The root URL where you will be serving cockpit. When provided
70           cockpit will expect all requests to be prefixed with the given url.
71           This is mostly useful when you are using cockpit behind a reverse
72           proxy, such as nginx.  /cockpit/ and /cockpit+ are reserved and
73           should not be used. For example /cockpit-