How To Use Cockpit in Fedora 23

Reading Time: 3 minutes
Note:
Please note that this article is considered legacy documentation because Fedora 23 has reached its end-of-life support.

Several free options exist for remotely managing Linux servers through a graphical user interface. While some seek to replicate the full range of features available in paid control panels such as Plesk or cPanel, others are focused on helping you perform common tasks and manage essential services. The GUI for remote server administration that ships with Fedora 23, Cockpit, falls into the latter category.

Pre-Flight Check

  • This article is intended as an introduction to the Cockpit GUI on Fedora 23 Server edition.
  • We’ll be logging in as root to a Liquid Web Self-Managed Fedora 23 server.

Step #1: Enable Cockpit

Cockpit is included as part of the default installation of Fedora 23. It is not, however, automatically enabled. Fortunately, it’s easy to get it up and running:

  1. Starting Cockpit requires only a single command:

    systemctl start cockpit

    Note: The source image for some Fedora 23 servers, depending on when the server was created, may not have included Cockpit. If the above command returns an error, you can install it with: dnf -y install cockpit
  2. Now, we’ll configure it to start on boot with:

    systemctl enable cockpit.socket

    Running that command should produce output similar to the following:

    [root@host ~]# systemctl enable cockpit.socket
    Created symlink from /etc/systemd/system/sockets.target.wants/cockpit.socket to /usr/lib/systemd/system/cockpit.socket.

  3. You can check the status of Cockpit with:

    systemctl status cockpit

    Which should display status information similar to:

    [root@host ~]# systemctl status cockpit
    ● cockpit.service - Cockpit Web Service
    Loaded: loaded (/usr/lib/systemd/system/cockpit.service; static; vendor preset: disabled)
    Active: active (running) since Wed 2016-02-03 14:47:36 EST; 7s ago
    Docs: man:cockpit-ws(8)
    Process: 14713 ExecStartPre=/usr/sbin/remotectl certificate --ensure --user=root --group=cockpit-ws --selinux-type=etc_t (code=exited, status=0/SUCCESS)
    Main PID: 14717 (cockpit-ws)
    CGroup: /system.slice/cockpit.service
    └─14717 /usr/libexec/cockpit-ws
    Feb 03 14:47:36 host.example.com systemd[1]: Starting Cockpit Web Service...
    Feb 03 14:47:36 host.example.com systemd[1]: Started Cockpit Web Service.
    Feb 03 14:47:36 host.example.com cockpit-ws[14717]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert

  4. Now that the service is running, we’ll need to make sure it’s accessible. Cockpit runs on port 9090, so you’ll need to allow it through the firewall. You can either add the service itself using:

    firewall-cmd --add-service=cockpit

    or simply open the port with:

    firewall-cmd --permanent --add-port=9090/tcp

  5. You now should reload the firewall for the rule to take effect:

    firewall-cmd --reload

Step #2: Log into Cockpit

  1. Point your browser to the Cockpit Dashboard at your server’s IP address and the Cockpit port, 9090:

    https://123.123.123.123:9090

    to arrive at Cockpit’s login screen.

    CockpitLoginScreen

  2. Use your server’s root credentials to log in.
  3. The server’s self-signed SSL certificate likely will trigger a browser warning, and you’ll need to accept the security certificate to proceed.
    Note: A self-signed certificate uses the same level of encryption as a verified certificate, except that it is you who are verifying your server’s identity, rather than a third party.

Step #3: Explore Cockpit

Once logged in you’ll see the Dashboard:

CockpitMainDashboard

The Dashboard loads the System tab by default, containing information about the server itself and graphs showing CPU and Memory Usage as well as Disk I/O and Network Traffic. Each chart label links to a more detailed view.

Cockpit’s main menu items allow you to perform a multitude of server management functions:

  • Services lists all services, and clicking on any entry takes you to a detail page showing the service log and allowing you to start/stop, enable/disable, reload/isolate, or mask/unmask each service.
  • Containers allows you to manage your Docker containers. You can search for new containers, add or remove containers, start and stop them, and set runtime variables on this page.
  • Logs displays the server’s system and service logs, and allows you to click on any entry for more detailed information, such as the process ID.
  • Storage gives you a graphical look at disk reads and writes, and also allows you to view relevant logs. In addition, you can set up and manage RAID devices and volume groups, and format, partition, and mount/unmount drives.
  • Networking contains an overview of inbound and outbound traffic, along with relevant logs and network interface information. You also can configure the network interface from this page.
  • The Tools menu expands to offer two additional user and server management tools:
    • Accounts lets you add and manage users, set up and change passwords, and add and manage public SSH keys for each user.
    • Terminal contains a fully functional terminal, with tab completion, allowing you to perform any task you could perform through its web interface with the same privileges your login credentials would allow via SSH.

Step #4: Learn More about Cockpit

