▲ 46 ▼ Is webmin safe to have accesible over the web (sh.itjust.works) submitted 1 week ago by DrunkAnRoot@sh.itjust.works to c/selfhosted@lemmy.world 46 comments fedilink hide all child comments As the title says ive started running webmin. And i wanna know if its safe for me to reverse proxy (with 2fa) or should i just use tailscale or ssh to access it.
[–] lka1988@lemmy.dbzer0.com 8 points 1 week ago* (5 children) Yes, and it's very useful. Cockpit, too. I would never expose either of them to the internet. permalink fedilink source parent hideshow 5 child comments replies: [–] moonpiedumplings@programming.dev 7 points 1 week ago* (1 child) I use cockpit, but via the client. They have a flatpak client that gives you cockpit's features, connects over ssh (and reuses your ssh config), and doesn't require anything to be installed on the host/server you are managing (besides ssh ofc). permalink fedilink source parent hideshow 1 child comment replies: [–] lka1988@lemmy.dbzer0.com 5 points 1 week ago* This sounds very handy. permalink fedilink source parent [–] riskable@programming.dev 1 point 1 week ago (2 children) What's it good for? I mean, beyond good ol SSH? permalink fedilink source parent hideshow 2 child comments replies: [–] moonpiedumplings@programming.dev 3 points 1 week ago ssh is probably fine for 99% of things. I use ssh exclusively mostly The features I load cockpit up for is: easier viewing of systemd/journalctl logs. You can click on services and see logs, search them, and so on. Partitioning a disk. Nothing too crazy, but I can format a disk, wipe them, via the GUI Networking configuration. If you are using networkmanager, cockpit will test the changes, attempt to connect, and then revert the changes if the connection fails (in like 15-30 seconds). This is legitimately insanely useful, I can change the ip address or something, connect via cockpit again, and only have the change stick if it's actually good. (See also, netplan try from the netplan configuration framework.) Cockpit also offers a GUI for managing virtual machines (via libvirt) or podman contaniers. So someone else might want that, although I don't really use that. (virtual machines can be managed remotely via virt-manager over ssh by connecting to qemu+ssh://user@remote-host/system, I manage podman via the terminal). permalink fedilink source parent [–] lka1988@lemmy.dbzer0.com 1 point 1 week ago Sometimes I don't want to use command line. Sometimes I just want to use a mouse. permalink fedilink source parent
[–] moonpiedumplings@programming.dev 7 points 1 week ago* (1 child) I use cockpit, but via the client. They have a flatpak client that gives you cockpit's features, connects over ssh (and reuses your ssh config), and doesn't require anything to be installed on the host/server you are managing (besides ssh ofc). permalink fedilink source parent hideshow 1 child comment replies: [–] lka1988@lemmy.dbzer0.com 5 points 1 week ago* This sounds very handy. permalink fedilink source parent
[–] lka1988@lemmy.dbzer0.com 5 points 1 week ago* This sounds very handy. permalink fedilink source parent
[–] riskable@programming.dev 1 point 1 week ago (2 children) What's it good for? I mean, beyond good ol SSH? permalink fedilink source parent hideshow 2 child comments replies: [–] moonpiedumplings@programming.dev 3 points 1 week ago ssh is probably fine for 99% of things. I use ssh exclusively mostly The features I load cockpit up for is: easier viewing of systemd/journalctl logs. You can click on services and see logs, search them, and so on. Partitioning a disk. Nothing too crazy, but I can format a disk, wipe them, via the GUI Networking configuration. If you are using networkmanager, cockpit will test the changes, attempt to connect, and then revert the changes if the connection fails (in like 15-30 seconds). This is legitimately insanely useful, I can change the ip address or something, connect via cockpit again, and only have the change stick if it's actually good. (See also, netplan try from the netplan configuration framework.) Cockpit also offers a GUI for managing virtual machines (via libvirt) or podman contaniers. So someone else might want that, although I don't really use that. (virtual machines can be managed remotely via virt-manager over ssh by connecting to qemu+ssh://user@remote-host/system, I manage podman via the terminal). permalink fedilink source parent [–] lka1988@lemmy.dbzer0.com 1 point 1 week ago Sometimes I don't want to use command line. Sometimes I just want to use a mouse. permalink fedilink source parent
[–] moonpiedumplings@programming.dev 3 points 1 week ago ssh is probably fine for 99% of things. I use ssh exclusively mostly The features I load cockpit up for is: easier viewing of systemd/journalctl logs. You can click on services and see logs, search them, and so on. Partitioning a disk. Nothing too crazy, but I can format a disk, wipe them, via the GUI Networking configuration. If you are using networkmanager, cockpit will test the changes, attempt to connect, and then revert the changes if the connection fails (in like 15-30 seconds). This is legitimately insanely useful, I can change the ip address or something, connect via cockpit again, and only have the change stick if it's actually good. (See also, netplan try from the netplan configuration framework.) Cockpit also offers a GUI for managing virtual machines (via libvirt) or podman contaniers. So someone else might want that, although I don't really use that. (virtual machines can be managed remotely via virt-manager over ssh by connecting to qemu+ssh://user@remote-host/system, I manage podman via the terminal). permalink fedilink source parent
[–] lka1988@lemmy.dbzer0.com 1 point 1 week ago Sometimes I don't want to use command line. Sometimes I just want to use a mouse. permalink fedilink source parent