Fedora 39 : How to start using cockpit tool in firefox.

Use lie any default installation like any Fedora Linux Distro package for cockpit tool with DNF or DNF5 tool.

$ sudo su
# dnf5 install cockpit
# systemctl enable --now cockpit.socket
# firewall-cmd --add-service=cockpit
# firewall-cmd --add-service=cockpit --permanent
# exit

The next step is to test if this runs well.

Get your ip address with netstat:

$ netstat nr

Because I used an virtual box for testing Fedora I get this ip 10.0.2.0

Use with firefox in the terminal:

$ firefox http://10.0.2.0:9090

The result will be the online cockpit tool.

Fedora 39 : Solve copy-paste in VirtualBox.

I'm using the Fedora 39 Linux distribution on an HP laptop and I also have it installed on a VirtualBox on my work computer. Today I will show you a way to solve copy paste between content on your computer and Fedora 39 on VirtualBox.

This requires Virtual Box to be set to bridge network as in the attached image.

The next step is to have the Cockpit tool installed, see instructions here.

Open the web address created by the Cockpit tool in your computer browser and go to the Terminal section. This way you will be able to transfer text content using your computer's browser and not the VirtualBox settings.

See the next image:

Fedora 27 : About Cockpit linux tool.

About the Cockpit the official website tell us:
Cockpit makes Linux discoverable, allowing sysadmins to easily perform tasks such as starting containers, storage administration, network configuration, inspecting logs and so on.
If you use Fedora 27 the this tool can be used very easy.
If your Fedora Spin don't come with this tool then you can install it with this command:

#dnf -y install cockpit

First you need to follow this steps:
- starting Cockpit requires only a single command:

#systemctl start cockpit

- we’ll configure it to start on boot with:

#systemctl enable cockpit.socket

- you can check the status of Cockpit with:

#systemctl status cockpit

- the Cockpit tool runs on port 9090, so you’ll need to allow it through the firewall with this command:

#firewall-cmd --add-service=cockpit

- or simply add with the open port with:

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

- you now should reload the firewall for the rule to take effect:

#firewall-cmd --reload

Testing is the next step by log into Cockpit from your localhost (your server’s IP address) with your server’s root credentials.
Once you logged in you’ll see the Dashboard web page containing information about the server itself and graphs showing CPU and Memory Usage as well as Disk I/O and Network Traffic.
Let's see the Dashboard:

• System come with infos about your system;
• Logs displays the server’s system and service logs. That 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. Also, 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, logs and network interface information. You also can configure the network interface from this page. 
• 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. 
• Accounts lets you to : add and manage users, set up and change passwords, and add and manage public SSH keys for each user. 
• 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.
• Terminal let you a fully functional terminal, with tab completion, allowing you to perform any task you could perform through its web interface.This come with the same privileges your login credentials would allow via SSH.

You can take a look at documentation for Cockpit to learn more about this tool.