internetfriend

Its weird, I just started encountering this too when switching from Mullvad to Proton. Eliminating the VPN removes the issue, and using Mullvad doesnt cause it, but something proton is doing just messes with the whole thing. The download usually still completes, so the errors are kind of harmless albeit annoying but even more weird since you'd expect some failures. I tried futzing with the nameservers and the timeout periods within SAB too, because its not a Binhex-sabnzbdvpn container error, its definitely protonVPN, but nothing seems to sort it. Its also not consistent, some downloads go through without a hitch and some do it, but the ones that do it reliably do it. If anyone else ran into this and worked out a solve on their side, I'd love to know! Thank you in advance. 🙇‍♂️

I'm actually running into the exact same issue with the exact same setup (following Spaceinvaderone tutorial) - So I'm curiously watching this thread. Turned out to just be a dropped forwarded port on my router, we're back in business!

Got everything back up and running, I have sonarr, radarr and nzbyhdra2 running inside this container, and I was able to quickly get nzbhydra back up and running but I ran into a wall with sonarr. I ended up fixing by mapping the port to the internal port vs the external port. For example for my SABNZBD installation, the port 8080 is mapped to 6700 externally, and while I previously connected sonarr and radarr via IP:6700, I not only had to change from IP -> localhost but also 6700 -> 8080. Not sure if its worth adding to the FAQ because my setup was weird/bad, but if anyone else runs into issues trying to connect sonarr and radarr, make sure not only is the internal IP set to localhost, but also the internal ports. Thanks again for everything @binhex! you the GOAT.

Came here exactly to ask about what I broke, and you already called out what I need to do. Back in business!

This fixed my issue as well, thanks a ton!

I'm actually fighting with the same problem, I just set up wireguard and can access any container not under a binhex-VPN enabled container. There is a FAQ to address this here under Q2: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md My issue is that I did add that script to my go file and also enable it immediately with /sbin/modprobe iptable_mangle , but I still cant access the containers. Is there any way to debug and see if the connection attempt is happening and where it is failing?

So you're using this docker successfully with mullvad+wireguard with good speed? (vs just working overall) I'm considering switching to them when my year sub to PIA expires in a couple months because of their buyout but the VPN provider I buy completely hinges on how well it performs with this app and the binhex-sabnzbdvpn app haha. Not concerned about SAB because that's less nuanced with port forwarding and all that, but if people are seeing good non-throttled speed with port forwarding working with mullvad I've love to hear about it. Edit: screw it, I'll probably just buy a month's worth since they bill monthly regardless of plan. Fingers crossed I can migrate easily without screwing it up too much. Thank you!

Sweet, awesome to hear. I ended up just blocking ipv6 at the router modem level too just in case but lovely to hear that there's a 2 layer protection scheme in place in case my ISP supplied modem decides to "change its mind" with my settings during some firmware update or whatever. thanks again!

I just recently upgraded from cable to fiber and noticed that the fiber modem issues out ipv6 addresses alongside ipv4. I read about how ipv6 can leak out your actual IP, and while PIA blocks it at the app level on windows, I'm curious on if this container with either openvpn or wireguard would do the same. Is there a way to test? Love the app, thank you!!

For people having issues with PIA and port forwarding, try SPAIN, seems to work ok for me right now. For binhex, THANK YOU for maintaining such a good piece of kit. Throwing some beer money your way which should go extra far vs spending $8 on a pint since none of us can go to bars depending on where we live....

No worries thanks for the response. I ended up just taking a screwdriver to it and it gave in easily.

Weird question. I just bought one of these used and it turns out that it didnt come with a key. It looks like all n36,40,54L servers have the same key, a W-23 from southco. If I paid for postage would someone perhaps be able to cut me a copy and mail it to me or send me their spare if they dont need it? I gotta mail the thing back if not and aye yi yi. Thanks!

Would you run the check that doesn't correct correct errors, or can I just hit check on the stock UNRAID page? Many thanks as always Joe.

Hi you might remember me from fun posts such as "Why is my 2tb drive reporting as 1tb" and "I had to format this drive in partition magic to get all my space on a new drive wtf" Anyways 2 of my 3 drives have finished a 5 pass preclear, and as far as I see I think I am good. If I didnt have the formatting issue I'd just jam ahead, but thought why not ask. results + smart below: SDC ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Seek_Error_Rate = 200 100 0 ok 0 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 176 163 021 Pre-fail Always - 6191 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 20 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 150 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 17 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 25 194 Temperature_Celsius 0x0022 120 116 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SDD == Disk /dev/sdd has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Seek_Error_Rate = 200 100 0 ok 0 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. SMARTT ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 176 166 021 Pre-fail Always - 6158 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 20 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 147 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 17 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 20 194 Temperature_Celsius 0x0022 119 115 000 Old_age Always - 31 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 So if we're good I am going to replace my parity drive and 1 data drive. Are my next steps to replace parity, rebuild, then replace a data drive, and rebuild one more time? thanks all!