62

Maybe I'm using the wrong terms, but what I'm wondering is if people are running services at home that they've made accessible from the internet. I.e. not open to the public, only so that they can use their own services from anywhere.

I'm paranoid a f when it comes to our home server, and even as a fairly experienced Linux user and programmer I don't trust myself when it comes to computer security. However, it would be very convenient if my wife and I could access our self-hosted services when away from home. Or perhaps even make an album public and share a link with a few friends (e.g. Nextcloud, but I haven't set that up yet).

Currently all our services run in docker containers, with separate user accounts, but I wouldn't trust that to be 100% safe. Is there some kind of idiot proof way to expose one of the services to the internet without risking the integrity of the whole server in case it somehow gets compromised?

How are the rest of you reasoning about security? Renting a VPS for anything exposed? Using some kind of VPN to connect your phones to home network? Would you trust something like Nextcloud over HTTPS to never get hacked?

top 50 comments
sorted by: hot top controversial new old
[-] effingjoe@kbin.social 55 points 1 year ago* (last edited 1 year ago)

I think many of us are using reverse proxies, and opening port 443 (https) and maybe port 80 (http).

load more comments (12 replies)
[-] somedaysoon@lemmy.world 29 points 1 year ago* (last edited 1 year ago)

Unless you need to share/provide services for a public, then you shouldn't be setting up reverse proxies or cloudflare tunnels in my opinion. All you need is WireGuard for you and the handful of users that might be using it.

I have two ports open for:

  1. WireGuard

  2. SSH Tunnel

Both of these services will only accept key based authentication.

WireGuard is the main way that my wife and me access the services away from home. When our phones disconnect from our home's SSID, Tasker automatically connects to the WireGuard tunnel so we never lose access to services.

The SSH tunnel is just a fallback in case I get behind a firewall that might be doing DPI and blocking VPN traffic. The SSH tunnel operates on 443 to hopefully appear to be SSL traffic and allowed through. I've used it a very limited amount of times to get out from strict corporate firewalls.

[-] Semi-Hemi-Demigod@kbin.social 5 points 1 year ago

I was able to reduce that to just SSH by having my Wireguard host on a VPS and connecting out from home. Running SSH on 443 is a neat idea.

load more comments (7 replies)
load more comments (9 replies)
[-] SeeJayEmm@lemmy.procrastinati.org 22 points 1 year ago

I've had 22, 80, & 443 open for literal decades. Key auth only on ssh. 80 & 443 rev proxy to inside web services I want to expose only. Also host game servers as needed.

Keep your stuff up to date and follow best practices for securing it. Use things like crowdstrike. If you can segment your network, go ahead.

Unless you have a target on your head your main concern is going to be scripts looking for vulnerabilities.

[-] spez_@lemmy.world 13 points 1 year ago

I am not exposing any ports online. I do not trust myself

Instead, I am using Tailscale (Wireguard)

[-] notleigh@aussie.zone 2 points 1 year ago

I've got a very similar setup now. Only recently adopted tailscale and was previously port tunnelling over SSH to access anything on the local network. SSH is still open, and am just waiting a bit to see if theres any cases where I need it before closing that out too.

Short story: If you don't need stuff open to the general public, just having Tailscale will probably cover you.

[-] droidpenguin@lemmy.world 12 points 1 year ago

Ya my paranoia only allows me to expose Wireguard to access everything. I sleep better at night knowing that's the only thing exposed. Too many instances of major companies getting hacked who have dedicated security teams to manage that. I am one person, learning to manage my own stuff in my free time.

[-] NotGeorge@lemmy.world 10 points 1 year ago

Port 443 through Traefik and a port for Plex.

load more comments (1 replies)
[-] Smk@lemmy.ca 9 points 1 year ago

I open 443 and 80 on my router and forward it to a reverse proxy.

I have a couple of service that are exposed but most of them make sense only when I'm home so I whitelist private IP address on my reverse proxy.

If you do.your basic security such as updating your servers and services and not having dumb password, you shouldn't be afraid. Think about it, all of the services that you use is exposed on the internet. I did work for big company and they don't do much more than what you would probably do, except maybe having some automated monitoring that flag weird stuff. But hey, aside from bots, I don't think Russian hackers are interested in your stuff. Stay low profile with your exposed things and it's gonna be alright. Make sure you backup.

[-] huojtkeg@lemmy.world 9 points 1 year ago

HTTPS and VPN (Wireguard) ports

[-] MaxMouseOCX@lemmy.world 7 points 1 year ago

Run your own vpn, and only allow access to your services remotely if they are coming through that vpn.

Now you've shifted some of the security over to how secure your vpn server's authentication is.

[-] notannpc@lemmy.world 7 points 1 year ago* (last edited 1 year ago)

I’ve got a few layers of security for my homelab setup that make me feel pretty comfortable against random attacks.

Cloudflare is used to manage my domains and act as an external proxy to obscure my IP address, I’ve only forwarded ports 80 and 443 to Traefik my containerized reverse proxy, Authelia to add 2FA to services that I feel should have extra protection and my homelab nodes are on a separate vlan that is configured to drop all attempts to initiate communication outside of that vlan. I also use the ubiquity intrusion detection and prevention features on my firewall to attempt to stop any know malicious activity.

A majority of these configurations are overkill for a homelab, but were fun to implement. If you use a reverse proxy and keep your software up to date you will likely be fine unless you are specifically targeted by skilled hackers. Any random scans, or shotgun style attacks tend to target unpatched vulnerabilities.

[-] Manifish_Destiny@lemmy.world 6 points 1 year ago

https, wireguard and mumble.

Just set up shodan monitoring, use burpsuite or owasp zap, and check your pcap files for accidental plaintext.

Also ssllabs has a nice website checker.

And get a NGFW

[-] pornhubfan@sh.itjust.works 4 points 1 year ago

If you're gonna post that here, at least flag the post as NGFW.

[-] ZenArtist@kbin.social 4 points 1 year ago

Everything except https and wireguard went above my head. Do you have some sort of guide/writeup that you can point to for integrating all this?

[-] Awwab@kbin.social 3 points 1 year ago

Shodan is a internet scanning website, it can monitor your IP for new ports open and some basic vulnerability stuff.

Burpsuite is a tool to capture network traffic, they are saying they use it to confirm all their services use end to end encryption for communication.

NGFW is next gen firewall and it's just a firewall that's able to do more than your basic in/out rules.

No, all of services are reverse-proxied through a WireGuard tunnel connected to my cloud VPS.

[-] redballooon@lemm.ee 5 points 1 year ago

I did for a while, but it never felt right.

I’m also lazy a f, so I purchased a new router that comes with WireGuard VPN and that works well enough with our iPhones.

[-] spez_@lemmy.world 2 points 1 year ago

I have the GL.iNet travel router, which has a lot of services built in like Tailscale https://www.gl-inet.com/products/gl-mt3000

It's based on OpenWrt

[-] YonatanAvhar@programming.dev 5 points 1 year ago

Run a WireGuard VPN on your server and only forward its port (only UDP is needed) to your server.

[-] Bristlerock@kbin.social 5 points 1 year ago

Exposed is the right term. Other than my Wireguard VPN port, everything I have exposed is HTTPS behind Authelia MFA and SWAG.

I'm tempted to switch Wireguard for Tailscale, as the level of logging with WG has always bothered me. Maybe one day.

[-] zib@kbin.social 4 points 1 year ago

I have https open along with a non-standard port for ssh. Just for fun, I have the standard ssh port open, but redirecting to a Raspberry Pi running a honeypot. It's fun to mess with foreign bots trying to access my network.

load more comments (2 replies)
[-] a_fancy_kiwi@lemmy.world 4 points 1 year ago

I have ports open for Wireguard and Plex. So far, no issues that I’m aware of. Time will tell

[-] Chupachups@kbin.social 3 points 1 year ago

Check out tail scale. It's wire guard made easy. I expose http services to the public Internet, and have all my devices on the same network so I can access local services without exposing them to the public Internet.

[-] pblsnchz@kbin.social 3 points 1 year ago

I used to, but then switched to Cloudflare tunnels and I sleep much better now.

[-] tbblake@lemmy.world 3 points 1 year ago

ssh to a few specific ip ranges, WireGuard to the world on a port I randomly picked

[-] iliketrains@kbin.social 3 points 1 year ago

I'm hosting an email server on a VPS that has fail2ban in it. A lot of ports are open but only wireguard and knockd are listening.

For remote server management, I would use wireguard for regular ssh access, but when I need to configure the wireguard I can just disable/reenable the wireguard-only ssh firewall rule using port knocking, there is also the option of using the serial console on the VPS web ui but it is slower.

Honestly, I'm not sure myself if my public facing services face a DoS attack. Well, there's always an option of using Cloudflare. With that being said though, I think in your case you should just use a free "VPN" like Tailscale or ZeroTier.

load more comments (2 replies)
[-] ulemmyagain@lemmy.world 3 points 1 year ago

I only have my (non default) ssh port exposed. I just use an ssh tunnel to access all my services. I don't know if this is a good idea or not, but it works for me.

[-] carzian@lemmy.ml 5 points 1 year ago

Security through obfuscation is never a good idea. Best practices for exposing ssh (iirc):

  • disable root login (or at least over ssh)
  • disable password login over ssh, use key pairs instead
  • use fail2ban to prevent brute forcing
  • install security updates frequently

All of those are pretty easy to do, and after that you're in a really good place.

I don't see a problem with ssh tunneling to access services, as long as the ssh server is secured correctly

load more comments (3 replies)
[-] SheeEttin@lemmy.world 2 points 1 year ago* (last edited 1 year ago)

None. If anything, I'd probably set up a VPN. But there's nothing so deathly important on my home network that I would need it while away from home. If I wanted to expose services, I'd use a reverse proxy and increase separation between services.

[-] TheInsane42@lemmy.world 2 points 1 year ago

Openvpn to connect to the network, 80 and 443 for static websites, that's it.

Email gets delivered by a VPS via a different port, ssh acces via vps as well. No initial connections from an ip not from the my country as well.

The only port I open is for wireguard. That way I can access all services on my LAN. Wireguard is also very secure and requires keys based authentication so is hard to brute. It also allows me to secure myself if I ever need to join WiFi or an untrusted network

[-] rarkgrames@lemmy.world 2 points 1 year ago

Have a look in to Twingate, that should do exactly what you need.

[-] nekusoul@lemmy.nekusoul.de 2 points 1 year ago

For services that need to be public facing (Mastodon, Lemmy, Gitea...) I'm renting a VPS. Services that are only for personal use run on my home server and are only accessible through Wireguard, with the VPS acting as a "bridge" whenever I'm outside of my home network.

[-] rikudou@lemmings.world 2 points 1 year ago

I have one for OpenVPN and that's it.

load more comments
view more: next ›
this post was submitted on 20 Jul 2023
62 points (95.6% liked)

Selfhosted

39677 readers
246 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 1 year ago
MODERATORS