Chapter 1. Getting started with the RHEL web console


Learn how to install, configure, and monitor systems by using the RHEL web console. This graphical interface simplifies common administration tasks, such as managing logs, storage, and remote hosts.

1.1. What is the RHEL web console

The RHEL web console is a web-based graphical interface for managing and monitoring your local system and Linux servers in your network environment.

In the RHEL web console, you can perform a wide range of administration tasks, including:

  • Managing services
  • Managing user accounts
  • Managing and monitoring system services
  • Configuring network interfaces and firewall
  • Reviewing system logs
  • Managing virtual machines
  • Creating diagnostic reports
  • Setting kernel dump configuration
  • Configuring SELinux
  • Updating software
  • Managing system subscriptions

The web console uses the same system tools as the command line. If you change a setting in the terminal, the web console updates instantly. You can switch between the web interface and the terminal at any time.

You can also monitor the logs and performance of systems in the network environment in a graphical form. In addition, you can change the settings directly in the web console or through the terminal.

1.2. Installing and enabling the web console

To access the RHEL web console, enable the cockpit.socket service first. RHEL 10 includes the web console installed by default in many installation variants. If this is not the case on your system, install the cockpit package before enabling the cockpit.socket service.

Procedure

  1. If the web console is not installed by default on your installation variant, manually install the cockpit package:

    # dnf install cockpit
    Copy to Clipboard Toggle word wrap
  2. Enable and start the cockpit.socket service, which runs a web server:

    # systemctl enable --now cockpit.socket
    Copy to Clipboard Toggle word wrap
  3. If the web console was not installed by default on your installation variant and you are using a custom firewall profile, add the cockpit service to firewalld to open port 9090 in the firewall:

    # firewall-cmd --add-service=cockpit --permanent
    # firewall-cmd --reload
    Copy to Clipboard Toggle word wrap

Verification

1.3. Logging in to the web console

When the cockpit.socket service is running and the corresponding firewall port is open, you can log in to the web console in your browser for the first time.

Prerequisites

  • Use one of the following browsers to open the web console:

    • Mozilla Firefox 52 and later
    • Google Chrome 57 and later
    • Microsoft Edge 16 and later
  • System user account credentials

    The RHEL web console uses a specific pluggable authentication modules (PAM) stack at /etc/pam.d/cockpit. The default configuration allows logging in with the user name and password of any local account on the system.

  • Port 9090 is open in your firewall.

Procedure

  1. In your web browser, enter the following address to access the web console:

    https://localhost:9090
    Copy to Clipboard Toggle word wrap
    Note

    This provides a web-console login on your local machine. If you want to log in to the web console of a remote system, see the Connecting to the web console from a remote machine section.

    If you use a self-signed certificate, the browser displays a warning. Check the certificate, and accept the security exception to proceed with the login.

    The console loads a certificate from the /etc/cockpit/ws-certs.d directory and uses the last file with a .cert extension in alphabetical order. To avoid having to grant security exceptions, install a certificate signed by a certificate authority (CA).

  2. In the login screen, enter your system user name and password.
  3. Click Log In.

    After successful authentication, the RHEL web console interface opens.

1.4. Administrative access in the web console

You can gain administrative access in the RHEL web console to perform privileged tasks, such as managing services, users, and networking, which require elevated permissions.

After you log in for the first time with a regular user account, the web console starts with limited access. When you have limited access, you can view the settings, but you cannot perform actions that require administrative privileges, such as installing packages.

To perform administrative tasks, click Limited access in the top panel of the web console page. You must have sudo access to the system and provide your user password to gain administrative access. From that point, the web console provides administrative access and preserves this setting across user sessions.

To switch back to limited access, click Administrative access in the top panel of the web console page.

Important

The RHEL web console disallows root account logins by default for security reasons. Instead of logging in as root, use administrative access. If your scenario requires logging in as root, see Connecting to the web console from a remote machine as a root user

Disable basic authentication for the RHEL web console to enforce stronger authentication methods, such as Kerberos. You can configure this setting in the cockpit.conf file to override default security behavior.

