80
Ways to Expose Services Publicly (lemmy.dbzer0.com)
submitted 1 week ago by to c/selfhosted@lemmy.world
86 comments fedilink hide all child comments
 

I want to expose my services publicly on my own domain name, how would you guys do that?

I have seen people using Cloudflare, but I don't want to use Cloudflare out of principle. I have also seen stuff on caddy and frp that I've done some rough researching.

What do you guys do?

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

Recently set up caddy myself, very straightforward setup. You essentially just edit one config file and point your domain host to the right place and are good to go. Took me by surprise actually.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 1 week ago (2 children)

    Yeah but my main concern is security. If I publicly have services like jellyfin or something then I would think I would have constant exploits and bot attacks

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 1 week ago

    You will.

    Anything you expose should be designed for it (e.g. not jellyfin). You should have a WAF configured for the type of service you're hosting. You can't just drop one and have it magically protect you, they take configuration. Same with fail2ban.

    And you should have these services in a DMZ, so that a compromise in one doesn't provide an entry point to other resources on your network.

  • permalink
  • fedilink
  • source
  • parent