Check out Cockpit’s official documentation to explore its features and learn how you can integrate Cockpit into your server management workflow.
 

How To Install NVM (Node Version Manager) on Fedora 23

Reading Time: 1 minute

Node Version Manager allows you to quickly install and manage node.js versions. It’s a bash script that has the capability to manage multiple active versions of node.js. It can be used to install node.js versions, execute commands with a specific node.js version, set the PATH variable to use a specific node.js version, and more. To learn more, visit the project’s Github page. Continue reading “How To Install NVM (Node Version Manager) on Fedora 23”

How To Install Node.js on Fedora 23

Reading Time: 2 minutes

Node.js is a cross-platform runtime environment built on JavaScript. Applications also are written in JavaScript. Node.js lends itself to rapidly deploying, real-time web applications, and is considered extremely scalable due to its event-driven architecture. Node Version Manager allows admins to easily install and manage multiple node.js versions. Continue reading “How To Install Node.js on Fedora 23”

How To Install Varnish on Fedora 23

Reading Time: 1 minute
Note:
Please note that this article is considered legacy documentation because Fedora 23 has reached its end-of-life support.

Varnish is a web accelerator, specifically a caching HTTP reverse proxy, designed to improve performance for busy, dynamic websites. By redirecting traffic to static pages whenever possible, Varnish reduces the number of dynamic page calls, thus reducing load.

Pre-Flight Check

  • These instructions are intended specifically for installing varnish on Fedora 23. If you’re using a different operating system, check out our guides to installing varnish on Fedora 21 or CentOS 7.
  • We’ll be working as root on a Liquid Web Self Managed Fedora 23 server. Apache and PHP already are installed, configured, and running.

Step #1: Install Varnish

A single command installs Varnish:

dnf -y install varnish

Step #2: Start Varnish

To configure varnish to start at boot, run the following command:

systemctl enable varnish

That should return output similar to:

[root@host ~]# systemctl enable varnish
Created symlink from /etc/systemd/system/multi-user.target.wants/varnish.service to /usr/lib/systemd/system/varnish.service.

To start Varnish:

systemctl start varnish

To check the status of Varnish:

systemctl status varnish

Varnish is configured to listen on port 6081 by default. It expects your web server to be listening on port 8080.

Step #3: Configuration File Locations

A basic and default configuration file can be found at:

/etc/varnish/default.vcl

An example configuration can be found in:

/usr/share/doc/varnish/example.vcl
 

How To Install XCache on Fedora 23

Reading Time: 1 minute
Note:
Please note that this article is considered legacy documentation because Fedora 23 has reached its end-of-life support.

Pre-Flight Check

Continue reading “How To Install XCache on Fedora 23”

How To Install Memcached on Fedora 23

Reading Time: 3 minutes

Memcached is a high-performance distributed, in-memory caching system. It primarily is used to speed up sites that make heavy use of databases. It also can, however, be used to store any kind of object.

Most popular Content Management Systems have a plugin or module designed to take advantage of memcached, and many programming languages such as PHP, Perl, Python, and Ruby also have a memcached library.

Memcached runs in memory and is quite fast, as it does not need to write data to disk.

Continue reading “How To Install Memcached on Fedora 23”

How To Install Squid on Fedora 23

Reading Time: 2 minutes
Note:
Please note that this article is considered legacy documentation because Fedora 23 has reached its end-of-life support.

Squid is a caching and forwarding web proxy. It is most often used in conjunction with a traditional LAMP stack (Linux, Apache, MySQL, PHP), and can be used to filter traffic on HTTP, FTP, and HTTPS, and increase the speed (thus lower the response time) for a web server via caching.

Continue reading “How To Install Squid on Fedora 23”

How To Install and Connect to PostgreSQL on Fedora 23

Reading Time: 2 minutes

PostgreSQL is a free, open-source object-relational database management system (object-RDBMS), similar to MySQL, and is standards-compliant and extensible. It often is used as a back-end for web and mobile applications. PostgreSQL, or ‘Postgres’ as it is nicknamed, adopts the ANSI/ISO SQL standards together, with the revisions.

Continue reading “How To Install and Connect to PostgreSQL on Fedora 23”

How To Install Pip on Fedora 23

Reading Time: 1 minute
Note:
Please note that this article is considered legacy documentation because this OS has reached its end-of-life support.

Pip is a tool for installing and managing packages for Python. The popular Python programming language is considered one of the easiest to learn because of its emphasis on code readability.

Continue reading “How To Install Pip on Fedora 23”

How To Install mlocate (locate and updatedb) on Fedora 23

Reading Time: 1 minute

The locate command is an invaluable tool when you’re trying to track down a particular file but know only the file name. Locate reads one or more databases prepared by the related updatedb and writes file names matching at least one of the patterns to standard output, one per line.

Continue reading “How To Install mlocate (locate and updatedb) on Fedora 23”