Use the none action to disable an authentication scheme and only allow authentication through GSSAPI and forms.

Prerequisites

Procedure

  1. Open or create the cockpit.conf file in the /etc/cockpit/ directory in a text editor of your preference, for example:

    # vi cockpit.conf
    Copy to Clipboard Toggle word wrap
  2. Add the following text:

    [basic]
    action = none
    Copy to Clipboard Toggle word wrap
  3. Save the file.
  4. Restart the web console for changes to take effect.

    # systemctl try-restart cockpit
    Copy to Clipboard Toggle word wrap

You can connect to your web console interface from any client operating system and also from mobile phones or tablets.

Prerequisites

  • A device with a supported internet browser, such as:

    • Mozilla Firefox 52 and later
    • Google Chrome 57 and later
    • Microsoft Edge 16 and later
  • The RHEL 10 system you want to access with an installed and accessible web console.

    For instructions, see Installing and enabling the web console.

Procedure

  1. Open your web browser.
  2. Type the remote server’s address in one of the following formats:

    1. With the server’s hostname:

      https://<server.hostname.example.com>:<port-number>
      Copy to Clipboard Toggle word wrap

      For example:

      https://example.com:9090
      Copy to Clipboard Toggle word wrap
    2. With the server’s IP address:

      https://<server.IP_address>:<port-number>
      Copy to Clipboard Toggle word wrap

      For example:

      https://192.0.2.2:9090
      Copy to Clipboard Toggle word wrap
  3. After the login interface opens, log in with your RHEL system credentials.

You can connect to the RHEL web console as the root user to gain full administrative control of a remote host. Be sure to use SSH keys instead of a password for this privileged connection.

On new installations of RHEL 9.2 or later, the RHEL web console disallows root account logins by default for security reasons. You can allow the root login in the /etc/cockpit/disallowed-users file.

Prerequisites

Procedure

  1. Open the disallowed-users file in the /etc/cockpit/ directory in a text editor of your preference, for example:

    # vi /etc/cockpit/disallowed-users
    Copy to Clipboard Toggle word wrap
  2. Edit the file and remove the line for the root user:

    # List of users which are not allowed to login to Cockpit root
     
    Copy to Clipboard Toggle word wrap
  3. Save the changes and quit the editor.

Verification

Log in to the RHEL web console by using a one-time password (OTP) to enhance security. You can use this two-factor authentication method in an IdM domain with enabled OTP.

Important

It is possible to log in using a one-time password only if your system is part of an Identity Management (IdM) domain with enabled OTP configuration.

Prerequisites

  • You have installed the RHEL 10 web console.

    For instructions, see Installing and enabling the web console.

  • An Identity Management server with enabled OTP configuration.
  • A configured hardware or software device generating OTP tokens.

Procedure

  1. Open the RHEL web console in your browser:

    • Locally: https://localhost:9090
    • Remotely with the server hostname: https://example.com:9090
    • Remotely with the server IP address: https://EXAMPLE.SERVER.IP.ADDR:9090

      If you use a self-signed certificate, the browser issues a warning. Check the certificate and accept the security exception to proceed with the login.

      The console loads a certificate from the /etc/cockpit/ws-certs.d directory and uses the last file with a .cert extension in alphabetical order. To avoid having to grant security exceptions, install a certificate signed by a certificate authority (CA).

  2. The Login window opens. In the Login window, enter your system user name and password.
  3. Generate a one-time password on your device.
  4. Enter the one-time password into a new field that displays in the web console interface after you confirm your password.
  5. Click Log in.
  6. Successful login takes you to the Overview page of the web console interface.

1.9. Adding a banner to the login page

You can add a custom banner to the RHEL web console login page. This helps to display important security warnings or legal notices to users before they log in to the system.

Prerequisites

