119
Selfhosting Sunday! What's up? (lemmy.nocturnal.garden)
submitted 9 months ago by to c/selfhosted@lemmy.world
113 comments fedilink hide all child comments
 

What's happening on your servers? Any interesting news things you tried?

I didn't do anyone other than updating Mastodon (native deployment) lately due to a lack of time. Reading so much about Immich caused me to consider trying it in parallel to Nextcloud but I'm not sure if I want to have everything twice.

Not quite homelab, but I'm about to install Linux Mint on my mom's laptop and that had me thinking about creating an off-site backup in her place again since she has a fiber connection. I'm still not sure about the potential design though, but currently my only backup is in the same rack as the live stuff.

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 9 months ago (1 child)

Rootless podman cannot bind ports <1024, only root can by default (on pretty much any distro I guess). Have you done something like sysctl net.ipv4.ip_unprivileged_port_start=80 to allow non-root processes to bind to port numbers >=80?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 9 months ago

    I've read about that and I already have that in my notes as well.

    It doesn't really affect my needs because my ISP blocks incoming on those ports anyways. Also I'm choosing not to use a tunnel at the moment so I'll be using a higher port anyways.

    The last time I asked about it, a few people seemed to agree it was something to do with the firewall settings. That seems most likely since I was able to connect when I disabled my firewall. I'm not a fan of working with iptables. The language for that type of networking is gibberish to me.

    I had also tried going from docker compose to rootful podman compose and ran into the same issue. Although I'm trying to work away from podman compose in the future, just taking it in steps.

  • permalink
  • fedilink
  • source
  • parent