OMV remote access

Comments

• neidu3@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

  I have no experience with OMV specifically, but generally making things accessible from outside your house means exposing it ti the internet.

  However, what you can do is to only expose an openvpn port, so that to gain access as if you were at home you could connect via o0envpn first.

  source

  • TentinQuarantino@feddit.org ⁨3⁩ ⁨weeks⁩ ago

    Does it mean I have to configure a VPN profile on all of the devices I need remote access from and I’m only able to access my NAS while this VPN profile is active?

    source

    • neidu3@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

      No, just one. You set up one device/server as a VPN gateway (often called VPN concentrator), and you will have access to anything the concentrator has access to on your home network.

      source

      • -> View More Comments
  • sugar_in_your_tea@sh.itjust.works ⁨2⁩ ⁨weeks⁩ ago

    I recommend WireGuard instead of OpenVPN. WireGuard is baked into the kernel so it should work better.

    source
• sem@lemmy.blahaj.zone ⁨2⁩ ⁨weeks⁩ ago

  You are lucky in a way that OMV has a fantastic documentation suite. it is not too long, and I recommend reading it cover to cover, as well as the omv-plugins and omv-extras documentation, skipping over anything that’s not interesting, but seeing that it’s there for future reference.

  OMV is interesting to me because it gives you a gui that lets you do many difficult or advanced things fairly quickly, but it is not always clear what all the options do, and things don’t always work as expected. My advice is start slow, stick to the garden path (don’t try anything custom or unusual), and frequently browse the forums.

  source

  • TentinQuarantino@feddit.org ⁨2⁩ ⁨weeks⁩ ago

    It is exactly what I’m doing. First I just created an SMB folder on the home network. Next paperless-ngx. After that Immich. But only on the local network. Now I want to go a step further. And I always get back to the documentation if I need something new. Regarding the garden path: exactly the reason why I explicitly asked for OMV. Thank you for your contribution. Much appreciated!

    source
• lka1988@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

  First and foremost: Do not expose your host system or the OMV admin interface to the internet. Ever. Only expose services that have been properly isolated from the rest of the network and host system. Everything else you can access via VPN, or locally.

  Secondly: OpenMediaVault beginner’s guide by DB Tech. Him, Craft Computing, Hardware Haven, and a few others whose names currently escape me, are all solid sources for hosting things at home.

  After OMV, I would start with learning Docker and other containerization methods, and VMs.

  source

  • TentinQuarantino@feddit.org ⁨2⁩ ⁨weeks⁩ ago

    You’re totally right and it wasn’t my plan. I actually deployed some services in a mix of docker compose and portainer. With separate UID and GID for each of them. And the idea is to really expose the 1 or 2 services for remote control.

    Oh think I saw this guy’s tutorial regarding docker an OMV. I will watch the whole series. Thank you for your help

    source

    • lka1988@sh.itjust.works ⁨2⁩ ⁨weeks⁩ ago

      Sounds like you’re pretty familiar already! I use OMV for my NAS and have several NFS shares for various services. It’s a solid solution IMO.

      source

      • -> View More Comments
• makingStuffForFun@lemmy.ml ⁨3⁩ ⁨weeks⁩ ago

  I have used OMV for years. Great system.

  I remote in using zeroTier.

  It’s installed on the OMV server, and I have it on all my devices.

  That puts all my devices on a virtual “local network” so I can explore my shared folders, log into the OMV admin panel, etc, anywhere in the world.

  Has been working beautifully for me, for years.

  I hope that helps.

  source

  • TentinQuarantino@feddit.org ⁨2⁩ ⁨weeks⁩ ago

    Oh that’s interesting! I never heard about it tbh. But if it is preinstalled it should lay on the hand to (at least) try it out. Thanks a lot for your comment!

    source
• Xanza@lemm.ee ⁨3⁩ ⁨weeks⁩ ago

  But I’m a bit lost which approach and tools to use without exposing and making my NAS vulnerable on the internet.

  You’re looking for a reverse proxy;

  *.domian.dev {
          encode zstd gzip
          @jelly host jelly.domian.dev
          handle @jelly {
                  reverse_proxy {selfhost_ip}:{port}
          }
          @ping host ping.domian.dev
          handle @ping {
                  respond "pong!"
          }
  }
  

  Running caddy like this directly connects your jelly.domain.dev domain to your selfhost ip on a specific port. From within your selfhost you ensure that you’re only allowing in the IP of the VPS, so no one can else can directly connect.

  Works great.

  source

  • TentinQuarantino@feddit.org ⁨2⁩ ⁨weeks⁩ ago

    Thank you for your tip! Reverse proxy was one of the techniques I was referencing in my post. But somehow I didn’t get how this thing functions. It’s easier than some might think actually. But on the weekend I have to sit down and nail it down to a solution

    source