this post was submitted on 31 Dec 2025
51 points (100.0% liked)

Selfhosted

54185 readers
903 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 
  • A different device from your home server?
  • On the same home server as the services but directly on the host?
  • On the same home server as the services but inside some VM or container?

Do you configure it manually or do you use some helper/interface like WGEasy?

I have been personally using wgeasy but recently started locking down and hardening my containers and this node app running as root is kinda...

you are viewing a single comment's thread
view the rest of the comments
[–] piyuv@lemmy.world 7 points 4 days ago (3 children)
[–] Auli@lemmy.ca 1 points 3 days ago

It's my outside device it allows things into my network might as well terminate the VPN there. I mean if my router is down I'm not getting to the VPN endpoint inside my network.

[–] dogs0n@sh.itjust.works 2 points 3 days ago* (last edited 3 days ago)

Maybe easier to setup because routers that support vpns come with nice-ish web uis.

That said, if you have a server (pc, pi, etc), setting up wireguard with wg-easy is mostly painless (comes with a nice web ui), so there is no reason to replace your router in this case!

Instead of replacing a router, I'd prefer buying a pi anyways.

Unless you want to route all outbound traffic through a vpn with zero config on devices, I can't see why you'd replace a router.

Final note: most people prefer hosting a vpn on a server, even if their router supports it as far as I'm aware at least (edit: this might be erong judging from the rest of the comments saying they use their router).

[–] sakphul@discuss.tchncs.de 1 points 3 days ago

For me a similar tasks should be handled by the same device. Network routing and VPN are similar things for me, therefor they are handled by the router.

It also handles VPN connections to other remote locations. So again same things in the same device.

Another benefit (which you can also have on the Server with some additional effort): the router boots up without interaction after a power outage. The Server does not. Them I can connect and unlock (LUKS password) the servers.