August 17, 20241 yr Hello, this issue is bugging me for a while and I have exactly zero clues where I can look for a fix. Here is whats happening: I have a gigabit cable internet connection, I can easily saturate that connection with my main PC, when I download a steam game for example (110-120ish MB's), no problems occur here. If I now try to download something on my Unraid Server at over 30-40-50ish MB's my entire network gets knocked out, I cant access the unraid UI or any other docker UI for that matter and I can't reach any websites. The network is knocked out for a few seconds(20-30) and then comes back online, just for it to shortly after get knocked out again. This is quiet the issue as I would like to have download that are fast and dont knock out my entire network. Here are a few things I observed / important notes: - Dockers I tested it with were (both binhex, both protonvpn) qbittorrentvpn,sabnzbdvpn - I use wireguard to connect to the server, tho my PC is in the network and uses ipv4 and no wireguard config - There is nothing in the logs (log tab in the unraid web UI) - The network dies for the server too (in case one can think it just saturates the server) - I have a fritzbox 6690 cable router - Server is a HPE ML350 Gen9 Again, I can saturate my connection as much as I want with other devices, so my guess is, that its either with unraid and my configuration, or the dockers I use. I'm really clueless to what could cause this issue, hence why I tried to provide anything that I can think off, if anyone has any idea please let me know. bocchi-diagnostics-20240817-0504.zip
August 17, 20241 yr Community Expert yeah, thats normal... I managed to get around it, by editing the download docker's settings to: Give him a custom network with its own ip address. No idea HOW, but it works.
August 17, 20241 yr Author 6 hours ago, MAM59 said: yeah, thats normal... I managed to get around it, by editing the download docker's settings to: Give him a custom network with its own ip address. No idea HOW, but it works. Sadly it didn't work for me ()
August 17, 20241 yr Author Solution Ok I figured it out, what a dumb issue to have. Apparently ProtonVPN has a feature called Moderate-NAT when you create a wireguard config (for my download dockers) and for some reason, don't ask me why, it causes this issue. So if you are having a similar issue, uncheck this box when creating a config and you should be good.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.