- DELUGE CLIENT NOT GETTING INTERNET UPDATE
- DELUGE CLIENT NOT GETTING INTERNET CODE
- DELUGE CLIENT NOT GETTING INTERNET DOWNLOAD
DELUGE CLIENT NOT GETTING INTERNET CODE
In the console, go to the Source Code folder you just uploaded in the plugins directory which will most likely be in /config/plugins. Now go to the webGUI of your unRAID server, click on the Docker tab, click on the icon of the delugevpn container and open the Console. mnt/user/appdata/binhex-delugevpn/plugins on your unRAID server. Extract the folder and copy or scp it to the plugins folder of the delugevpn container.
DELUGE CLIENT NOT GETTING INTERNET DOWNLOAD
egg from, instead download one of the compressed Source Code files. To get the plugin working, you'll need to compile it from scratch using the python version that's used in the container. In any case that version, it's the version I'm using and it works with the ltConfig plugin. The 2.0.4 label is either a typo by the dev team or is an early beta of 2.0.4.
DELUGE CLIENT NOT GETTING INTERNET UPDATE
Working fine for months, then update and BAM, issues. Pointing to a potential cipher issue? I sorta remember having a similar issue the last time I updated the container several months back. Sat Apr 18 18:19:16 2020 WARNING: 'auth' is used inconsistently, local='auth SHA512', remote='auth ' Sat Apr 18 18:19:16 2020 WARNING: 'cipher' is used inconsistently, local='cipher AES-256-CBC', remote='cipher AES-256-GCM'
Sat Apr 18 18:19:16 2020 VERIFY OK: depth=0, C=CA, ST=ON, O=Windscribe Limited, OU=Operations, CN=Windscribe Node Server 4096 Sat Apr 18 18:19:16 2020 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Sat Apr 18 18:19:16 2020 Validating certificate extended key usage
Sat Apr 18 18:19:16 2020 WARNING: file 'nf' is group or others accessible I'm also getting this at the beginning of the log: 12:14:43,312 DEBG 'watchdog-script' stdout output:Īny ideas from anyone? I'm getting tagged for a bunch of H&R's. 12:14:43,229 DEBG 'watchdog-script' stdout output: Waiting for iptables chain policies to be in place. 12:14:43,218 DEBG 'watchdog-script' stdout output: This makes it even worse because I have NO idea what the difference was that caused the fix.Įdited Apby log is showing this on repeat, might this be a clue to the issue? 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. I swear I have been back and forth with so many settings, Bridge, Host, br0, different LAN_Network settings, different vpn settings, different. Why does it not work on default Bridge settings?ĮDIT: What the #!? I just tried going back to Bridge again, and now my WebUI works. Why can I not use br0? That's what my other containers are set to, and work fine. 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 does br0 not work? I really don't understand that far. By default settings (and following SpaceInvaderOne's exact video on this), I can't get it to work. However, that's only one step I've tried. LAN_Network is usually blank, but I have also tried putting in 192.168.1.2. (i like to keep the IP fixed so I don't need to change bookmarks and Sonarr/Radarr). I have tried br0, set the Fixed IP to 192.168.1.2. And as I said there's no point in trying to reach the webui on br0, if you want to use br0 try the desktop/thin client like I mentioned. So in order to know whats correct I really want to know your routers IP or what Ip your're connecting to when you try to reach the webui. There is really only one value that works for your network, no point in trying multiple. And setting it to blank and to match the IP set on br0 confirms that. Since you say lan_network has been tried in many formats it says to me that you don't really know what to put there.
0 kommentar(er)
