Jump to content

internetfriend

Members
  • Posts

    116
  • Joined

  • Last visited

Posts posted by internetfriend

  1. On 10/9/2023 at 1:44 AM, SaltyKram said:

    supervisord.log 38.67 kB · 1 download

     

    Hi Binhex, 

     

    I'm having an issue with warnings of timeout connections using ProtonVPN with Sabnzbvpn. It looks like the below: 

     

    WARNING 4 minutes ago Failed to connect: [Errno 9] Bad file descriptor news.eweka.nl:563 (81.171.92.219)
    WARNING 4 minutes ago Failed to connect: [Errno 9] Bad file descriptor news.eweka.nl:563 (81.171.92.219)
    WARNING 4 minutes ago Failed to connect: timed out news.eweka.nl:563 (81.171.92.219)

     

    Although the above is Eweka, it appears to happen with connections to all of my other backup providers as well - it seems to depend on if it is actively being used/connected to. Sabnzb and my downloads appear to continue downloading even after this error shows up. 

     

    Prior to using ProtonVPN, I have used Mullvad in this same container flawlessly. I am currently using ProtonVPN in your qBittorrent container also without issue. 

     

    I have switched ports on the providers from 443 to 563, switched from Wireguard back to openvpn, added 8.8.8.8 to the name server - all result in the same error. The only thing that fixes these warnings is switching back to Mullvad, so it seems to be specific to ProtonVPN. 

     

    My redacted debug log is attached. Any ideas on how I can make ProtonVPN work?

     

    Thanks!

     

     

    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. 🙇‍♂️

  2. 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.

    • Like 1
  3. 16 hours ago, binhex said:

     

    IMPORTANT:- As part of the tightening up if you run multiple containers through a single vpn container then please ensure you define all web ui ports (if more than 1 port then use comma to separate) for all routed containers in 'ADDITIONAL_PORTS' env var for the vpn container.

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

    • Like 1
  4. 6 hours ago, binhex said:

    most probably you need to add your wireguard network to the LAN_NETWORK env var for sabnzbdvpn, otherwise it will be blocked when you are on the vpn, if you want more than one network then use a comma to seperate the values.

    This fixed my issue as well, thanks a ton!

    • Like 1
  5. 20 hours ago, LoneTraveler said:

    Hi, 

     

    I thought I would post here as my issue seems to be Sabnzbdvpn specific. 

     

    I am utilising Wireguard to access my UNRAID remotely and can fire up all dockers and use them as if I was local, except for Sabnzbdvpn, it just times out. 

     

    Sabnzbdvpn is configured the same as the other Binhex containers in that it uses a custom network so they can all talk to one another, and I'm able to access them the same as any other container, except for Sabnzbdvpn. 

     

    I'm sure this is a simple error on my behalf, but if anyone can advise, it will be greatly appreciated. 

     

    Thanks. 

    Screenshot_20210210-082845_Bromite.thumb.jpg.299e2982ab543c981f73ca7b0bc705ed.jpg

     

     

     

    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? :(

  6. On 2/4/2021 at 12:53 PM, crafty35a said:

    Great work on this! I'm completely new to Docker, but did eventually get this working on Windows in Hyper-V mode (Mullvad/Wireguard).

    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!

  7. 13 hours ago, binhex said:

    There should be no concern around ipv6.

    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!

  8. 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!!

  9. 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.... :(

    • Like 1
  10. Right on! This is actually the system I was using before heroku was banned by southwest: https://github.com/samyun/southwest-price-drop-bot 

     

    However it doesn't seem to have a docker hub entry. Before I go down the path of setting up the one I linked before, is it possible to deploy this git into a docker and use it instead without there being an existing docker file in the hub?

     

    Thanks again for your help, its very appreciated!

  11. I'm trying to get this app installed into a Docker: https://github.com/xur17/southwest-alerts 

    It has a dockerhub entry which I tried but it fails to boot in unraid, probably because the variables are not being properly set.

    Its a cool app, it monitors Southwest flight prices and lets you rebook to save some cash when the flight prices drop.

     

    Is there something I can do to add it to my server? I'm good enough to get containers going for my entertainment apps but something custom like this is beyond me. :(

     

     

    Thank you!

     

  12. Hello! I've run Unraid 6.1.9 for quite a while on older hardware. I wanted to downsize so I moved all my drives to an n40L server I had handy and pretty well known on the forums. Unfortunately I'm unable to get the LAN working, ifconfig eth0 reports nothing back.

     

    EDIT: I was able to solve by doing a bios reset, who knows what was kicking around in there.

     

    My diagnostics file is attached, the remaining issue is the only drives being detected are from my expansion card and the OD Sata cable, and not the 4 drive hot swappable ones.

     

    Would an IDE to AHCI mismatch cause that perhaps?

     

    EDIT: I'm a dumbass and didnt check for loose cables.

     

    All is well!

    QONVIyz.gif

     

    Thank you!

    tower-diagnostics-20160930-2156.zip

  13. 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!

  14. Hey Friends,

     

    I awoke to my UNRaid server sending my email a cryptic note every minute until I shut it down.

     

    SUBJECT: cron for user root /usr/lib/sa/sa1 2 1 1> /dev/null

    BODY: Cannot write data to system activity file: No space left on device

     

    Exactly on the minute for hours. Is that command familiar with anyone? Just trying to debug this, though after a reboot its stopped itself.

     

    I'm still kicking around on 5.0-rc16c; I'm a little concerned that when I update my addons are all going to be trashed; but I assume theres no merit there in worrying?

     

    Thanks guys!  :D

    syslog.txt

  15. 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!

  16. Alright, so W  T  F.

     

    Here's what I have done so far.

    • Added disk to windows, reported only 1tb in windows xp (jumpered mind you)
    • shut down, ran partition magic from DOS prompt who sees 2TB. Installed an NTFS partition across whole drive.
    • Booted to windows. Windows sees 2TB (WHAT)
    • Boot WD Diagnostic app, Sees 2TB. (WHATx2)
    • Put drive back into UNRAID. Unraid sees 2TB (WHATx3)

     

    Here is an HDPARM full and what you asked for earlier (-N) along with a SMART, and what I see in PRECLEAR.

     

    /dev/sdc:

    max sectors  = 3907027055/14715056(18446744073321613488?), HPA setting seems invalid (buggy kernel device driver?)

     

    HDPARM FULL: http://pastebin.com/TTbtRSUV

    SMART: http://pastebin.com/FvBkWY8s

    PRECLEAR: http://dl.dropbox.com/u/519591/UNRAID/Unreal.JPG

     

    So I mean, I guess I'm good if this passes preclear, right?  ???

     

    Holy hell what a morning.

     

     

  17. Haha, well shit. My server is old, its a HP Proliant 110ML so I wouldn't be surprised if there's something funny in the bios. If I drop the drive into my desktop (current tech) and it stays at 1TB then yeah theres a problem.

    If I do that and it DOES show up at 2TB, what would my next steps be? My bios in the server is pretty much up to date (there's an update but it has nothing to do with this issue and I'd rather not mess with it if I don't need to) and the SATA card has no issue with it, though it happens on both the mobo and the SATA card.

     

     

    If I format it in windows, will PRECLEAR still function or will it assume it has been "used" and not want to function? Or can I just run it again and it wipes it all clean? (Basically does it refuse to run if it finds a NTFS partition)

     

    I really hope these aren't fake/busted, they came from Newegg and Newegg usually doesn't do that kind of nonsense. At least I kept all the boxes in case I need to mail them back I suppose.

     

    Thanks as always for the help Joe.

     

  18. SDD

    /dev/sdd:

    max sectors  = 1953569134/14715056(18446744073321613488?), HPA setting seems invalid (buggy kernel device driver?)

     

    SDC

    /dev/sdc:

    max sectors  = 1953569134/14715056(18446744073321613488?), HPA setting seems invalid (buggy kernel device driver?)

     

    I tried pulling the jumper just for grins to see if anything showed up differently, same deal though.

     

    I shut down and put in my 3rd (I bought 3) which showed up as SDC as well since I cant run all 3 at once.

     

    here is disk 3.

     

    /dev/sdc:

    max sectors  = 1953569134/14715056(18446744073321613488?), HPA setting seems invalid (buggy kernel device driver?)

     

    they were all manufactured on the same date, and purchased from the same retailer, but I think thats kind of odd for them to all have the same issue dont you think?

     

    For grins, here is an HDPARM for one of my data drives, a WD 1tb BLACK model.

    http://pastebin.com/Mrhqb1F6

     

    /dev/sda:

    max sectors  = 1953525168/7368112(1953525168?), HPA setting seems invalid (buggy kernel device driver?)

     

    Yeah so I am at a loss. :(

    New server time? haha.

     

     

×
×
  • Create New...