Biloxi_1
-
Posts
18 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Biloxi_1
-
-
6 minutes ago, binhex said:
looking at your log i would say your vpn provider is having issues:-
Fri Jun 7 07:17:14 2019 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)try a different endpoint, or contact your vpn provider and tell them you are having TLS key negotiation failing.
Thank you for your response. I did try a different end point, and received the same results. I noticed while troubleshooting that if I swap the network type in the settings from "bridge" to "custom: br0" the torrents will start downloading, but I i cannot reach webui in that configuration.
-
Hey guys, I'm having what I think is a networking issue. I had everything up and running fine for a long time, however I was troubleshooting an unrelated vm issue last week, and I think I mucked up a network setting somewhere. I can get my container to start, and connect to my vpn provider, but nothing will download, and all the trackers timeout. In the console I can see the connection, but I cannot ping anything outside of my network. My other containers seem to be functioning normally. Any thoughts? I am probably missing something super obvious.
-
10 minutes ago, itimpi said:
You could probably solve this in two ways without passing through the NIC:
- Install the 'vfio' network drivers inside the Ubuntu VM. They should be on the vfio CD image that you probably already have attached to the VM.
- Change the 'model' of the network card in the VM XML to something for which VM Ubuntu already has drivers. Something like 'e1000' is likely to work. To make this change to the VM settings you have to make the edit in XML mode.
I have used both approaches on different VMs when using 'br0' as the network connection without passing through a network card (my hardware does not support pass-through).
Changing the model to e1000 did the trick. Thank you for your assistance!
-
1
-
This is super helpful! Thank you so much! Unfortunately my NIC is not in it's own IOMMU group, and I don't want to blacklist it, because it is the NIC for the whole machine. I'm gonna see if I can borrow an additional NIC and get this working.
-
Thank you for your response. I am unsure how to do either of those things. I attempted to set the vm to emulate another type of network card, but it keeps giving me an error when I try to start it. I don't think I have the correct syntax. I have attached a screenie of an lspci command. Is that where I should be looking for supported nics?
-
Hello, I am attempting to run this VM in KVM. I can get the machine to boot up, however I cannot get it attached to my network via dhcp or statically. When i do an "ifconfig -a" the only interface that shows up is "lo", and if I try to manually enable an interface, it gives me the following error: ERROR while getting interface flags: No such device. Any help would be appreciated.
-
Hey again, I'm still struggling with this. I was reading the below forum post where you helped another guy, and I am having the exact same problem. I tried the steps that you outlined in the post changing the options to what I thought were correct. How do you figure out which options should be selected? I am trying to get this to run https://sourceforge.net/projects/metasploitable/files/Metasploitable2/ I have setup the VM with Ubuntu and just general linux and tried various combinations of BIOSs and vdisk modes. Any input you could provide would be much appreciated.
-
Yes, I meant vmdk. Thank you for correcting me. This has gotten me further along, Now when I start the VM it just drops me at a UEFI shell prompt. It is probably the driver issue that you spoke of.
-
Hello, I am trying get some virtual box VM's from vulnhub up and running on my Unraid server, and I am running into difficulty. I am running Unraid 6.6.7 and I have other VM's loaded from .iso up and working. I download the files and receive a vmdf file. I have converted them to qcow2 using qemu-ing but I am unable to get the vm manager to recognize the files. I am trying to select them from the "OS Install ISO" drop down. Is this correct? Am I missing steps? Will this work at all? Any help would be appreciated.
-
12 minutes ago, strike said:
Ok. Early on in your log you were having authentication issues possibly due to the special characters in your password. It looks fine at the end of the log though (no more authentication issues), but these things with special characters can be unpredictable. It doesn't look like you have to have an e-mail address as your login, you can have a username, but it doesn't say how to change it. If they were offering a trial period you could simply just create a new account and try with another username, but it doesn't look like that they offer that? Maybe you can contact support about changing the login?
Other than that I'm not sure what could be causing the issue. Maybe you can try a different browser if you haven't tried it. And as I mentioned earlier you can try to nuke the docker image and re-download all your containers using CA's previous apps. You don't have to configure anything and you won't lose any settings/data. If you don't know how to do it just ask
I'm not sure it will have any effect in this case, but you said it has been working for months and then suddenly it stops so it could be worth a try. Recreating the docker image has helped me more than once.
Roger. Thanks for looking at it for me. I will try to email them about the user name , and maybe redo the docker image. I'll post back here if I get it working again.
-
9 minutes ago, strike said:
And to be clear, you're not reaching the webui at all or do you reach the webui but it's blank? The warning about special characters in your password is gone, but it still complains about your username, you're sure it does not contain any special characters? Everything else seems to be ok.
I get a timeout. I do have a special character in my username, an "@" because it is an email address. Looking through my options on nord vpn I don't see where I can change it however. It was working fine for months =/
-
1 hour ago, strike said:
I can't see anything wrong in that log, but you need to post a debug log. Edit the container and set the debug variable to "true", start the container and let it run for a few min. Then post the entire suprervisord.log file (remove username/password. Also, is your unraid server IP 10.10.10.x? Do you have any special characters in your username/password? This container only supports characters 0-9, a-z,A-Z any other characters can cause issues.
Debug log attached. I do use the 10.10.10.x scheme on my network. I changed my password removing the special characters, but still no joy.
-
48 minutes ago, Biloxi_1 said:
So I went to grab logs to upload this morning and my container is working again. I didnt make any changes, so my only theory is the vpn server I was connecting to was having issues, but that seems strange, because I tried 3 separate servers. Either way it is working again. Thanks for the advice, and I will remember in the future to upload logs when seeking help.
ok, I had to restart the container because I fat fingered a file path while re-configuring and I am back where I started, I cannot log into the webui from my LAN with the vpn enabled. Here is my log, would anyone be willing to assist me in figuring this out?
Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/
2018-06-29 06:38:27.775261 [info] Host is running unRAID
2018-06-29 06:38:27.797646 [info] System information Linux c66e9c800913 4.14.13-unRAID #1 SMP PREEMPT Wed Jan 10 10:27:09 PST 2018 x86_64 GNU/Linux
2018-06-29 06:38:27.823124 [info] PUID defined as '99'
2018-06-29 06:38:28.056046 [info] PGID defined as '100'
2018-06-29 06:38:28.510192 [info] UMASK defined as '000'
2018-06-29 06:38:28.535557 [info] Permissions already set for volume mappings
2018-06-29 06:38:28.565467 [info] VPN_ENABLED defined as 'yes'
2018-06-29 06:38:28.596707 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/ca301.nordvpn.com.udp.ovpn
dos2unix: converting file /config/openvpn/ca301.nordvpn.com.udp.ovpn to Unix format...
2018-06-29 06:38:28.648026 [info] VPN remote line defined as 'remote 207.189.31.109 1194'
2018-06-29 06:38:28.674828 [info] VPN_REMOTE defined as '207.189.31.109'
2018-06-29 06:38:28.701593 [info] VPN_PORT defined as '1194'
2018-06-29 06:38:28.735308 [info] VPN_PROTOCOL defined as 'udp'
2018-06-29 06:38:28.761654 [info] VPN_DEVICE_TYPE defined as 'tun0'
2018-06-29 06:38:28.786282 [info] VPN_PROV defined as 'custom'
2018-06-29 06:38:28.812200 [info] LAN_NETWORK defined as '10.10.10.0/24'
2018-06-29 06:38:28.837771 [info] NAME_SERVERS defined as '209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4'
2018-06-29 06:38:28.863517 [info] VPN_USER defined as 'XXXXXXXX'
2018-06-29 06:38:28.888834 [info] VPN_PASS defined as 'XXXXXXXX'
2018-06-29 06:38:28.916754 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2018-06-29 06:38:28.943604 [info] ENABLE_PRIVOXY defined as 'no'
2018-06-29 06:38:28.971067 [info] Starting Supervisor...
2018-06-29 06:38:29,120 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2018-06-29 06:38:29,121 INFO Set uid to user 0 succeeded
2018-06-29 06:38:29,124 INFO supervisord started with pid 7
2018-06-29 06:38:30,126 INFO spawned: 'start-script' with pid 136
2018-06-29 06:38:30,128 INFO spawned: 'deluge-script' with pid 137
2018-06-29 06:38:30,129 INFO spawned: 'deluge-web-script' with pid 138
2018-06-29 06:38:30,129 INFO spawned: 'privoxy-script' with pid 139
2018-06-29 06:38:30,130 INFO reaped unknown pid 8
2018-06-29 06:38:30,133 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN
2018-06-29 06:38:30,133 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-06-29 06:38:30,133 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-06-29 06:38:30,133 INFO success: deluge-web-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-06-29 06:38:30,133 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-06-29 06:38:30,135 DEBG 'deluge-script' stdout output:
[info] Deluge config file already exists, skipping copy
2018-06-29 06:38:30,136 DEBG 'deluge-script' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid
2018-06-29 06:38:30,136 DEBG 'privoxy-script' stdout output:
[info] Privoxy set to disabled
2018-06-29 06:38:30,136 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 23423994509144 for <Subprocess at 23423997082656 with name privoxy-script in state RUNNING> (stderr)>
2018-06-29 06:38:30,136 DEBG fd 22 closed, stopped monitoring <POutputDispatcher at 23423994508712 for <Subprocess at 23423997082656 with name privoxy-script in state RUNNING> (stdout)>
2018-06-29 06:38:30,136 INFO exited: privoxy-script (exit status 0; expected)
2018-06-29 06:38:30,137 DEBG received SIGCLD indicating a child quit
2018-06-29 06:38:30,139 DEBG 'start-script' stdout output:
[warn] Username contains characters which could cause authentication issues, please consider changing this if possible
2018-06-29 06:38:30,143 DEBG 'start-script' stdout output:
[warn] Password contains characters which could cause authentication issues, please consider changing this if possible
2018-06-29 06:38:30,220 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1
2018-06-29 06:38:30,223 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf
2018-06-29 06:38:30,226 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf
2018-06-29 06:38:30,229 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf
2018-06-29 06:38:30,232 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf
2018-06-29 06:38:30,234 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf
2018-06-29 06:38:30,237 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf
2018-06-29 06:38:30,239 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf
2018-06-29 06:38:30,242 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf
2018-06-29 06:38:30,246 DEBG 'start-script' stdout output:
207.189.31.109
2018-06-29 06:38:30,253 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...
2018-06-29 06:38:30,254 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.14.13-unRAID
2018-06-29 06:38:30,255 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...
2018-06-29 06:38:30,255 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'
2018-06-29 06:38:30,255 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory
2018-06-29 06:38:30,258 DEBG 'start-script' stdout output:
[info] Adding 10.10.10.0/24 as route via docker eth0
2018-06-29 06:38:30,259 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
2018-06-29 06:38:30,259 DEBG 'start-script' stdout output:
--------------------
2018-06-29 06:38:30,259 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0
10.10.10.0/24 via 172.17.0.1 dev eth0
2018-06-29 06:38:30,259 DEBG 'start-script' stdout output:
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.4
--------------------
2018-06-29 06:38:30,281 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16
2018-06-29 06:38:30,360 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------
2018-06-29 06:38:30,362 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1194 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -s 10.10.10.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1194 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -d 10.10.10.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
2018-06-29 06:38:30,362 DEBG 'start-script' stdout output:
--------------------
2018-06-29 06:38:30,363 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...
2018-06-29 06:38:30,382 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 WARNING: file 'credentials.conf' is group or others accessible
Fri Jun 29 06:38:30 2018 OpenVPN 2.4.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Mar 1 2018
Fri Jun 29 06:38:30 2018 library versions: OpenSSL 1.1.0g 2 Nov 2017, LZO 2.10
2018-06-29 06:38:30,382 DEBG 'start-script' stdout output:
[info] OpenVPN started
2018-06-29 06:38:30,383 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 WARNING: --ping should normally be used with --ping-restart or --ping-exit
Fri Jun 29 06:38:30 2018 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Fri Jun 29 06:38:30 2018 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Fri Jun 29 06:38:30 2018 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
2018-06-29 06:38:30,383 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]207.189.31.109:1194
Fri Jun 29 06:38:30 2018 Socket Buffers: R=[212992->212992] S=[212992->212992]
Fri Jun 29 06:38:30 2018 UDP link local: (not bound)
Fri Jun 29 06:38:30 2018 UDP link remote: [AF_INET]207.189.31.109:1194
2018-06-29 06:38:30,469 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 TLS: Initial packet from [AF_INET]207.189.31.109:1194, sid=f931ff2c 29853a57
2018-06-29 06:38:30,559 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA
2018-06-29 06:38:30,560 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 VERIFY OK: depth=1, C=PA, O=NordVPN, CN=NordVPN CA2
2018-06-29 06:38:30,560 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 VERIFY KU OK
Fri Jun 29 06:38:30 2018 Validating certificate extended key usage
Fri Jun 29 06:38:30 2018 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2018-06-29 06:38:30,560 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 VERIFY EKU OK
Fri Jun 29 06:38:30 2018 VERIFY OK: depth=0, CN=ca301.nordvpn.com
2018-06-29 06:38:30,915 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:30 2018 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Fri Jun 29 06:38:30 2018 [ca301.nordvpn.com] Peer Connection Initiated with [AF_INET]207.189.31.109:1194
2018-06-29 06:38:31,936 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:31 2018 SENT CONTROL [ca301.nordvpn.com]: 'PUSH_REQUEST' (status=1)
2018-06-29 06:38:32,021 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,sndbuf 524288,rcvbuf 524288,dhcp-option DNS 103.86.96.100,dhcp-option DNS 103.86.99.100,route-gateway 10.8.8.1,topology subnet,ping 60,ping-restart 180,ifconfig 10.8.8.68 255.255.255.0,peer-id 12,cipher AES-256-GCM'
2018-06-29 06:38:32,021 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: timers and/or timeouts modified
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
Fri Jun 29 06:38:32 2018 Socket Buffers: R=[212992->1048576] S=[212992->1048576]
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: --ifconfig/up options modified
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: route options modified
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: route-related options modified
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: peer-id set
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: adjusting link_mtu to 1657
Fri Jun 29 06:38:32 2018 OPTIONS IMPORT: data channel crypto options modified
Fri Jun 29 06:38:32 2018 Data Channel: using negotiated cipher 'AES-256-GCM'
Fri Jun 29 06:38:32 2018 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Jun 29 06:38:32 2018 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Jun 29 06:38:32 2018 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:11:00:04
2018-06-29 06:38:32,022 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 TUN/TAP device tun0 opened
Fri Jun 29 06:38:32 2018 TUN/TAP TX queue length set to 100
2018-06-29 06:38:32,022 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Fri Jun 29 06:38:32 2018 /usr/bin/ip link set dev tun0 up mtu 1500
2018-06-29 06:38:32,023 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 /usr/bin/ip addr add dev tun0 10.8.8.68/24 broadcast 10.8.8.255
2018-06-29 06:38:32,025 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 /root/openvpnup.sh tun0 1500 1585 10.8.8.68 255.255.255.0 init
2018-06-29 06:38:32,028 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 /usr/bin/ip route add 207.189.31.109/32 via 172.17.0.1
2018-06-29 06:38:32,029 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 /usr/bin/ip route add 0.0.0.0/1 via 10.8.8.1
2018-06-29 06:38:32,030 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 /usr/bin/ip route add 128.0.0.0/1 via 10.8.8.1
2018-06-29 06:38:32,031 DEBG 'start-script' stdout output:
Fri Jun 29 06:38:32 2018 Initialization Sequence Completed
2018-06-29 06:38:32,137 DEBG 'deluge-script' stdout output:
[info] Deluge not running
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.8.8.68 different, marking for reconfigure
2018-06-29 06:38:32,138 DEBG 'deluge-script' stdout output:
[info] Attempting to start Deluge...
2018-06-29 06:38:32,258 DEBG 'deluge-script' stdout output:
[info] Deluge listening interface currently defined as 10.8.8.68
[info] Deluge listening interface will be changed to 10.8.8.68
[info] Saving changes to Deluge config file /config/core.conf...
2018-06-29 06:38:32,384 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 207.189.31.109
2018-06-29 06:38:32,384 DEBG 'deluge-script' stdout output:
[info] Deluge started
2018-06-29 06:38:32,670 DEBG 'deluge-web-script' stdout output:
[info] Starting Deluge webui... -
2 hours ago, strike said:
@Biloxi_1 , @eb3k Have any of you tried nuking the docker image and re-download all your containers? This can solve many weird issues, so if you haven't tried it you might wanna give it a go. With CA's previous apps you'll be up and running as it was in about 3 min. If this doesn't work you'll have to post full debug logs which I can't see either of you have done. Without logs you most definitely won't get any help.
So I went to grab logs to upload this morning and my container is working again. I didnt make any changes, so my only theory is the vpn server I was connecting to was having issues, but that seems strange, because I tried 3 separate servers. Either way it is working again. Thanks for the advice, and I will remember in the future to upload logs when seeking help.
-
On 6/21/2018 at 4:20 PM, eb3k said:
Just recently my Deluge Web UI stopped working. It loads a page, but it is totally blank. I have made no configuration changes to my unRAID system since the last time it worked. I was assuming it was a hiccup with an update to the docker, but since there wasn't a replacement I figured I must be the only one experiencing the issue. I have restarted the image, I have reinstalled the docker, I have tried stopping all other dockers. None of these has changed the behavior. I don't see any warnings/errors in the log. I'm sort of at a loss at this point since it was working fine one day and not the next with no changes on my part except standard updates. Does anyone have any ideas of other things to try? What do you need from me to help find the issue?
Thanks
*Edit*
The Daemon seems fine as I can access it with my desktop client. It is just the web UI, all other functions appear to be working.
I seem to be having this issue also. Container ran fine for months, then just quit working. I restarted, downloaded new config files from nord, and even deleted the whole container and started over. log shows it is pulling an ip from the vpn server and that webui is starting, but I still cannot reach the UI. When I shut off the vpn function in the config, the UI works fine.
I'm not sure it will have any effect in this case, but you said it has been working for months and then suddenly it stops so it could be worth a try. Recreating the docker image has helped me more than once.
[Support] binhex - DelugeVPN
in Docker Containers
Posted
OK, I have it set up like this, but I cannot reach the webui via 192.168.1.2:8112 nor (unraid ip)192.168.1.100:8112. I am attaching pics of it in bridge and custom configurations for a sanity check.
