I have my LAN Network set to: 192.168.2.0/24 and Network Type set to: Bridge not any of the others, tried then just for shits and giggles and they give errors. My LAN on 192.168.2.1 as the first IP and 192.168.2.254 as the last IP. AKA 192.168.2.1 with a Subnet of 255.255.255.0

I'm sorry for doubting you. You are right! The Dallas A02 exit node was broken!! I changed it to the Atlanta-a01 exit node and It says I have a VPN IP and a Deluge IP but I still can't access the WebUI. And this time when I try to go to the Proxy port it says "Invalid header received from client." instead of "This site can’t be reached ERR_CONNECTION_REFUSED"! Things are getting better! Here is my supervisord.log again.
Hopefully it's the last time. Your AWESOME! Thank you for your help!
supervisord.log

OK, I fixed the UMASK and deleted all the files in the APPS folder and started again. I get to Sun Feb 24 19:32:55 2019 Initialization Sequence Completed but still the webui and proxy is not accessible. Here is the new supervisord.log. The tunnel appears to be transmitting traffic when I ping in the container's bash the tun5 packets go up. This has me confused.
Starting to think I need to create a PFSense router and go that route but really would rather just use this docker if possible. I think I got my username and password fully out of this file...I hope....
Thank you for your help and time on this.
supervisord.log

Here is a new supervisord.log. Please help. I ping things in the container and the TX and RX of the tunnel increase so the tunnel is working. Just something isn't working. No idea what.
supervisord.log

Hello, Been trying to get this to work for a while. I bash in to the container and the VPN is working but Deluge is not accessible. I need a new set of eyes on it. There is so much information I cannot parse it all. Thank you.
supervisord.log

Interesting...My NIC is on-board 4 port Intel NIC. Not sure where to start to look in to that. What would cause such a thing? Think it's the class 6 bonding? I noticed every once and a while it would say that ETH0 was down.

My server was running performing great. I have been moving alot of files one disk at a time to update my movie library to be compatible with Radarr. My server went in to the weekly parity check while I was working so I quit and went to bed. This morning my dockers were failing. They can't access the App Data share. So I started to investigate and found that the Shares menu on unRAID is empty. I sshed in to the server and did an MC and sure enough /mnt/user is red and in accessible. I've added 3.7k to the Radarr library over the last couple days. Which means I've moved 3.7K of foles to a new folder to make the media compatible with Radarr. All the data is still on my /mnt/cache and my /mnt/diskN. Ironically, /mnt/user0 works fine. Here is my diagnostics file. I can't reboot or anything as my Parity Check is only 88% complete. This has never happened before in the 4.6 years I've been using unRAID. Even the initial data copy, 16TB, never gave me a problem. Any help is appreciated. Thank you for your time.
rudder2-server-diagnostics-20190208-0852.zip

Are you running a windows 10 VM with GPU Passthrew? If so, I had this problem going from 5.6.0 to 6.6.0 threw 6.6.6 and it was Windows 10 VM that was at fault. Here is my bug report and what I did to fix it.