Selfhosted

40763 readers

957 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

[–] ChrislyBear 1 points 2 years ago

Yes, definitely. If someone breaches the VPS, I've lost. That's why it's rather locked down using strict firewall rules, pubkey auth, fail2ban, etc.

No matter what you expose to the Internet, you're accepting a risk.

If I had to start over, I'd probably set up some form of cloud infrastructure with maybe Cloudflare for access control and security or whatever. My system started when I didn't have a lot of funds. So everything is kind of cobbled together.

The VPS is/was for hosting a few game servers and now I'm too lazy to migrate away, haha.

At least everything is based on configs that I keep in Git repositories. But I digress (again).