this post was submitted on 20 Oct 2023
1 points (100.0% liked)

Self-Hosted Main

515 readers
1 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.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
[email protected]
1
VPN for specific containers only (alien.top)
submitted 1 year ago by [email protected] to c/[email protected]
4 comments fedilink hide all child comments
 

Hi there, I hope somebody can help me out with this, because I've done some research already but either I have come across dead links or I haven't understood what I was reading.

I have a bunch of docker containers running behind Nginx Proxy Manager and I have pi-hole with unbound set up as dns server for ad-blocking and also to resolve "mydomain.tld" to my local server ip (I have a hard time remembering ips/ports).

Some containers are publicly available for convenience, the rest aren't but I'd still like to have some or all of them behind a VPN so I can access them from outside my local network and it would be great if I could also set the pi-hole as the dns server for the VPN.

Long story short, I don't want to route all of the traffic behind the VPN, just specific containers.

All of them are running on ubuntu server with no VMs, it's a small homelab, nothing fancy.

How can I do this?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago

I did just this for a while.

Use a docker image that has a VPN built into it like `binhex-privoxyvpn`

Once that container is up and running, tell your new container to use that as it's network.

docker run --network=container:privoxyvpn blah, blah.