Jump to content

watsoma

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by watsoma

  1. Thanks Binhex - BT were in fact hijacking the DNS.

     

    I set the DNS in both unRaid and at the router to use Google and it worked a treat :)  

     

    One thing of note for any other users who have a similar issue; if you use a BT Hub 4 (like I have), then you can't override the DNS settings. You will need to either use a dynamic DNS site or use another router which will allow you to configure the DNS. You will also need to turn off all the BT Parental controls on your BT account to get this working. If you have a BT Hub 5, i believe you can override the DNS......

     

    Luckily, I have a spare Netgear router so all working now.

     

    Many thanks for the speedy responses  :)

  2. 31 minutes ago, binhex said:

     

    it looks like you have dns hijacking going on (prbably your ISP), here is name resolution output from your log:-

     

     

    and here is what it should look like:-

     

     

    notice the ip's returned is significantly shorter, i think you will find the two ip's your seeing listed are most probably your ISP's name servers. 

     

    confirmed ip address 213.120.234.114 is owned by BT.

     

    so you can try switching your dns from BT to say google, you will need to do this for unraid (if defined) and on your router.

     

    Thanks - I'll give this a shot and see if that resolves it.

  3. Just now, mr-hexen said:

     

    Ya nothing is jumping out from the logs for me either...do you have any special characters or spaces in your username / password?

     

    The log's saying using previous IP, never seen that message before.

     

    The username is standard from PIA (i.e. P followed by 7 numbers) and the password just contains standard A-Z (mixed case) and 0-9. I had noted that special characters can sometimes cause issues so I avoided them....

  4. 4 minutes ago, binhex said:

    @watsoma if you have set your LAN_NETWORK to 192.168.1.254, which is kinda implied by your quote below, then this is incorrect, click on link in my sig to vpn docker faq, its in there as to how to identify and set it correctly.

     

     

    sorry, I should have clarified :

     

    The router sits at 192.168.1.254 and the UnRaid server is static at 192.168.1.75. The netmask according to the ifconfig from UnRaid is 255.255.255.0 so I have the LAN_NETWORK set to 192.168.1.0/24.

  5. I am relatively new to UnRaid and Binhex's wonderful DelugeVPN but I am experiencing a problem which has left me stumped but I just know it's going to be a simple fix !

     

    I have Binhex's Deluge VPN set-up on UnRaid 6.3.2 and when I try and start the WebUI it comes up with a "page not found" message. If I set the VPN_ENABLED=NO it works fine. All indications suggest a problem with my PIA user / password but I have triple checked these and they are fine.

     

    I have checked my default gateway, which sits at 192.168.1.254 so the LAN_NETWORK looks ok, so I am stumped for now......the logs show it seems to be stuck with :

     

    2017-03-10 09:49:44,091 DEBG 'start-script' stdout output:
    [debug] Waiting for valid IP address from tunnel...

    Fri Mar 10 09:49:44 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]213.120.234.114:1198
    Fri Mar 10 09:49:44 2017 UDP link local: (not bound)
    Fri Mar 10 09:49:44 2017 UDP link remote: [AF_INET]213.120.234.114:1198

     

    The deployed ports shows :

    deployed host ports ...
      crashplan4242 4243 4280 4239
      plexmediaserver
      netdata
      binhex-delugevpn8112 58846 58946 58946 8118

     

    I have attached logs and hope that someone can point out the glaring obvious mistake I have made :)

     

    Cheers!

    delugevpn-log.txt

    ifconfig.txt

    Supervisord.log.txt

×
×
  • Create New...