MEnVaNic

Members
  • Posts

    19
  • Joined

  • Last visited

Posts posted by MEnVaNic

  1. 4 hours ago, MEnVaNic said:

    Have pretty much the same but cannot ping the container at all. They are on the same docker network other container can ping themself without problem. The on thing I found out is if I disable the vpn I can ping the container just fine. Since Iam using a VPS there is no lan_network so not realy sure what to enter here "LAN_NETWORK".

     

    Tested it on my local machine with radarr and sabnzbvpn they can ping each other just fine. Dunno where Iam wrong.

     

    Help is appreciated.

    Got it fixed. The container uses the first network it find or is connected to. Hat to used 2. Changed it back to one and everything can connect again.

  2. On 10/12/2023 at 10:24 PM, hwextreme said:

    does anyone else have issues with local name resolution?

     

    I have network for my 'Arr docker containers & SAB (all bridge mode).  I can ping my sabnzbvpn container from the other containers by name and IP address, and everything is working fine from the 'Arr applications when I point them to the IP address of the SAB container, but I cannot use the name of the container or the container ID, as when I try all of the 'Arr apps fail to connect.

     

    Im a bit lost as why they fail to connect via name when the container they are on can


    From the readarr container

    sh-5.1# ping sabnzbdvpn.dockernet
    PING sabnzbdvpn.dockernet (172.18.0.6) 56(84) bytes of data.
    64 bytes from sabnzbdvpn.dockernet (172.18.0.6): icmp_seq=1 ttl=64 time=0.

     

    from the readarr app

    Test was aborted due to an error: Unable to connect to SABnzbd, HTTP request failed: [403:Forbidden] [GET] at [http://sabnzbdvpn.dockernet:8080/api?
     

    Have pretty much the same but cannot ping the container at all. They are on the same docker network other container can ping themself without problem. The on thing I found out is if I disable the vpn I can ping the container just fine. Since Iam using a VPS there is no lan_network so not realy sure what to enter here "LAN_NETWORK".

     

    Tested it on my local machine with radarr and sabnzbvpn they can ping each other just fine. Dunno where Iam wrong.

     

    Help is appreciated.

  3. On 3/16/2021 at 7:50 AM, DoesItHimself said:

    Just updated everything on the server and I'm running into the below error. Its a paste of the log which repeats over and over as hydra tries to start. Nothing has changed on my end with the docker or any settings.

     

    I see it stating there is a corrupt config file - I've already tried to delete the container and image for it and reload from a template with no luck.

     

    Any ideas?

     

     

    2021-03-16 02:46:26,300 INFO - Determined java version as '11' from version string 'openjdk version "11.0.10" 2021-01-19'
    2021-03-16 02:46:26,301 INFO - Starting NZBHydra main process with command line: java -Xmx256M -DfromWrapper -XX:TieredStopAtLevel=1 -noverify -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/config/logs -Dspring.output.ansi.enabled=ALWAYS -jar /app/nzbhydra2/bin/lib/core-3.13.1-exec.jar --nobrowser --datafolder /config in folder /app/nzbhydra2/bin
    02:46:27.053 [main] DEBUG org.nzbhydra.config.ConfigReaderWriter - Using temporary file /config/nzbhydra.yml.bak
    at [Source: (File); line: 1, column: 1]
    java.lang.RuntimeException: Config file /config/nzbhydra.yml corrupted. If you find a ZIP in your backup folder restore it from there. Otherwise you'll have to delete the file and start over. Please contact the developer when you have it running.
    at org.nzbhydra.NzbHydra.initializeAndValidateAndMigrateYamlFile(NzbHydra.java:215)
    at org.nzbhydra.NzbHydra.main(NzbHydra.java:114)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at org.springframework.boot.loader.Launcher.launch(Launcher.java:109)
    at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49)
    at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
    Caused by: java.lang.RuntimeException: Config file /config/nzbhydra.yml corrupted. If you find a ZIP in your backup folder restore it from there. Otherwise you'll have to delete the file and start over. Please contact the developer when you have it running.
    at org.nzbhydra.NzbHydra.initializeAndValidateAndMigrateYamlFile(NzbHydra.java:215)
    at org.nzbhydra.NzbHydra.main(NzbHydra.java:114)
    2021-03-16 02:46:27,069 ERROR - Main process shut down unexpectedly. If the wrapper was started in daemon mode you might not see the error output. Start Hydra manually with the same parameters in the same environment to see it
    Logging wrapper output to /config/logs/wrapper.log

     

    You basically have to do this Config file /config/nzbhydra.yml corrupted. If you find a ZIP in your backup folder restore it from there. Otherwise you'll have to delete the file and start over. Please contact the developer when you have it running.

    This is located in the appdata!

  4. 41 minutes ago, Seraph91P said:

    The Ip keeps changing as you can see here.

    
    [debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.74.196'
    
    2020-12-10 13:23:02,157 DEBG 'watchdog-script' stdout output:
    [debug] Waiting for iptables chain policies to be in place...
    
    2020-12-10 13:23:02,165 DEBG 'watchdog-script' stdout output:
    [debug] iptables chain policies are in place
    
    2020-12-10 13:23:02,168 DEBG 'watchdog-script' stdout output:
    [debug] VPN incoming port is 51796
    [debug] qBittorrent incoming port is 51796
    [debug] VPN IP is 10.2.228.71
    
    2020-12-10 13:23:02,168 DEBG 'watchdog-script' stdout output:
    [debug] qBittorrent IP is 10.2.228.71
    
    2020-12-10 13:23:32,173 DEBG 'watchdog-script' stdout output:
    [debug] Checking we can resolve name 'www.google.com' to address...
    
    2020-12-10 13:23:32,271 DEBG 'watchdog-script' stdout output:
    [debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.12.164'

     

     

     

    35 minutes ago, binhex said:

    if you mean the following lines then that is perfectly normal and does not indicate a restart/reconnection, its simply round robin load balancing returning different ip's for a name server lookup of www.google.com:-

     

     

     

    Ok forget what I said just saw it myself this is just the dns the ip stays the same.

    But still my speeds are like all over the place from 10kbs to 10mbs and keep bouncing around is this normal? 

    After the start of the container its like super fast and stays there but after some time it crashes to kbs.

    Like 7kbs after I had 14mbs before?

    Am Downloading to the cache drive.

    Because if I try the same torrent without vpn its more steady.

  5. 19 minutes ago, binhex said:

    there is no sign of reconnection in your log snippet, what makes you think its reconnecting?

    The Ip keeps changing as you can see here.

    [debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.74.196'
    
    2020-12-10 13:23:02,157 DEBG 'watchdog-script' stdout output:
    [debug] Waiting for iptables chain policies to be in place...
    
    2020-12-10 13:23:02,165 DEBG 'watchdog-script' stdout output:
    [debug] iptables chain policies are in place
    
    2020-12-10 13:23:02,168 DEBG 'watchdog-script' stdout output:
    [debug] VPN incoming port is 51796
    [debug] qBittorrent incoming port is 51796
    [debug] VPN IP is 10.2.228.71
    
    2020-12-10 13:23:02,168 DEBG 'watchdog-script' stdout output:
    [debug] qBittorrent IP is 10.2.228.71
    
    2020-12-10 13:23:32,173 DEBG 'watchdog-script' stdout output:
    [debug] Checking we can resolve name 'www.google.com' to address...
    
    2020-12-10 13:23:32,271 DEBG 'watchdog-script' stdout output:
    [debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.12.164'

     

  6. Hey, got everything working. The only Problem I have is that the container keeps reconnecting.

    Iam on Unraid with a custom setup.

    That is quite disturbing because the torrents wont get quite to speed.

    Testet deluge aswell there it seems to be working.

    After every restart the speeds are great but then it starts to reset and they drop.

    Here is the log.

     

    2020-12-10 13:22:47,116 DEBG 'watchdog-script' stdout output:
    [debug] Checking we can resolve name 'www.google.com' to address...
    
    2020-12-10 13:23:02,157 DEBG 'watchdog-script' stdout output:
    [debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.74.196'
    
    2020-12-10 13:23:02,157 DEBG 'watchdog-script' stdout output:
    [debug] Waiting for iptables chain policies to be in place...
    
    2020-12-10 13:23:02,165 DEBG 'watchdog-script' stdout output:
    [debug] iptables chain policies are in place
    
    2020-12-10 13:23:02,168 DEBG 'watchdog-script' stdout output:
    [debug] VPN incoming port is 51796
    [debug] qBittorrent incoming port is 51796
    [debug] VPN IP is 10.2.228.71
    
    2020-12-10 13:23:02,168 DEBG 'watchdog-script' stdout output:
    [debug] qBittorrent IP is 10.2.228.71
    
    2020-12-10 13:23:32,173 DEBG 'watchdog-script' stdout output:
    [debug] Checking we can resolve name 'www.google.com' to address...
    
    2020-12-10 13:23:32,271 DEBG 'watchdog-script' stdout output:
    [debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.12.164'
    
    2020-12-10 13:23:32,272 DEBG 'watchdog-script' stdout output:
    [debug] Waiting for iptables chain policies to be in place...
    
    2020-12-10 13:23:32,279 DEBG 'watchdog-script' stdout output:
    [debug] iptables chain policies are in place
    
    2020-12-10 13:23:32,283 DEBG 'watchdog-script' stdout output:
    [debug] VPN incoming port is 51796
    [debug] qBittorrent incoming port is 51796
    [debug] VPN IP is 10.2.228.71
    
    2020-12-10 13:23:32,283 DEBG 'watchdog-script' stdout output:
    [debug] qBittorrent IP is 10.2.228.71
    
    2020-12-10 13:24:02,288 DEBG 'watchdog-script' stdout output:
    [debug] Checking we can resolve name 'www.google.com' to address...
    
    2020-12-10 13:24:02,390 DEBG 'watchdog-script' stdout output:
    [debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.12.164'
    
    2020-12-10 13:24:02,391 DEBG 'watchdog-script' stdout output:
    [debug] Waiting for iptables chain policies to be in place...
    
    2020-12-10 13:24:02,398 DEBG 'watchdog-script' stdout output:
    [debug] iptables chain policies are in place
    
    2020-12-10 13:24:02,401 DEBG 'watchdog-script' stdout output:
    [debug] VPN incoming port is 51796
    [debug] qBittorrent incoming port is 51796
    [debug] VPN IP is 10.2.228.71
    
    2020-12-10 13:24:02,402 DEBG 'watchdog-script' stdout output:
    [debug] qBittorrent IP is 10.2.228.71
    
    2020-12-10 13:24:20,259 DEBG 'start-script' stdout output:
    [info] Successfully assigned and bound incoming port '51796'
    
    2020-12-10 13:24:32,407 DEBG 'watchdog-script' stdout output:
    [debug] Checking we can resolve name 'www.google.com' to address...
    
    2020-12-10 13:24:32,426 DEBG 'watchdog-script' stdout output:
    [debug] DNS operational, we can resolve name 'www.google.com' to address '216.58.214.4'
    
    2020-12-10 13:24:32,426 DEBG 'watchdog-script' stdout output:
    [debug] Waiting for iptables chain policies to be in place...
    
    2020-12-10 13:24:32,434 DEBG 'watchdog-script' stdout output:
    [debug] iptables chain policies are in place
    
    2020-12-10 13:24:32,437 DEBG 'watchdog-script' stdout output:
    [debug] VPN incoming port is 51796
    [debug] qBittorrent incoming port is 51796
    [debug] VPN IP is 10.2.228.71
    
    2020-12-10 13:24:32,437 DEBG 'watchdog-script' stdout output:
    [debug] qBittorrent IP is 10.2.228.71
    
    2020-12-10 13:25:02,442 DEBG 'watchdog-script' stdout output:
    [debug] Checking we can resolve name 'www.google.com' to address...
    
    2020-12-10 13:25:02,541 DEBG 'watchdog-script' stdout output:
    [debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.12.164'
    
    2020-12-10 13:25:02,542 DEBG 'watchdog-script' stdout output:
    [debug] Waiting for iptables chain policies to be in place...
    
    2020-12-10 13:25:02,549 DEBG 'watchdog-script' stdout output:
    [debug] iptables chain policies are in place
    
    2020-12-10 13:25:02,553 DEBG 'watchdog-script' stdout output:
    [debug] VPN incoming port is 51796
    [debug] qBittorrent incoming port is 51796
    [debug] VPN IP is 10.2.228.71
    
    2020-12-10 13:25:02,553 DEBG 'watchdog-script' stdout output:
    [debug] qBittorrent IP is 10.2.228.71
    
    2020-12-10 13:25:32,558 DEBG 'watchdog-script' stdout output:
    [debug] Checking we can resolve name 'www.google.com' to address...
    
    2020-12-10 13:25:32,669 DEBG 'watchdog-script' stdout output:
    [debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.12.164'
    
    2020-12-10 13:25:32,669 DEBG 'watchdog-script' stdout output:
    [debug] Waiting for iptables chain policies to be in place...
    
    2020-12-10 13:25:32,677 DEBG 'watchdog-script' stdout output:
    [debug] iptables chain policies are in place
    
    2020-12-10 13:25:32,680 DEBG 'watchdog-script' stdout output:
    [debug] VPN incoming port is 51796
    [debug] qBittorrent incoming port is 51796
    [debug] VPN IP is 10.2.228.71
    
    2020-12-10 13:25:32,680 DEBG 'watchdog-script' stdout output:
    [debug] qBittorrent IP is 10.2.228.71

    Help is appreciated.

  7. On 11/12/2020 at 6:52 PM, Bobat said:

    If you're using PIA, make sure you're using the most up to date ovpn config files from the PIA site.  They just recently retired a bunch of legacy servers.  My config file was pointing to one of those old servers and I couldn't figure out why it wouldn't connect anymore.  Download the default Nextgen config files and make sure you're using the current server names.

    Have the same error. Using the latest files since my qbittorrent vpn is working fine.

    Still getting the waiting 10s error.

  8. 5 hours ago, binhex said:

    if by this you mean the following error then that can be ignored, its caused by PIA being dumb and shoving non json content into the respaonse from their api which jq then trips over:-

    
    2020-12-06 20:52:43,603 DEBG 'start-script' stderr output:
    parse error: Invalid numeric literal at line 4, column 0

     

    Yes refers to this:

     

    2020-12-07 17:02:00,691 DEBG 'start-script' stdout output:
    [warn] Unable to successfully download PIA json to generate token from URL 'https://212.102.35.1/authv3/generateToken'
    [info] Retrying in 10 secs...
    
    2020-12-07 17:02:10,724 DEBG 'start-script' stderr output:
    parse error: Invalid numeric literal at line 4, column 0
    
    2020-12-07 17:02:10,982 DEBG 'start-script' stdout output:
    [warn] Unable to successfully download PIA json to generate token from URL 'https://212.102.35.1/authv3/generateToken'
    [info] Retrying in 10 secs...

     

  9. 13 hours ago, binhex said:

    hmm ok guys i see a lot of chat about AUTH_FAILED, please can you detail which endpoints you are attempting connection to, i want to verify with a completely clean container that there are no issues on my side, i do believe at present this is all PIA, as this reddit post seems to indicate, new accounts are balked on authentication for PIA:-

    https://www.reddit.com/r/PrivateInternetAccess/comments/k60kon/openvpn_auth_failed_issues/?ref=share&ref_source=embed&utm_content=body&utm_medium=post_embed&utm_name=50ba78c8d6d4483ebc726ab1240d3fb9&utm_source=embedly&utm_term=k60kon

     

    just to be 100% clear here, i am using a wireguard connection to PIA and its stable for me, uptime on the container is currently 7 days and its still has a working PF and dl/ul are fine.

     

    edit - interestingly, a completely different docker image developer has the same AUTH_FAILED issue reported by a end user for PIA, that points the finger of blame quite firmly at PIA:- 

    https://github.com/haugene/docker-transmission-openvpn/issues/1590

    PIA Support finally answered. Treid alot with them nothing seems to have worked. Tested alot of connections like all over the world nothing seems to work.

    They also mentioned to use OpenVpn 2.4.9 since I tried to use it from my pc also no luck. Wireguard does not work either Times out or Line 4 error.

  10. 23 hours ago, Liam_Galt said:

    Yeah I've been asking support and they just tell me to make sure my credentials are correct. You're definitely not the only one. I think this is on their server side, credentials aren't propagating correctly or something. You can follow my Reddit post for some other info, but there's not anything really helpful there, either lol. 

     

    Tried now everything from that post aswell. 

    No luck so far atleast I now know how to use the cert file and not the integrated one.

    But still AUTH_FAILED. As far as I can read it it literaly says that my credentials are wrong. 
    I checked now many times changed the password 3 times. I use the correct ones.

    Dunno what to do probaply refund is the only option.

     

    2020-12-06 15:16:57 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
    2020-12-06 15:16:57 VERIFY EKU OK
    2020-12-06 15:16:57 VERIFY OK: depth=0, C=US, ST=CA, L=LosAngeles, O=Private Internet Access, OU=Private Internet Access, CN=frankfurt410, name=frankfurt410
    2020-12-06 15:16:57 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 2048 bit RSA
    2020-12-06 15:16:57 [frankfurt410] Peer Connection Initiated with [AF_INET]212.102.57.191:1198
    2020-12-06 15:16:58 AUTH: Received control message: AUTH_FAILED
    2020-12-06 15:16:58 SIGUSR1[soft,auth-failure] received, process restarting
    2020-12-06 15:17:05 ERROR: could not read Auth username/password/ok/string from management interface
    2020-12-06 15:17:05 Exiting due to fatal error

     

  11. Hello erveryone,

     

    still getting the error AUTH_Failed. 

    I use the credentials to login into the webinterface of pia the p000000 one.

    I tried every fix I found here or via google. Even tried it on my pc itself it wont connect.

    Can someone please tell me what Iam doing wrong here. Also treid wireguard which says: 

     

    "

    2020-12-05 13:06:40,872 DEBG 'start-script' stderr output:
    parse error: Invalid numeric literal at line 4, column 0

    2020-12-05 13:06:41,109 DEBG 'start-script' stdout output:
    [warn] Unable to successfully download PIA json to generate token from URL 'https://212.102.34.129/authv3/generateToken'
    [info] Retrying in 10 secs...
    "

     

    Tried it for days now please help. Oh and btw the pia support does not answer.

  12. Helly everyone,

     

    First of all Thank you for all the great work you guys do!

     

    Second: I have sucessfully passed through my Soundcard (Asus Raid DLX).

     

    On my Manjaro VM everything works fine feels sanppy.

     

    But on my Windows VM my Soundcard starts to lagg kind of. Its like its hanging and then continues to work.

    I also cannot install the Driver for the Soundcard but still it works with windows ones.

     

    I tried the MSI "fix" if it would help but its not.

     

    I have to mention the soundcard is kind of special since it has an USB Hub or Controler onborad. So I passed trough the hole thing which is so far working. I excluded it from Unraid at Boot via the vfio-pci.cfg

     

    03:00.01b21:1142USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller

         USB devices attached to this controller:

         Bus 004 Device 002: ID 0b05:180d ASUSTek Computer, Inc. STRIX SOUND CARD

         Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

         Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

     

    under this Controller is the soundcard listet so I took the hole. I know that it has to be this Controller since there is also a driver for this to reduce lag. Which I installed succesfully but the main driver does not work.

     

    I hope someone can help me.

     

    Sorry for bad english I am not a native speaker ;)

     

    System Specs:

     

    CPU I7 5820K @3.3GHz

    Mainboard Asus X99-A

    GPU Asus GTX 670

    RAM 16gig