this post was submitted on 03 Aug 2025
113 points (88.4% liked)

Selfhosted

50178 readers
359 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 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
113
How to Setup a Secure Ubuntu Home Server: A Complete Guide (www.davidma.co)
submitted 2 days ago by udc@lemmy.world to c/selfhosted@lemmy.world
24 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] truthfultemporarily@feddit.org 44 points 2 days ago (3 children)

This is mostly nonsense.

  • Why block outgoing? Its just going to cause issues for most people. If you're going to do that, do it centrally (hw firewall)
  • Why allow http and NTP incoming, when there is no http / NTP server running.
  • If there is http server running no mention of https://ssl-config.mozilla.org/ and modsecurity
  • If you're using ufw anyway why not go with applications instead of ports?
  • In a modern distro, the defaults are usually sane (maybe except TCP), most of the stuff in the SSH config is already default.
  • Why change the SSH port of a home server, which most likely is not reachable from the outside anyway?
  • Actually potentially impactful stuff like disabling services you don't need, such as cups, is not mentioned
  • unattended-upgrades not mentioned
  • SELinux / AppArmor not mentioned
  • LKRG not mentioned https://lkrg.org/
  • Fail2ban not mentioned

Don't just copy random config from the internet, as annoying as it is, read the docs.

[–] Mordikan@kbin.earth 5 points 2 days ago

But you need that legal banner in case your spouse acts up and you need to throw their ass in prison.

[–] uranibaba@lemmy.world 3 points 2 days ago (1 children)

Why change the SSH port of a home server, which most likely is not reachable from the outside anyway?

And if it is, why change it on the server and not in the fw?

[–] truthfultemporarily@feddit.org 0 points 2 days ago (1 children)

If you change it, definitely change it on the server so it shows up in netstat and is consistent.

[–] uranibaba@lemmy.world 1 points 1 day ago (1 children)

I mean keep using port 22 on the server and redirect whatever port you want in your firewall (your router unless you have a dedicted fw) to port 22. Don't change the ssh port on the server at all.

[–] truthfultemporarily@feddit.org 1 points 1 day ago

I understand this, but this is inconsistent behavior. You now use 22 inside your network and something else outside. Whenever you create inconsistent behavior, everyone using it has to have an awareness of all these inconsistent behaviors.

Also, it is hard to troubleshoot because the tool most admins would want to use (netstat) will not give you useful information to understand the situation.

[–] RubberElectrons@lemmy.world 1 points 2 days ago

Til about lkrg.