likesboc
-
Posts
41 -
Joined
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by likesboc
-
-
5 hours ago, bonienl said:
You have two wireguard tunnels with the same IP address, that won't work. Delete the duplicate tunnel.
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.
-
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!
-
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.
-
On 9/20/2022 at 2:09 AM, ljm42 said:
If the Docker containers are started *before* the WireGuard tunnel is started, then they can access the Internet over the default network.
BTW, if your WireGuard tunnel was set to autostart but it didn't, the issue is likely that your network did not initialize in the expected amount of time (i.e. the DHCP server was too slow). Unraid 6.11.0 has code to work around this, but in the meantime you can speed up your network initialization by statically assigning an IP address rather than using DHCP.
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
-
12 hours ago, ljm42 said:
Interesting, we'll need to do some testing to see if we can reproduce this. But in the meantime if the Docker containers are set to autostart I'd recommend setting the VPN tunnel to autostart too.
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.
-
On 9/16/2022 at 5:15 AM, ljm42 said:
To test it, setup the tunnel and containers as described at the url above. Then disconnect the tunnel and confirm the containers lose access.
If you are able to reproduce a problem, please provide the exact steps to do so.
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!
-
18 hours ago, likesboc said:
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
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
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.
-
6 minutes ago, Squid said:
Many possible reasons for that. Main biggie reason though would be if you copied the appdata somewhere and then placed it back and didn't structure the commands appropriately to handle all the symlinks etc present which will seriously bloat the appdata
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 ./aIs 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
-
Hi, so i am investigating what uses up lots of space on my cache drive and i found that my binhex-plex docker currently uses 261GB. i found the size by doing the following command
du -a -h --max-depth=1 | sort -hr 278G . 261G ./binhex-plexIs this normal? It does take care of lots of files but i find that a bit much? Is there anything i can do about it?
-
6 hours ago, trurl said:
And if these are torrents, it could be that lots of files are getting created at the same time on cache, and then as they download, the total size becomes too large for cache.
i see, this could be it, it was multiple files. circumventing the cache drive appears the only valid option in this case. thanks for the guidance!
-
21 hours ago, itimpi said:
Not at all clear. Have you checked what is actually taking up the space? For instance do you have any dockers configured to use the cache/pool directly as this would bypass that setting?20 hours ago, trurl said:And of course, any share set to cache-only will not overflow. Besides the usual appdata, domains, system, which shouldn't grow unless you have misconfigured something, you have a few other shares that are set to cache prefer or only. What is the purpose of these? How large are they?
You can see how much of each disk is being used by each user share by clicking Compute... for the share (or the Compute All button) on the User Shares page
I'm trying to manage a download that is larger than my cache drive. It is being downloaded into a share that uses the "Yes : Cache" Setting. Thus i thought it would use up all available space (900/1000gb see the setting from above) and then overflow into the array. It didn't though. For the transfer i'm targeting my share located at "/mnt/user/downloads/" - if i understand it right this shouldn't bypass the set limit of keeping 100gb free.
-
On 5/10/2021 at 8:15 PM, itimpi said:
What version of Unraid are you running? For UnRaid 6.8.3 there is a Minimum Free Space setting for the cache under Settings -> Global Share Settings. For the current UnRaid release (where you can have multiple pools) you set Minimum Free Space for a particular pool by clicking on it on the Main tab.
sadly it happened again, that setting did not prevent the cache from filling up. am i doing something wrong?
-
On 5/17/2021 at 4:08 PM, Squid said:
Excluded folders has nothing to do with whether or not the apps are stopped or not. You want to click the advanced settings link at the bottom.
alright, i'll check it out. thx!
-
On 3/22/2021 at 6:53 PM, likesboc said:
hi, i'm facing the problem that some dockers do not turn on again after the backup. every monday morning, after my sunday night backup, i see that "binhex-jacket" and "binhexx-radarr" are turned off. how can i find out what is causing this? thanks!
I'm still facng this issue. What can i do to follow up on this? Every monday morning those docker containers are shutdown although they are excluded through the "excluded folder" option. Any help is appreciated.
-
10 minutes ago, itimpi said:
What version of Unraid are you running? For UnRaid 6.8.3 there is a Minimum Free Space setting for the cache under Settings -> Global Share Settings. For the current UnRaid release (where you can have multiple pools) you set Minimum Free Space for a particular pool by clicking on it on the Main tab.
I'm running 6.9.2, that global pool setting is what i was looking for. I could swear i had this set already. What put me using it off before was the "not enought space error" that is mentioned in the description. I set it to 100GB and i hope this means it will overflow when it only has this amount left. Thank you very much for your help!
-
I have various shares using the cache drive. How can i achieve that they don't fill it up completely? The "minimum free space" setting doesn't make sense to me as it only applies to single files? I'd like all the shares on my cache drive to use up 80% of my cache so that i never run the risk of having dockers or other system shares halt.
-
Hi,
i need to manage a download larger than my cache drive. I vaguely remember having set a max usage limit to 80% of the cache drive but can't seem to find it anymore. I thought the cache would fill up and overflow to the diskshare after it reached this limit, thus the huge download wouldn't be a problem.
In reality the cache drive filled up to 100% all dockers crashed and i had to reboot the whole system
How can i resolve this? I want to keep using the cache drive for downloads, offloading per mover at night.
Thanks!
-
Alright, thank you for your tip, i'll check it out. Thanks!
In my configuration there is no DHCP involved, the network is configures statically an i'm am not using autostart on containers. Thanks! Cheers
Unraid leaked my IP - again!
in General Support
Posted
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.