95birdman@gmail.com

Members
  • Posts

    4
  • Joined

  • Last visited

95birdman@gmail.com's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I'm trying to modify my new Wireguard endpoint. I'm in the wg0.conf file, and see what I need to change, but not sure of what exactly I should be changing and what my options are? If I wanted a Toronto server, do I change amsterdam to toronto, or do I need an entirely new server address? If so, where do I find a list of available wireguard servers for this? EDIT: I found out how. I just looked at my old list of OpenVPN servers such as ca-toronto and uk-london and changed nl-amsterdam to ca-vancouver for example in my /appdata/binhex-delugevpn/wireguard/wg0.conf file. Huge increase in speed!
  2. My Deluge is set to 192.168.1.2. I have tried br0, set the Fixed IP to 192.168.1.2. (i like to keep the IP fixed so I don't need to change bookmarks and Sonarr/Radarr). LAN_Network is usually blank, but I have also tried putting in 192.168.1.2. However, that's only one step I've tried. By default settings (and following SpaceInvaderOne's exact video on this), I can't get it to work. Why does br0 not work? I really don't understand that far. It doesn't work on Bridge either, so what's the concept at work here that causes the disconnect? ELI5 please because Linux/unRaid and this type of networking is not my expertise. Why can I not use br0? That's what my other containers are set to, and work fine. Why does it not work on default Bridge settings? EDIT: What the ####!? I just tried going back to Bridge again, and now my WebUI works. I swear I have been back and forth with so many settings, Bridge, Host, br0, different LAN_Network settings, different vpn settings, different .ovpn files, you name it. Every "fix" I've read here, I've tried. I changed nothing but turning Bridge back on while changing nothing else (same settings I had before while attempting Bridge) and now the WebUI works. This makes it even worse because I have NO idea what the difference was that caused the fix.
  3. As stated, I've tried Bridge, but it doesn't change anything. LAN_Network has been tried in many formats. including 192.168.1.0/24, blank, and matching IP i set to as br0. I use br0 on everything, including DelugeVPN at the moment, everything works until I try enabling the VPN, but like I said, even on Bridge, WebUI will not load.
  4. I've been through what seems like every solution on here. I'm very new to unRaid and have a mild knowledge of networking, so please ELI5 if you can. I cannot get the WebUI to load with VPN_ENABLED. I'm using PIA with the proper credentials. I've copied over the correct cert files and tried multiple region .ovpn files, including confirmed port forwarding locations. Logs show nothing alarming, it says WebUI started, but when I try to load the WebUI, it just never connects to it. I'm on br0 mode, locked the IP, but have tried different IP configurations, including Bridge. I've deleted and started over from scratch. I've deleted web.conf and had it rebuild. Nothing. "This site cannot be reached." WebUI loads fine with the VPN off. Can anyone please help? 2020-04-17 15:09:06,098 DEBG 'start-script' stdout output: [info] OpenVPN started Fri Apr 17 15:09:06 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2020-04-17 15:09:06,099 DEBG 'start-script' stdout output: Fri Apr 17 15:09:06 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]199.229.249.155:1198 Fri Apr 17 15:09:06 2020 UDP link local: (not bound) 2020-04-17 15:09:06,100 DEBG 'start-script' stdout output: Fri Apr 17 15:09:06 2020 UDP link remote: [AF_INET]199.229.249.155:1198 2020-04-17 15:09:06,388 DEBG 'start-script' stdout output: Fri Apr 17 15:09:06 2020 [f49e79fd4f438f94880236dbe4d0a5e4] Peer Connection Initiated with [AF_INET]199.229.249.155:1198 2020-04-17 15:09:07,586 DEBG 'start-script' stdout output: Fri Apr 17 15:09:07 2020 TUN/TAP device tun0 opened Fri Apr 17 15:09:07 2020 /usr/bin/ip link set dev tun0 up mtu 1500 2020-04-17 15:09:07,587 DEBG 'start-script' stdout output: Fri Apr 17 15:09:07 2020 /usr/bin/ip addr add dev tun0 local 10.44.10.6 peer 10.44.10.5 2020-04-17 15:09:07,588 DEBG 'start-script' stdout output: Fri Apr 17 15:09:07 2020 /root/openvpnup.sh tun0 1500 1558 10.44.10.6 10.44.10.5 init 2020-04-17 15:09:07,590 DEBG 'start-script' stdout output: [debug] Waiting for valid IP address from tunnel... 2020-04-17 15:09:07,597 DEBG 'start-script' stdout output: Fri Apr 17 15:09:07 2020 Initialization Sequence Completed 2020-04-17 15:09:07,701 DEBG 'start-script' stdout output: [debug] Valid IP address from tunnel acquired '10.44.10.6' 2020-04-17 15:09:07,702 DEBG 'start-script' stdout output: [info] Port forwarding is enabled [info] Checking endpoint 'ca-montreal.privateinternetaccess.com' is port forward enabled... 2020-04-17 15:09:07,705 DEBG 'start-script' stdout output: [info] Attempting to curl https://www.privateinternetaccess.com/vpninfo/servers?version=82... 2020-04-17 15:09:08,309 DEBG 'start-script' stdout output: [info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200 2020-04-17 15:09:08,366 DEBG 'start-script' stdout output: [info] PIA endpoint 'ca-montreal.privateinternetaccess.com' is in the list of endpoints that support port forwarding 2020-04-17 15:09:08,367 DEBG 'start-script' stdout output: [info] List of PIA endpoints that support port forwarding:- [info] ca-montreal.privateinternetaccess.com [info] ca-vancouver.privateinternetaccess.com [info] de-berlin.privateinternetaccess.com [info] de-frankfurt.privateinternetaccess.com [info] sweden.privateinternetaccess.com [info] swiss.privateinternetaccess.com [info] france.privateinternetaccess.com [info] czech.privateinternetaccess.com [info] spain.privateinternetaccess.com [info] ro.privateinternetaccess.com [info] israel.privateinternetaccess.com [info] Attempting to get dynamically assigned port... 2020-04-17 15:09:08,371 DEBG 'start-script' stdout output: [info] Attempting to curl http://209.222.18.222:2000/?client_id=c17ecb588136bdfca3053ae66d423197b80c518f5c260a69249a2cdefceeaed5... 2020-04-17 15:09:08,863 DEBG 'start-script' stdout output: [info] Curl successful for http://209.222.18.222:2000/?client_id=c17ecb588136bdfca3053ae66d423197b80c518f5c260a69249a2cdefceeaed5, response code 200 2020-04-17 15:09:08,890 DEBG 'start-script' stdout output: [info] Successfully assigned incoming port 42792 2020-04-17 15:09:08,891 DEBG 'start-script' stdout output: [info] Checking we can resolve name 'www.google.com' to address... 2020-04-17 15:09:08,960 DEBG 'start-script' stdout output: [info] DNS operational, we can resolve name 'www.google.com' to address '172.217.164.228' 2020-04-17 15:09:08,961 DEBG 'start-script' stdout output: [info] Attempting to get external IP using Name Server 'ns1.google.com'... 2020-04-17 15:09:09,463 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address 199.229.249.155 2020-04-17 15:09:09,726 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2020-04-17 15:09:09,732 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place [info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.44.10.6 different, marking for reconfigure 2020-04-17 15:09:09,736 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2020-04-17 15:09:09,741 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running 2020-04-17 15:09:09,741 DEBG 'watchdog-script' stdout output: [info] Deluge incoming port 6890 and VPN incoming port 42792 different, marking for reconfigure 2020-04-17 15:09:09,741 DEBG 'watchdog-script' stdout output: [info] Attempting to start Deluge... [info] Removing deluge pid file (if it exists)... 2020-04-17 15:09:10,000 DEBG 'watchdog-script' stdout output: [info] Deluge key 'listen_interface' currently has a value of '10.1.10.6' [info] Deluge key 'listen_interface' will have a new value '10.44.10.6' [info] Writing changes to Deluge config file '/config/core.conf'... 2020-04-17 15:09:10,135 DEBG 'watchdog-script' stdout output: [info] Deluge key 'outgoing_interface' currently has a value of 'tun0' [info] Deluge key 'outgoing_interface' will have a new value 'tun0' [info] Writing changes to Deluge config file '/config/core.conf'... 2020-04-17 15:09:10,258 DEBG 'watchdog-script' stdout output: [info] Deluge key 'default_daemon' currently has a value of 'bef87a7dd78145fe9fc4d12332d989d3' [info] Deluge key 'default_daemon' will have a new value 'bef87a7dd78145fe9fc4d12332d989d3' [info] Writing changes to Deluge config file '/config/web.conf'... 2020-04-17 15:09:10,482 DEBG 'watchdog-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2020-04-17 15:09:10,693 DEBG 'watchdog-script' stdout output: [info] Deluge process listening on port 58846 2020-04-17 15:09:12,410 DEBG 'watchdog-script' stdout output: Setting "random_port" to: False Configuration value successfully updated. 2020-04-17 15:09:14,199 DEBG 'watchdog-script' stdout output: Setting "listen_ports" to: (42792, 42792) Configuration value successfully updated. 2020-04-17 15:09:15,758 DEBG 'watchdog-script' stdout output: [info] No torrents with state 'Error' found 2020-04-17 15:09:15,758 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... [info] Deluge Web UI started 2020-04-17 15:09:15,758 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 42792 [debug] Deluge incoming port is 42792 [debug] VPN IP is 10.44.10.6 [debug] Deluge IP is 10.44.10.6 2020-04-17 15:09:45,762 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2020-04-17 15:09:45,768 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2020-04-17 15:09:45,778 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 42792 [debug] Deluge incoming port is 42792 [debug] VPN IP is 10.44.10.6 [debug] Deluge IP is 10.44.10.6 2020-04-17 15:10:15,782 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2020-04-17 15:10:15,788 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2020-04-17 15:10:15,797 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 42792 [debug] Deluge incoming port is 42792 [debug] VPN IP is 10.44.10.6 [debug] Deluge IP is 10.44.10.6 2020-04-17 15:10:45,802 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2020-04-17 15:10:45,808 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2020-04-17 15:10:45,817 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 42792 [debug] Deluge incoming port is 42792 [debug] VPN IP is 10.44.10.6 [debug] Deluge IP is 10.44.10.6 2020-04-17 15:11:15,822 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2020-04-17 15:11:15,828 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2020-04-17 15:11:15,837 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 42792 [debug] Deluge incoming port is 42792 [debug] VPN IP is 10.44.10.6 [debug] Deluge IP is 10.44.10.6 2020-04-17 15:11:45,842 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2020-04-17 15:11:45,848 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2020-04-17 15:11:45,857 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 42792 [debug] Deluge incoming port is 42792 [debug] VPN IP is 10.44.10.6 [debug] Deluge IP is 10.44.10.6