Hi there.
I’m using Leap 15.6 Xfce on my miniPC at home.
I’ve followed these guides to install Cockpit:
Running Cockpit — Cockpit Project
Administering SUSE Linux Enterprise Micro using Cockpit
But when I try to open the localhost:9090 or the ip_address:9090 the browser simply says that nothing exists. In the installation process I can’t see any error.
What should I do?
What does sudo systemctl status cockpit.socket
show?
Ah, seems that I can’t start it…
Run the command that I gave and post the output here (as text). We’re interested in the systemd socket unit here.
Refer to the following guide re posting output as pre-formatted text:
Documentation
Using Discourse
🔖 This guide explains how to post code or preformatted text in Discourse using Markdown, BBCode, and HTML formats. 🙋 Required user level: All users Have a line of code you need to share? Maybe you need to share an error log from your site?...
Reading time: 2 mins 🕑
Likes: 14 ❤
~> sudo systemctl status cockpit.socket
● cockpit.socket - Cockpit Web Service Socket
Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; enabled; preset: disabled)
Active: active (listening) since Sat 2025-05-31 10:31:21 CEST; 1h 7min ago
Triggers: ● cockpit.service
Docs: man:cockpit-ws(8)
Listen: [::]:9090 (Stream)
Process: 28940 ExecStartPost=/usr/share/cockpit/motd/update-motd localhost (code=exited, status=0/SUCCESS)
Process: 28949 ExecStartPost=/bin/ln -snf active.motd /run/cockpit/motd (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CPU: 30ms
CGroup: /system.slice/cockpit.socket
mag 31 10:31:21 localhost.localdomain systemd[1]: Starting Cockpit Web Service Socket...
mag 31 10:31:21 localhost.localdomain systemd[1]: Listening on Cockpit Web Service Socket.
This was on my Tumbleweed but Leap may have the same problem. Checking the file will tell you.
I had installed the Cockpit Flatpak to check it out, but I wanted to see how the Tumbleweed Cockpit looked. It’s much better and looks very promising.
I was getting errors:
systemd[1]: cockpit-wsinstance-https-factory.socket: Job cockpit-wsinstance-https-factory.socket/start failed with result 'dependency'.
And…
cockpit.socket: Failed with result 'trigger-limit-hit'
This from: https://bugzilla.suse.com/show_bug.cgi?id=1230546
The actual proposed fix (and also quick) is to change the /et…