@Android_Gynous well your still going to have to run the cockpit service/socket to connect, so it’s six of one, half a dozen of the other… still another port exposed… plus the additional plugins etc. If it’s only the local machine then the cockpit way would be fine, I manage multiple machines and arches (x86_64/ARM/RISCV64) here, so for me the flatpak user install is perfect.
@Android_Gynous … so far not for me … keep getting “gnu_tls” and “connection reset” errors but I’ll start a new thread for that if I can’t figure it out … most people seem fine
@Android_Gynous … so far not for me … keep getting “gnu_tls” and “connection reset” errors but I’ll start a new thread for that if I can’t figure it out … most people seem fine
started my thread and @hui is on it … just gotta wait for an update now
https://forums.opensuse.org/t/cockpit-socket-errors/
The OpenSuse bugzilla site never showed up in any of my searches so I made a bookmark for it … gonna start an OpenSuse folder I think
is there any news about the estimative date of TW dropping YaST? i
So we will have to configure the ports either way and cockpit will have sshd to be running?
Only when you want to manage other machines from your box. If Cockpit only runs on the machine which you want to manage, no sshd is running or required.