Jump to content

strike

Members
  • Posts

    776
  • Joined

  • Last visited

Posts posted by strike

  1. 3 hours ago, WalkerJ said:

    The symptom is the VPN can't connect because of "possible DNS issues"

    Yeah, that's not the same issue as the rest is having. The rest is having a successful start as far I can see. If your log states that you have possible DNS issues you should change your nameservers in the container template to something else, like maybe 1.1.1.1,8.8.8.8. PIA users have had this issue on/off for some time. So if you're a PIA user changing your nameservers is worth a shot. 

     

    For you other guys/future posters reading this it will probably take some time to debug. So please enable debug logs and post them along with your diagnostics as well. Also write if your're using zerotier/Tailscale as that maybe could be a factor.

    • Like 1
  2. 3 hours ago, gcalabro said:

    Found these in the log:

    Unless you're outside your LAN that's not your issue. That error would have been there before 6.12 too.

    Edit: Actually with the new unraid version and the changes to networking maybe deluge thinks your outside your LAN. Are you running zerotier or Tailscale by any chance? 

  3. 3 minutes ago, gcalabro said:

    Switched to bridge and it didn’t work. It seems the application is functioning, however. It’s only access to the web UI that seems to be broken.

    Hmm.. Could be something related to the new unraid update then. I've seen a few people mention various network issues in other threads. But then more people should have reported issues here I think. Post a new log with bridge enabled please. 

  4. So after almost 10 years using medusa I switched over to sonarr as medusa was becoming painfully slow. 1 thing I'm missing tho is what's called scene exceptions in medusa. This is a feature where you can add another name to the show than what it's called when your're pulling it from tvdb or whatever indexer. Sometimes the show is released with another name, as an example I'm using the the show "The Idol 2023". On the tracker I'm using the show is released as "The Idol US" or "The Idol". But since the show is called The Idol 2023 in sonarr it doesn't find any episodes. So how do I solve this in sonarr?

  5. 22 minutes ago, mike_walker said:

    PS If there are any other ideas why the Virgin dl rate is so bad I'd love to hear.  I've not changed anything in the deluge preferences so pretty sure that isn't the issue (and I followed the guidance on limiting the ul speeds etc..).

    The number one reason for low speed is not having an open incoming port. Have you set that up with your vpn provider and put that port in the deluge settings?

  6. 1 minute ago, Gex2501 said:

    I'm not using labels...just want to try a nicer UI. Is there something special about the binhex-delugevpn that doesn't work with Flood? Do I need some special config?

    No, nothing special. I've just tried it for a few min tho. It was as I said useless to me as it doesn't support labels. 

  7. On 3/25/2023 at 1:14 AM, johnzimm said:

    I think this is a simple fix, but before I go messing things up... I am using a new router and it gave Unraid a new IP. I can connect to the Unraid web UI but I can not connect to the binhex-delugevpn web UI. Is there something I should change? Thank you

    You're right, change LAN_NETWORK to 192.168.3.0/24

  8. 1 hour ago, FrozenGamer said:

    would using windows machine to extract and copy those files vs terminal cause any problems with the install in appdata? 

    That depends, winrar in windows does not copy symlinks for example. And I don't know if it preserves permissions either. Best way to do it is via the CLI. It's super simple and faster. 

  9. 48 minutes ago, binhex said:

    keep in mind also, even if somebody was able to get onto the container (a feat in itself) they would not be running as root and therefore would not be able to change iptables and would have a VERY restrictive view of your lan (defined via VPN_OUTPUT_PORTS), connecting to SMB/NFS would most definitely not be possible - just thought i would send you the warm and fuzzies so you sleep better at night 🙂

    Haha :P I do feel a bit warmer and fuzzier now that you mention it. But this is the container I trust the most so I wasn't really worried about that. If it weren't for all my other containers  running on br0 with a separate IP I would run this container in bridge so I could reverse proxy it. But I can live with just the thin client, it works well.

  10. 1 hour ago, headnoodle said:

    Ah so not only did I miss it, the question was only asked in the last month   So from the thread it seems like I cannot have a custom IP unless I forgo the web client and use a thin client instead.  Not a big issue, it just upsets my ocd as I like to have each of my docker instances on a separate IP so I can assign an internal DNS entry for them to look prettier  

    Yeah, I like to have most of my containers on a separate IP as well, for security reasons for the most part. As they are then isolated from the host. So I'm using the thin client for deluge. The only thing I miss that I can't get from the thin client, is to set up a reverse proxy. 

  11. 5 minutes ago, binhex said:

    its working here for me too, but im seeing a few people posting on my github repo about problems with the new image, so there looks to be something going on, no idea what yet, and as i mentioned i cannot replicate it yet. i suspect iptable module issue at present, link to issue:-

    https://github.com/binhex/arch-delugevpn/issues/352

    Good to know, I'll be watching this issue. If they all have airvpn I might know what the solution is. @Lamkam is using airvpn I can see from the little log snippet. I'll ask on the github issue if they can confirm which provider they're using.

    • Thanks 1
  12. 1 hour ago, Lamkam said:

    Since last image update of today, it's failing. Looks like its looping and restarting constantly. Logs do not show anything useful.

     

    Havent changed any settings or anything since ages for this container, and was always working fine. Any ideas?

     

    Created by...
    ___.   .__       .__
    \_ |__ |__| ____ |  |__   ____ ___  ___
     | __ \|  |/    \|  |  \_/ __ \\  \/  /
     | \_\ \  |   |  \   Y  \  ___/ >    <
     |___  /__|___|  /___|  /\___  >__/\_ \
         \/        \/     \/     \/      \/
      https://hub.docker.com/u/binhex/
    2023-02-14 18:51:34.371998 [info] System information Linux 4bd397d513e9 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 GNU/Linux
    2023-02-14 18:51:34.395934 [info] OS_ARCH defined as 'x86-64'
    2023-02-14 18:51:34.416313 [info] PUID defined as '1000'
    2023-02-14 18:51:34.443650 [info] PGID defined as '1000'
    2023-02-14 18:51:34.479826 [info] UMASK defined as '000'
    2023-02-14 18:51:34.500000 [info] Permissions already set for '/config'
    2023-02-14 18:51:34.524385 [info] Deleting files in /tmp (non recursive)...
    2023-02-14 18:51:34.550638 [info] VPN_ENABLED defined as 'yes'
    2023-02-14 18:51:34.572721 [info] VPN_CLIENT defined as 'openvpn'
    2023-02-14 18:51:34.597115 [info] VPN_PROV defined as 'airvpn'
    2023-02-14 18:51:34.623935 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/AirVPN_Netherlands_UDP-443.ovpn
    2023-02-14 18:51:34.676341 [info] VPN remote server(s) defined as 'nl.vpn.airdns.org,'
    2023-02-14 18:51:34.693537 [info] VPN remote port(s) defined as '443,'
    2023-02-14 18:51:34.711049 [info] VPN remote protcol(s) defined as 'udp,'
    2023-02-14 18:51:34.736628 [info] VPN_DEVICE_TYPE defined as 'tun0'
    2023-02-14 18:51:34.757510 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
    2023-02-14 18:51:34.901110 [debug] DNS operational, we can resolve name 'nl.vpn.airdns.org' to address '213.152.162.148'
    Created by...
    ___.   .__       .__
    \_ |__ |__| ____ |  |__   ____ ___  ___
     | __ \|  |/    \|  |  \_/ __ \\  \/  /
     | \_\ \  |   |  \   Y  \  ___/ >    <
     |___  /__|___|  /___|  /\___  >__/\_ \
         \/        \/     \/     \/      \/
      https://hub.docker.com/u/binhex/
    2023-02-14 18:52:35.278009 [info] System information Linux 4bd397d513e9 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 GNU/Linux
    2023-02-14 18:52:35.302738 [info] OS_ARCH defined as 'x86-64'
    2023-02-14 18:52:35.323116 [info] PUID defined as '1000'
    2023-02-14 18:52:35.349231 [info] PGID defined as '1000'
    2023-02-14 18:52:35.385817 [info] UMASK defined as '000'
    2023-02-14 18:52:35.410273 [info] Permissions already set for '/config'
    2023-02-14 18:52:35.430875 [info] Deleting files in /tmp (non recursive)...
    2023-02-14 18:52:35.459583 [info] VPN_ENABLED defined as 'yes'
    2023-02-14 18:52:35.485748 [info] VPN_CLIENT defined as 'openvpn'
    2023-02-14 18:52:35.509858 [info] VPN_PROV defined as 'airvpn'
    2023-02-14 18:52:35.535714 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/AirVPN_Netherlands_UDP-443.ovpn
    2023-02-14 18:52:35.585318 [info] VPN remote server(s) defined as 'nl.vpn.airdns.org,'
    2023-02-14 18:52:35.610432 [info] VPN remote port(s) defined as '443,'
    2023-02-14 18:52:35.628152 [info] VPN remote protcol(s) defined as 'udp,'
    2023-02-14 18:52:35.653142 [info] VPN_DEVICE_TYPE defined as 'tun0'
    2023-02-14 18:52:35.673416 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
    2023-02-14 18:52:35.715358 [debug] DNS operational, we can resolve name 'nl.vpn.airdns.org' to address '213.152.161.68'

    Last image is working fine here. Do this: https://github.com/binhex/documentation/blob/master/docker/faq/help.md

  13. 7 hours ago, headnoodle said:

    Not sure if this has been asked before but cannot find it when searching the thread, so apologies up front if it is there an I missed it.

     

    I have installed the docker instance of this in unraid and all works fine with the vpn file entered etc.  My problem is that when I change the docker instance to use a fixed IP address it doesn't allow me to load the page.  It looks find based on the logs, nothing untoward listed.  If I turn of vpn then it works fine on the fixed IP

     

    Any help would be appreciated...... :)

    https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=1223362

     

  14. Just now, jontron said:

    I just looked through the logs and it's a permissions issue. I'll start looking around to see if someone has already found the fix. Thanks!

    Ok, Yeah a lot of users had permission issues when updating to 6.11 due to not using the correct setup. If you have the arrs running on another uid/gid other then 99/100 you need to change it back to the standard 99/100. And make sure the right permission are set in the settings of the arrs. After doing that you might need to run the new (docker safe) perms script found under tools in the unraid webui on you shares to fix permission issues.  

  15. 8 minutes ago, jontron said:

    So deluge is good. But just checked my arrs that are routing through it and they aren't visible

    You mean you can't get to the webui of the arrs? Has it been a while since you updated delugevpn? There was some changes some time ago when routing other apps through a vpn app. Do you have your input and output ports setup according to the faq Q25 and Q27? https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

×
×
  • Create New...