this post was submitted on 25 Nov 2023
1 points (100.0% liked)

Self-Hosted Main

511 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
Cloud Linux VPS - Extending Docker from the Cloud home lab (Via VPN) (alien.top)
submitted 11 months ago by [email protected] to c/[email protected]
4 comments fedilink hide all child comments
 

I have had a NAS running docker with various containers, but I just purchased a very cheep ubuntu running docker (managed via portainer) VPS over the cloud. My NAS CPU/RAM is fairly limited and I would like to offload some resources to this cloud instance. Is there any good documentation on establishing a VPN for local traffic to my network? I have Wireguard running on my Unifi UDM and I am thinking this is the first step for linking the virutal cloud server. Thanks!

top 4 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 11 months ago

Read about site-to-site VPN configuration, it's what you're looking for.

[–] [email protected] 1 points 11 months ago

you should check out the WireGuard documentation, it's pretty straightforward to set up with your Unifi UDM. Once you have your VPN connection established, you can easily route your local traffic to your new cloud VPS. Good luck!

[–] [email protected] 1 points 11 months ago (1 children)

I have a setup where Wireguard docker container that is connected to my local network and if I use any other container to get local access I use `network_mode: service:wireguard-container` for that remote container have the same access as my VPN container.

This has pros and cons. Major pro that the host machine has no access to my network, so it works as regular server. Cons are that if I want to expose say a web panel for one of my local services I have to apply proxy settings to the VPN container and if you use a multiple copies of the same container that does not allow to change default port... you get collisions.

[–] [email protected] 1 points 11 months ago

I think this is pretty much what I am looking for. I dont see a big need to have the host access the local network as everything I am using is in docker containers. I tried getting wireguard running on the host and a container and kept getting errors like the one below when trying to start wireguard

​

RTNETLINK answers: Operation not supported

Unable to access interface: Protocol not supported

AI also ran sudo modprobe wireguard which gave this modprobe: FATAL: Module wireguard not found in directory /lib/modules/4.15.0-20-generic

Any details on how you got yours going?