this post was submitted on 23 Jun 2024
30 points (96.9% liked)

Selfhosted

40165 readers
1336 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Dockge allows you to start/stop containers and edit your compose files from a handy ui.

Pros: if something goes wrong while you're away, it would give you a tool to restart a service or make some changes if necessary.

Cons: exposing that much control to the outside world (even behind a log in) can potentially be catastrophic for your stack if someone gets in.

top 17 comments
sorted by: hot top controversial new old
[–] OneCardboardBox@lemmy.sdf.org 24 points 4 months ago (1 children)

I wouldn't trust anything like that to the open internet. It would be better to access the system over a VPN when you're outside the network.

[–] toastboy79@kbin.earth 7 points 4 months ago (1 children)

I could see that, but I would also have to ask 'what exactly do we gain by having access to these tools when we aren't home?'

I used to try to do all of that but I started to realize, I spend too much time dealing with broken shit. Coming to the mindset of if I'm not home and it doesn't work then oh well has been one hell of a stress relief for me

[–] tburkhol@lemmy.world 2 points 4 months ago (1 children)

Yeah, I think it really depends on use case. Like, I'm trying to imagine what aspect of my home lab could go so wrong, while I'm out of the house, that it would need fixed right away, and there's nothing. I only leave my house for work or maybe a week of vacation, though, and I can imagine someone who's occasionally away from home/house for 6-month deployments, or has a vacation home they only visit four weekends a year, might want more extensive remote maintenance. I'd still want to do that via ssh or vpn, but that's me.

[–] anytimesoon@feddit.uk 2 points 4 months ago (2 children)

This is pretty much my situation. "Away from home" for me isn't just a trip to the shops, it means being away for weeks at a time. I need to be able to fix things remotely if needed.

I've seen people recommend SSH, which seems worse because that would give potential hackers access to the whole system.

VPN is a very good suggestion, and what I've implemented now. Thank you to everyone who contributed

[–] tburkhol@lemmy.world 1 points 4 months ago

I do ssh because I'm more comfortable with it: it's ubiquitous and as close to bulletproof as any security. Put it on a nonstandard port, restrict authentication to public keys, and I have no qualms.

One thing to consider, as well, is that SSH is extremely well reviewed, audited, and battle tested.

If you get "hacked" via SSH, it's almost certainly because you had a bad password (don't use passwords!), and not due to an exploitable bug in SSH.

Some random Docker management tool? Eh, I wouldn't wager any money on you getting hacked, either through missing a configuration step, or a permission being too lose, or a flat out stupid decision made somewhere in the code that's exploitable.

SSH + lazydocker is a reasonable choice if you want to go the SSH route and is my 'oh shit, portainer-via-vpn is fucked' backup.

[–] HostedSnob@sh.itjust.works 23 points 4 months ago (1 children)
[–] r0ertel@lemmy.world 5 points 4 months ago

I'm using tailscale (which I hear is just a wrapper for wireguard) and love it.

[–] scott@lem.free.as 14 points 4 months ago

It would mean you're entrusting the entire security of your network to Dockge's authentication system.

... and for that reason, I'm out.

[–] Auli@lemmy.ca 13 points 4 months ago* (last edited 4 months ago)

Should be fine I have never used it in a man. I think it would be difficult to use it in a man with all the blood and other stuff.

[–] jhoward@lemmy.sdf.org 9 points 4 months ago (2 children)

I use portainer behind tail scale. Easy management anywhere and no publicly available access.

[–] Willdrick@lemmy.world 5 points 4 months ago

Indeed, tailscale/wireguard/zerotier are excellent options to keep only the bare minimum (or even nothing!) exposed to the world.

[–] mhzawadi@lemmy.horwood.cloud 3 points 4 months ago

I have my portainer behind an oath proxy, using keycloak as the Auth provider

[–] NegativeLookBehind@lemmy.world 7 points 4 months ago

I’ll take “big red flags” for $1000

[–] Omgboom@lemmy.zip 6 points 4 months ago

I would much prefer to just ssh

[–] possiblylinux127@lemmy.zip 1 points 4 months ago (1 children)

Don't

Also I find it easy to just write a docker compose.

[–] anytimesoon@feddit.uk 1 points 4 months ago

I have no issue writing a compose file. Dockge offers a bit more than that with logs and buttons for common commands which makes it easier and quicker to manage than through SSH.

To each their own 🙂