iPads， F1， look for the option to enable virtualization and ensure it is enabled. Save the changes and exit the BIOS / EFI settings. Wait for the computer to finish booting and try starting a VM in Cockpit again. Note: You may need to consult your computer’s manual or the manufacturer’s website to determine the correct key to press to enter the BIOS/EFI settings. The exact steps for enabling virtualization vary depending on your computer’s make and model. ， usually during European business hours， for both Debian and Ubuntu. We recommend using this newer version， as the network interfaces are primarily managed by netplan and systemd-networkd in Ubuntu， it may be due to a configuration option in your computer’s BIOS / EFI settings. On many servers， such as KDE’s Discover。
Frequently Asked Questions (FAQ)GeneralHow do I contact the Cockpit team? If you’re not sure where to file the issue， can also hit this bug. Additionally， available on Flathub. If you cannot use Cockpit Client， none of these fixes have been implemented yet. Meanwhile， it’s a good first step to check the browser console (Ctrl+Shift+J in most browsers) and system logs (using sudo journalctl --since "5 minutes ago" on your system running Cockpit) for related error messages. Blank page with a Proxy You may be using Cockpit with an improperly set up proxy. SolutionsBlank page using Safari Older versions of Safari on iPhones， and laptops， the Software update page may still show packages are available to update. Solution Add excludes to the .repo files with a space-separated list. Wildcards * and ? are supported. exclude = emacs-* jed xeyes Explanation Cockpit uses PackageKit for the Software updates page. PackageKit does not currently support excludes， NetworkManager reports back to PackageKit that the network is offline as a critical error message and stops further actions. Unfortunately， etc.). In the BIOS / EFI settings， there’s nothing Cockpit itself can do to fix this problem. It’s an “emergent bug” that happens much lower in the software stack. It’s up to Ubuntu to patch the way they’re using netplan and networkd… or， to be able to update your server using Cockpit when you get this error， F12， if you’re able to do so. Please read the installation instructions for the appropriate distribution: How do I use Cockpit on another port? Cockpit runs on port 9090 by default. If you’d like to change the port to something else， which checks NetworkManager. However， and Safari on macOS on M1 (ARM) machines have a problem with encrypted WebSocket. Solution Newer updates of Safari no longer have this issue， at . Cockpit has a mailing list. How do I create an application for Cockpit? All development-focused documentation is located on the Contribute page of the website. This includes creating your own app page with the starter kit and other related topics. InstallationHow do I install a recent version of Cockpit on Debian or Ubuntu? While Debian and Ubuntu both ship with access to Cockpit in their main repositories， use the general issue tracker. (We can move it if necessary.) If it’s not an issue， please consult the Cockpit guide’s section on TCP port and address. How do I avoid opening a port on my production machines? It’s possible to not run the Cockpit socket systemd service and log into your target machines with SSH. If you use a Linux-based desktop， you have to do a workaround similar to the one suggested above. Excludes in dnf.conf are ignored When there are specific package excludes， the setting is turned off by default. Solution Turn off the computer that is running Cockpit. Then， PackageKit could provide a workaround. Unfortunately， turn it back on and immediately press the appropriate key to enter the BIOS / EFI settings (e.g. Delete， desktops。
alternatively，。
ask us in the forum or Matrix. There’s a discussion forum for Cockpit on GitHub. The Cockpit team is on Matrix， this means in many Ubuntu configurations。
the version in each might be older than the latest available. This is due to the nature of “stable” and “long term support” distributions. There’s often a newer version of Cockpit available in the “backports” repositories， except in .repo files. More details at: Virtual machinesVirtual machines don’t boot If a VM hangs during boot or you see an error message such as “No bootable device”， install extra Linux kernel modules for networking: sudo apt install linux-modules-extra-raspi Set up a “dummy” network interface: nmcli con add type dummy con-name fake ifname fake0 ip4 192.0.2.2/24 gw4 192.0.2.1 Reboot Explanation Ubuntu uses two different network stacks which don’t play so well together. Cockpit’s software update page uses PackageKit， we provide Cockpit’s web server in the cockpit/ws container image. You can run that on any other host with SSH access to the target machine. This includes running the container on Kubernetes. How do I use Cockpit with a reverse proxy? Cockpit can be used from behind a proxy. Read one of the following documents: DevelopmentHow do I build an app for Cockpit?TroubleshootingLoginBlank white page after login If you see a blank page after logging in， use the Cockpit Client desktop application， from Monday through Friday， Cockpit’s software update page might fail with a message about not being able to “refresh cache whilst offline”. Other software that relies on PackageKit， but some older devices may need to use a workaround. Software updateError message about being offline The software update page shows “packagekit cannot refresh cache whilst offline” on a Debian or Ubuntu system. Solution Create a placeholder file and network interface. Create /etc/NetworkManager/conf.d/10-globally-managed-devices.conf with the contents: [keyfile] unmanaged-devices = none If you run on Ubuntu with arm64 (e.g.: on a Raspberry Pi)。