this post was submitted on 03 Feb 2025
17 points (94.7% liked)

Selfhosted

41667 readers
925 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 2 years ago
MODERATORS
 

https://github.com/wg-easy/wg-easy

Plus

https://github.com/qdm12/gluetun

The idea being; I can use a normal wireguard VPN from anywhere in the world to connect back to my homelab, all while being able to access stuff on my network, but also have my public IP address set by the gluetun container?

Anyone done this? Or have a docker conpose?

you are viewing a single comment's thread
view the rest of the comments
[–] JoeKrogan 1 points 10 hours ago

I have something similar . I have WG on the host to access my services and gluetun in a container using openvpn for specific services.

In my case I have the host wg pass through connections to the outside via iptables rules but I'm not forwarding the connection to gluetun. I have the ip of my server as my ip.

In your case as you want a commercial vpn ip as your exit ip you would need to use iptables to pass traffic between the 2 networks .