Procedure

  1. Open the /etc/issue.cockpit file in a text editor of your preference:

    # vi /etc/issue.cockpit
    Copy to Clipboard Toggle word wrap
  2. Add the content you want to display as the banner to the file, for example:

    This is an example banner for the RHEL web console login page.
    Copy to Clipboard Toggle word wrap

    You cannot include any macros in the file, but you can use line breaks and ASCII art.

  3. Save the file.
  4. Open the cockpit.conf file in the /etc/cockpit/ directory in a text editor of your preference, for example:

    # vi /etc/cockpit/cockpit.conf
    Copy to Clipboard Toggle word wrap
  5. Add the following text to the file:

    [Session]
    Banner=/etc/issue.cockpit
    Copy to Clipboard Toggle word wrap
  6. Save the file.
  7. Restart the web console for changes to take effect.

    # systemctl try-restart cockpit
    Copy to Clipboard Toggle word wrap

Verification

  • Open the web console login screen again to verify that the banner is now visible:

    Example banner

You can enable the automatic idle lock and set the idle timeout for your system through the web console interface. This ensures your screen automatically locks after a period of inactivity, protecting the system from unauthorized access.

Prerequisites

Procedure

  1. Open the cockpit.conf file in the /etc/cockpit/ directory in a text editor of your preference, for example:

    # vi /etc/cockpit/cockpit.conf
    Copy to Clipboard Toggle word wrap
  2. Add the following text to the file:

    [Session]
    IdleTimeout=<X>
    Copy to Clipboard Toggle word wrap

    Substitute <X> with a number for a time period of your choice in minutes.

  3. Save the file.
  4. Restart the web console for changes to take effect.

    # systemctl try-restart cockpit
    Copy to Clipboard Toggle word wrap

Verification

  • Check if the session logs you out after a set period of time.

1.11. Changing the web console listening port

By default, the RHEL web console communicates through TCP port 9090. You can change the port number by overriding the default socket settings. This adjustment is often necessary to meet specific security or network policies.

Prerequisites

  • You have installed the RHEL 10 web console.

    For instructions, see Installing and enabling the web console.

  • You have root privileges or permissions to enter administrative commands with sudo.
  • The firewalld service is running.

Procedure

  1. Pick an unoccupied port, for example, <4488/tcp>, and instruct SELinux to allow the cockpit service to bind to that port:

    # semanage port -a -t websm_port_t -p tcp <4488>
    Copy to Clipboard Toggle word wrap

    Note that a port can be used only by one service at a time, and thus an attempt to use an already occupied port implies the ValueError: Port already defined error message.

  2. Open the new port and close the former one in the firewall:

    # firewall-cmd --service cockpit --permanent --add-port=<4488>/tcp
    # firewall-cmd --service cockpit --permanent --remove-port=9090/tcp
    Copy to Clipboard Toggle word wrap
  3. Create an override file for the cockpit.socket service:

    # systemctl edit cockpit.socket
    Copy to Clipboard Toggle word wrap
  4. In the following editor screen, which opens an empty override.conf file located in the /etc/systemd/system/cockpit.socket.d/ directory, change the default port for the web console from 9090 to the previously picked number by adding the following lines:

    [Socket]
    ListenStream=
    ListenStream=<4488>
    Copy to Clipboard Toggle word wrap

    Note that the first ListenStream= directive with an empty value is intentional. You can declare multiple ListenStream directives in a single socket unit and the empty value in the drop-in file resets the list and disables the default port 9090 from the original unit.

    Important

    Insert the previous code snippet between the lines starting with # Anything between here and # Lines below this. Otherwise, the system discards your changes.

  5. Save the changes, and exit the editor.
  6. Reload the changed configuration:

    # systemctl daemon-reload
    Copy to Clipboard Toggle word wrap
  7. Check that your configuration is working:

    # systemctl show cockpit.socket -p Listen
    Listen=[::]:4488 (Stream)
    Copy to Clipboard Toggle word wrap
  8. Restart cockpit.socket:

    # systemctl restart cockpit.socket
    Copy to Clipboard Toggle word wrap

Verification

  • Open your web browser, and access the web console on the updated port, for example:

    https://machine1.example.com:4488
    Copy to Clipboard Toggle word wrap
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red Hat
Back to top