Wireguard | Can't reach OMV

Hi all,

once I've changed my laptop I'm not able to access OMV via wireguard (installed with docker). Nothing is changed in my configuration, and even with other PCs, from different network, I can't reach out the server. Below my actual configuration for peer1:

[Interface]
PrivateKey = [...]
ListenPort = 51820
Address = 10.13.13.2/32
DNS = 10.13.13.1


[Peer]
PublicKey = [...]
PresharedKey = [...]
AllowedIPs = 192.168.178.0/24
Endpoint = myomvhost.duckdns.org:51820

and here my docker .yml:

version: "2.1"
services:
    wireguard:
        image: lscr.io/linuxserver/wireguard:latest
        container_name: wireguard
        cap_add:
            - NET_ADMIN
        environment:
            - PUID=1001
            - PGID=100
            - TZ=Europe/Rome
            - SERVERURL=myomvhost.duckdns.org
            - SERVERPORT=51820 #optional
            - PEERS=4 #optional
            - PEERDNS=auto #optional
            - INTERNAL_SUBNET=10.13.13.0 #optional
            - ALLOWEDIPS=192.168.178.101/24 #optional
            - PERSISTENTKEEPALIVE_PEERS= #optional
            - LOG_CONFS=true #optional
        volumes:
            - /Config/wireguard:/config
        ports:
            - 51820:51820/udp
        sysctls:
            - net.ipv4.conf.all.src_valid_mark=1
        restart: unless-stopped

Does anyone could help please?

Thanks!

Mime

Ciao ryecoaaron, thanks for reply.

I was using docker since OMV 6. It gives me much control and I've never had any trouble until now.

Even the user I set is dedicated and granted to docker, so I just can't understand what is happening now.

Thanks,

Mime

I update docker images constantly, but nothing seems to be changed. As I posted .yml file is stored in my config folder, using compose instead of portainer to set configurations.

Ciao gderf,

if you set local IP you'll not be able to connect from remote.

So I tried this way and it works when I'm in same local network, but from external network I can't reach OMV again.

Thanks anyway!

Mime

Quote from gderf

Get an appropriate keyfile from your VPN provider. Make changes to it at your own risk.

I'm not sure I've understood properly. I've installed wireguard in a docker container on OMV and set the client on my laptop. If you mean the private and public key I've hidden both in my first post... They are correct in my conf file.

Quote from gderf

No, I do not mean the public and private keys.

Where did you get this from?

Endpoint = myomvhost.duckdns.org:51820

I set it from duckdns, but it's not the real one... it's just an example to let understand my configuration. I thought it was clear XD

Good morning,

after several tests I resolved that my connection is under GNAT and so on...
I tried to install Tailscale, as well with docker, and I could find the nginx page by the hostname. Unfortunately I'm not able to connect directly to OMV. I read somewhere that Tailscale has to be set as "HOST", but I coudn't find any guide on the web. Below my yml configuration:

services:
    tailscale-nginx:
        image: tailscale/tailscale:latest
        hostname: MimeOmv
        environment:
            - TS_AUTHKEY=<my_auth_key>
            - TS_EXTRA_ARGS=--advertise-tags=tag:container
            - TS_STATE_DIR=/var/lib/tailscale
            - TS_USERSPACE=false
            - TS_EXTRA_ARGS=--advertise-exit-node
            - TS_ROUTES=192.168.101.0/24
        volumes:
            - /Config/tailscale-nginx:/config
            - /dev/net/tun:/dev/net/tun
        cap_add:
            - net_admin
            - sys_module
        restart: unless-stopped
        nginx:
            image: nginx
        depends_on:
            - tailscale-nginx
        network_mode: service:tailscale-nginx

Does anyone could help please?

Thanks.

I love you. Definitely.
It works great! And with hostname I'm able to connect to the remote folders as the local ones.

Thank you so much for your help, you saved my nights.