Remote access

Hello everyone,

OMV is great and working well for me.

I know that a NAS is never supposed to be exposed on the Internet, but still I want to expose a few ports so I can control a few things remotely.

My ISP gives me a public IP address so I set up DDNS and fort forwarding rules on my router. For some reason remote access is not working, here's some TCPdump info on the OMV machine:

Visiting OMV using DDNS address on a device in the same LAN: you can see the incoming and outgoing packets

Visiting OMV using DDNS address on the same device but from Internet: you can see the incoming packets but no outgoing ones, it seems that my OMV machines receives the request but never responds.

I'm confused by this, appreciate all your help.

Zitat von tinh_x7

Have you install the OpenVPN plugin ?

In a docker container yes

Zitat von gderf

It would be more helpful if you said what ports are being used/forwarded.

Zitat von tinh_x7

There is a plugin for that, no need to use Docker.
As gderf mentioned, more details would be helpful for troubleshooting.

Thank you guys.

The port I'm forwarding is 9091, I've tried to forward other ports too like port 80 (just for testing, I don't plan to expose port 80 on the Internet), the same happens.

I use OpenVPN in a docker container so that whatever application running inside that container is protected by the VPN, I don't need the whole OMV machine protected by the VPN.

Also here is the iptables if it helps

Zitat von gderf

No idea why you have the firewall running on your pi, if it's behind a NAT router it's unnecessary. But if you insist on doing this then you need to get things working without it, then do what it takes to keep things working with it running.

Your understanding of the OpenVPN docker is not correct. "whatever application running inside that container is protected by the VPN" .......uh....nope.

I believe those rules were created when the docker containers are created.

You are right, my understanding of the OpenVPN docker was incorrect. The VPN is active, remote requests will be treated as "non-local" traffic and therefore be routed out through the VPN interface.

I've created a reverse proxy, now the problem is solved, thanks!