likesboc

Some Dockers show you which IP they are using. Plus there are various test tools and websites out there that show which adress is used.

Are you assuming i would be using mutliple tunnels at the same time? Because that is not the case. But of course i configure multiple tunnels to change exit adresses for example or to switch if a tunnel is in error. How else should i do that? Any recommendations?

Hello, i've upgraded to 6.12.3 and attached a new diagnostics file. I am not using IPv6 (at least not intentionally, i am on a private IPv4 subnet, with no specific changes to the containers besides using wg0). This time i was able to upgrade and reboot without a hassle and no stuck services. I had to re-import the tunnel configuration because the old one didn't work anymore (as you had mentioned). After adding a new configuration the tunnel started as well as the dockers. So, to me, it still seems that after the last reboot the system believed that the autostart of the tunnel had worked and let the dockers online, not noticing that in reality the tunnel wasn't online. The only thing i changed in the past weeks was the ipv4 adress of the system after rearranging subnets, but that worked without any errors. diagnostics-20230717-2225.zip

and it happened again. i needed to change the ip of the system, which lead to having to reboot it (because the docker service hung, and it couldn't unmount the cache drive, so i rebooted the whole system). after the reboot is done and i start the array i check in the vpn settings if "autostart" is done and ... it isn't. the tunnel cannot be started - but i can start dockers which go online with my original ip! i checked if there is anything showing up in the logs when i try starting the tunnel manually but it just states "Tunnel WireGuard-wg1 started" which it is not. so the system believes the tunnel is starting although it isn't. this is super creepy and if i hadn't double checked i would have never noticed! diagnostics-20230713-2120.zip

Thanks for getting back to me. I'm running 6.12.2. Everything was fine until the last reboot while upgrading to 6.12.2. I am running the VPN profile exactly as outlined and have done so successfuly since the feature was released. After the upgrade/reboot apparently the wg0 tunnel was unable to start. When trying to start it manually, it didn't, the button just switched back to the off position. I then saw that the dockers, although configured for wg0, where in fact, online. I added a second tunnel wg1 which startet instantly and provided the dockers it's service. So the only thing out of the ordinary was that wg0 was somehow unresponsive although it had worked fine before. I didn't change the configuration or anything like that. (Independently from that i am unable to delete the wg0 tunnel. I am able to delete the configuration bound to it, but the tunnel itself remains empty in the settings menu. I always found that a bit weird but thought Unraid just needed an empty first entry in this menu. )

Although my Wireguard tunnel "wg0" is set to "Autostart" in settings - VPN Manager the connection failed to start for some reason. Despite that, i just noticed that a docker, which is configured to use the respective tunnel "wg0", was online with my actual ip, bypassing the tunnel setting completely. I am in shock honestly - this is the second time (!) this is happening and i find it beyond frustrating.

Hey, thanks for looking into this. I understand the feature has to be activated before working, however, the docker containers are configured to use the vpn tunnel exclusively (wg0 in my case). I don't see a reason why the container should fallback to the default network unless configured that way. If wg0 isn't there, it should not be able to connect regardless of the state of the tunnel. At least that is my logic In my configuration there is no DHCP involved, the network is configures statically an i'm am not using autostart on containers. Thanks! Cheers

I'm (relatively) certain i had autostart for the tunnel on, after i had rebooted the system it was off though. Thank you for looking into it, i feel it's important that this works in all scenarios.

Hi, yes i am talking about the new Unraid built in VPN Feature. When i disconnect the tunnel manully the dockers also lose internet access, so this works. My issue was caused by a reboot i think. I had to turn of the whole system and when i turned it back on again i forgot to enable the VPN tunnel. I think this is an error though because the dockers are configured to use the tunnel "wg0" but when i don't turn it on after a reboot, the dockers can go online anyways, ignoring their setting to use "wg0" exclusively. I feel the dockers should remain offline as long the tunnel is offline, even (or especially when) i forget turning it on.

I just realised that the VPN tunnel i'm using is down. I am connected to it through the built in Settings/VPN Manager tool. I was certain that Dockers that are connected through this tunnel (called wg0) are offline, when the tunnel is offline. They are not, i'm a bit in shock. Is this working as intended? What is supposed to happen when the tunnel is down? The dockers just fallback to the regular connection revealing my adress?

i've disabled the builtin vpn feature and switched to the unraid os wireguard solution. rutorrent works well behind the tunnel wg0, i just can't get a port working with it. i've activated a port with my vpn provider and i've setup that port with rtorrent but it's not listening. what might i be missing? thanks!

hi, i've successfully made use of the new wireguard feature, providing more security/privacy to docker containers. i want to forward a port from my vpn provider to a docker that is using the tunnel per wg0 - how do i do that? thanks for any tips!

what do i need to do to make use of the new "unraid built in wireguard"? i have been running your plex server in host mode for a long time, it answers on my unraid's ip adress at port 32400. when i switch from host mode to the wg0 tunnel the plex website becomes unresponsive. i have a "vpn tunneled access for docker" tunnel active to hide the plex server behind it. i guess i have to use a different ip locally? but how do i set it? i tried figuring out the ip it receives per console, but the adress it gets (a private 172 adress) isn't responsive either. i'm thankful for any hints!

I found it, this is not a docker but a plex issue. Apparently the Video Preview Thumbnails can become very large. If anyone else stumbles across it, here is the description.

Alright, thx, i didn't move the appdata folder at all, at least not that i know of. I found that the media folder is very big /mnt/cache/appdata/binhex-plex/Plex Media Server/Media/localhost# du -a -h --max-depth=1 | sort -hr 248G . 17G ./4 17G ./3 17G ./1 16G ./f 16G ./d 16G ./c 16G ./b 16G ./9 16G ./8 16G ./7 16G ./6 16G ./5 16G ./2 16G ./0 15G ./e 15G ./a Is this the structure you mean? Can i reduce the size somehow? I guess i could reinstall the docker but i'd need to do a proper backup/restore so i don't lose the view stats and playlists i guess