Selfhosted

40763 readers

968 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

Is it safe to open ports 80 and 443 in my home network? (sh.itjust.works)

submitted 2 years ago by [email protected] to c/selfhosted

40 comments fedilink hide all child comments

Hi all, I'm running a small website off of a raspberry pi in my house. I have opened ports 80 and 443 and connected my IP to a domain. I'm pretty confident in my security for my raspberry pi (no password ssh, fail2ban, nginx. Shoutout networkchuck.). However, I am wondering if by exposing my ports to the raspberry pi, I am also exposing those same ports to other devices in my home network, for example, my PC. I'm just a bit unsure if port forwarding to an internal IP would also expose other internal IP's or if it only goes to the pi. If you are able to answer or have any other comments about my setup, I would appreciate your comment. Thanks!

you are viewing a single comment's thread
view the rest of the comments

[–] surewhynotlem 12 points 2 years ago (1 children)

You could put the pi on its own subnet. That way if it's hacked, the rest of the network is protected. Just make sure your router admin interface doesn't answer on that subnet.

[–] TitanLaGrange 9 points 2 years ago (1 children)

You could put the pi on its own subnet.

This option is sometimes referred to as a 'DMZ' and may be supported by the router. Also look for VLAN options.

[–] Manbat 4 points 2 years ago (1 children)

DMZ in essence means "forward ALL ports" to X. You should only DMZ a host that you know is very secure as its attack surface is significantly increased. If you need just one or two services open, best to not use DMZ

[–] [email protected] 2 points 2 years ago* (last edited 2 years ago)

This is true for consumer routers/firewalls