After a bit of time, the conteiners or apps in casaOS are not reacheble any more from nordvpn mechnet

salvatoreG · January 1, 2025, 4:22pm

Hi guys,
thank you for to open this topic.
I have a strange issue on my server.
I installed on ubuntu server 24 casaOS. On ubuntu server I configured nordVPN with meshnet that allows LAN domain and meshnet domain.
On casaOS I installed two containers apps. NextCloud and Crafty.
This containers are reacheble on both domains to begin after start server. So from LAN ( like 192.168…) and meshnet than hostname or ip from nordvpn.
After a bit time they are not reacheble from mechnet domain but only LAN domain.
I have to restart server for return them available on both domain.

Some information regard my system:
sudo uname -a
[sudo] password for server:
Linux homeserver 6.8.0-51-generic #52-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 5 13:09:44 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

network system
ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group 57841 qlen 1000
link/ether 00:23:24:ee:83:a2 brd ff:ff:ff:ff:ff:ff
altname enp1s0
inet 192.168.1.6/24 metric 100 brd 192.168.1.255 scope global dynamic eno1
valid_lft 41034sec preferred_lft 41034sec
inet6 2a01:e11:1005:4d50:223:24ff:feee:83a2/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 86194sec preferred_lft 86194sec
inet6 fe80::223:24ff:feee:83a2/64 scope link
valid_lft forever preferred_lft forever
3: nordlynx: <POINTOPOINT,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
link/none
inet 100.111.63.196/32 scope global nordlynx
valid_lft forever preferred_lft forever
4: br-d31cbfdff17c: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:67:43:c4:a0 brd ff:ff:ff:ff:ff:ff
inet 172.21.0.1/16 brd 172.21.255.255 scope global br-d31cbfdff17c
valid_lft forever preferred_lft forever
inet6 fe80::42:67ff:fe43:c4a0/64 scope link
valid_lft forever preferred_lft forever
5: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:4b:6b:4a:bf brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
inet6 fe80::42:4bff:fe6b:4abf/64 scope link
valid_lft forever preferred_lft forever
6: br-fe92652bf6d8: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:c3:b7:45:02 brd ff:ff:ff:ff:ff:ff
inet 172.19.0.1/16 brd 172.19.255.255 scope global br-fe92652bf6d8
valid_lft forever preferred_lft forever
7: br-1b98dd52377e: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:b4:58:38:d2 brd ff:ff:ff:ff:ff:ff
inet 172.18.0.1/16 brd 172.18.255.255 scope global br-1b98dd52377e
valid_lft forever preferred_lft forever
8: br-5b938987d109: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:66:07:81:49 brd ff:ff:ff:ff:ff:ff
inet 172.20.0.1/16 brd 172.20.255.255 scope global br-5b938987d109
valid_lft forever preferred_lft forever
10: veth44d7497@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-d31cbfdff17c state UP group default
link/ether 4a:22:be:22:60:3c brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::4822:beff:fe22:603c/64 scope link
valid_lft forever preferred_lft forever
12: vethf8d075a@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether 8e:b7:1c:aa:57:2f brd ff:ff:ff:ff:ff:ff link-netnsid 4
inet6 fe80::8cb7:1cff:feaa:572f/64 scope link
valid_lft forever preferred_lft forever
14: veth3ae1ec5@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-d31cbfdff17c state UP group default
link/ether 5a:27:27:33:09:87 brd ff:ff:ff:ff:ff:ff link-netnsid 2
inet6 fe80::5827:27ff:fe33:987/64 scope link
valid_lft forever preferred_lft forever
16: veth09cc969@if15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-d31cbfdff17c state UP group default
link/ether 7e:53:dd:30:be:54 brd ff:ff:ff:ff:ff:ff link-netnsid 3
inet6 fe80::7c53:ddff:fe30:be54/64 scope link
valid_lft forever preferred_lft forever
18: veth29a0a33@if17: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-d31cbfdff17c state UP group default
link/ether aa:63:31:c7:7a:24 brd ff:ff:ff:ff:ff:ff link-netnsid 1
inet6 fe80::a863:31ff:fec7:7a24/64 scope link
valid_lft forever preferred_lft forever

hardware system:
on link google drive

Docker containers configuration:
on link google drive, same link.

Into link there is a zip file with text files. Reply from lshw and yaml files

Thank you for your interesting.

Have good day

salvatoreG · January 1, 2025, 4:25pm

I fogot it.
CasaOS web UI and SSH connection are available also when the containers apps on meshnet domain are not working any more on both domain.

Adam_Meshnet · January 9, 2025, 9:58am

Hey @salvatoreG,

It sounds a lot like you need to grant your Meshnet peers local network access permission. Meshnet treats Docker containers as local networks, so they won’t be accessible without this permission.

To allow local network access, use this command:

nordvpn meshnet peer local allow [command options] <peer_hostname>|<peer_nickname>|<peer_ip>|<peer_pubkey>

You will have to do that for your remote devices from your CasaOS terminal.