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!

  • bethfreeman913@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year 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!

  • szakes1@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

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

  • PovilasID@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    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.

    • noaccess@alien.topOPB
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year 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?