clowrym

I didint think of this... Done, installed, confirmed working & set up a script to re-install it after reboot.

I am having this issue was well. Attached Diag. Mine is only on a single disk though.... tower-diagnostics-20190122-1629.zip Edit: I spoke too soon, its affecting all my btrfs disks (only have a few left...most have been converted to xfs)

As am I Jan 22 15:49:32 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 16, flush 0, corrupt 0, gen 0 Jan 22 15:49:43 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 17, flush 0, corrupt 0, gen 0 Jan 22 15:50:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 15:50:33 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 18, flush 0, corrupt 0, gen 0 Jan 22 15:50:41 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 19, flush 0, corrupt 0, gen 0 Jan 22 15:50:46 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 20, flush 0, corrupt 0, gen 0 Jan 22 15:51:00 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 21, flush 0, corrupt 0, gen 0 Jan 22 15:51:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 15:51:21 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 22, flush 0, corrupt 0, gen 0 Jan 22 15:52:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 15:52:23 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 23, flush 0, corrupt 0, gen 0 Jan 22 15:52:28 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 24, flush 0, corrupt 0, gen 0 Jan 22 15:52:28 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 25, flush 0, corrupt 0, gen 0 Jan 22 15:52:32 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 26, flush 0, corrupt 0, gen 0 Jan 22 15:52:34 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 27, flush 0, corrupt 0, gen 0 Jan 22 15:52:34 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 28, flush 0, corrupt 0, gen 0 Jan 22 15:52:39 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 29, flush 0, corrupt 0, gen 0 Jan 22 15:52:59 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 30, flush 0, corrupt 0, gen 0 Jan 22 15:53:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 15:53:45 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 31, flush 0, corrupt 0, gen 0 Jan 22 15:53:45 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 32, flush 0, corrupt 0, gen 0 Jan 22 15:53:52 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 33, flush 0, corrupt 0, gen 0 Jan 22 15:53:52 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 34, flush 0, corrupt 0, gen 0 Jan 22 15:54:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 15:54:11 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 35, flush 0, corrupt 0, gen 0 Jan 22 15:54:15 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 36, flush 0, corrupt 0, gen 0 Jan 22 15:54:26 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 37, flush 0, corrupt 0, gen 0 Jan 22 15:54:26 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 38, flush 0, corrupt 0, gen 0 Jan 22 15:54:31 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 39, flush 0, corrupt 0, gen 0 Jan 22 15:54:37 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 40, flush 0, corrupt 0, gen 0 Jan 22 15:54:39 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 41, flush 0, corrupt 0, gen 0 Jan 22 15:55:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 15:55:29 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 42, flush 0, corrupt 0, gen 0 Jan 22 15:55:32 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 43, flush 0, corrupt 0, gen 0 Jan 22 15:55:48 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 44, flush 0, corrupt 0, gen 0 Jan 22 15:55:48 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 45, flush 0, corrupt 0, gen 0 Jan 22 15:55:54 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 46, flush 0, corrupt 0, gen 0 Jan 22 15:55:54 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 47, flush 0, corrupt 0, gen 0 Jan 22 15:56:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 15:56:02 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 48, flush 0, corrupt 0, gen 0 Jan 22 15:56:19 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 49, flush 0, corrupt 0, gen 0 Jan 22 15:56:29 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 50, flush 0, corrupt 0, gen 0 Jan 22 15:56:29 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 51, flush 0, corrupt 0, gen 0 Jan 22 15:56:37 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 52, flush 0, corrupt 0, gen 0 Jan 22 15:56:37 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 53, flush 0, corrupt 0, gen 0 Jan 22 15:56:52 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 54, flush 0, corrupt 0, gen 0 Jan 22 15:56:57 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 55, flush 0, corrupt 0, gen 0 Jan 22 15:57:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 15:57:19 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 56, flush 0, corrupt 0, gen 0 Jan 22 15:58:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 15:58:05 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 57, flush 0, corrupt 0, gen 0 Jan 22 15:58:12 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 58, flush 0, corrupt 0, gen 0 Jan 22 15:58:12 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 59, flush 0, corrupt 0, gen 0 Jan 22 15:58:18 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 60, flush 0, corrupt 0, gen 0 Jan 22 15:58:18 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 61, flush 0, corrupt 0, gen 0 Jan 22 15:58:25 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 62, flush 0, corrupt 0, gen 0 Jan 22 15:59:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 15:59:02 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 63, flush 0, corrupt 0, gen 0 Jan 22 16:00:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 16:00:22 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 64, flush 0, corrupt 0, gen 0 Jan 22 16:00:44 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 65, flush 0, corrupt 0, gen 0 Jan 22 16:00:44 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 66, flush 0, corrupt 0, gen 0 Jan 22 16:00:53 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 67, flush 0, corrupt 0, gen 0 Jan 22 16:01:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 16:01:43 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 68, flush 0, corrupt 0, gen 0 Jan 22 16:01:43 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 69, flush 0, corrupt 0, gen 0 Jan 22 16:01:49 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 70, flush 0, corrupt 0, gen 0 Jan 22 16:02:00 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 71, flush 0, corrupt 0, gen 0 Jan 22 16:02:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 16:02:40 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 72, flush 0, corrupt 0, gen 0 Jan 22 16:02:40 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 73, flush 0, corrupt 0, gen 0 Jan 22 16:02:45 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 74, flush 0, corrupt 0, gen 0 Jan 22 16:03:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 16:03:40 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 75, flush 0, corrupt 0, gen 0 Jan 22 16:03:45 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 76, flush 0, corrupt 0, gen 0 Jan 22 16:03:45 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 77, flush 0, corrupt 0, gen 0 Jan 22 16:03:47 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 78, flush 0, corrupt 0, gen 0 Jan 22 16:03:47 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 79, flush 0, corrupt 0, gen 0 Jan 22 16:03:54 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 80, flush 0, corrupt 0, gen 0 Jan 22 16:04:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 16:04:09 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 81, flush 0, corrupt 0, gen 0 Jan 22 16:04:25 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 82, flush 0, corrupt 0, gen 0 Jan 22 16:04:25 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 83, flush 0, corrupt 0, gen 0 Jan 22 16:05:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 16:05:25 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 84, flush 0, corrupt 0, gen 0 Jan 22 16:05:25 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 85, flush 0, corrupt 0, gen 0 Jan 22 16:06:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 16:07:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 16:07:43 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 86, flush 0, corrupt 0, gen 0 Jan 22 16:07:43 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 87, flush 0, corrupt 0, gen 0 Jan 22 16:07:46 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 88, flush 0, corrupt 0, gen 0 Jan 22 16:07:56 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 89, flush 0, corrupt 0, gen 0 Jan 22 16:08:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 16:08:11 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 90, flush 0, corrupt 0, gen 0 Jan 22 16:08:21 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 91, flush 0, corrupt 0, gen 0 Jan 22 16:08:25 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 92, flush 0, corrupt 0, gen 0 Jan 22 16:08:32 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 93, flush 0, corrupt 0, gen 0 Jan 22 16:08:38 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 94, flush 0, corrupt 0, gen 0 Jan 22 16:08:38 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 95, flush 0, corrupt 0, gen 0 Jan 22 16:08:56 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 96, flush 0, corrupt 0, gen 0 Jan 22 16:08:56 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 97, flush 0, corrupt 0, gen 0 Jan 22 16:09:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 16:09:05 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 98, flush 0, corrupt 0, gen 0 Jan 22 16:09:05 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 99, flush 0, corrupt 0, gen 0 Jan 22 16:09:07 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 100, flush 0, corrupt 0, gen 0 Jan 22 16:10:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jan 22 16:10:15 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 101, flush 0, corrupt 0, gen 0 Jan 22 16:10:15 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 102, flush 0, corrupt 0, gen 0 Jan 22 16:10:22 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 103, flush 0, corrupt 0, gen 0 Jan 22 16:10:31 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 104, flush 0, corrupt 0, gen 0 Jan 22 16:10:31 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 105, flush 0, corrupt 0, gen 0

Upgraded, Only issue is my VPN will not start, posted on the plugin page. New layout looks good!! openvpn: error while loading shared libraries: libcrypto.so.l: cannot open shared object file: No such file or directory openvpn: error while loading shared libraries: libcrypto.so.l: cannot open shared object file: No such file or directory

Just upgraded to 6.7.0-rc1, for some reason I can't start my plugin anymore, the following is all the entries I see in the Logs Jan 22 11:19:01 Test ool www[18957]: /usr/local/emhttp/plugins/openvpnserver/scripts/rc.openvpnserver 'start' Jan 22 11:19:01 Test sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=root ; COMMAND=/usr/sbin/openvpn --writepid /var/run/openvpnserver/openvpnserver.pid --config /mnt/cache/appdata/OpenVPN/openvpnserver.ovpn --script-security 2 --daemon Also found: openvpn: error while loading shared libraries: libcrypto.so.l: cannot open shared object file: No such file or directory

modified to the following & everything is working after a few modifications as I have actual wattage used instead of Percentage.... #!/usr/bin/php <?php $command = "upsc"; $args = "ups"; $tagsArray = array( "battery.charge", "device.model", "ups.realpower", "ups.load", "battery.runtime", "output.voltage" ); //do system call $call = $command." ".$args; $output = shell_exec($call); //parse output for tag and value foreach ($tagsArray as $tag) { preg_match("/".$tag."\s*:\s([\d|\.]+)/si", $output, $match); //send measurement, tag and value to influx sendDB($match[1], $tag); } //end system call //send to influxdb function sendDB($val, $tagname) { $curl = "curl -i -XPOST 'http://192.168.0.XX:8086/write?db=UPS' --data-binary 'APC,host=Tower,region=us-west " .$tagname."=".$val."'"; $execsr = exec($curl); } ?>

I've been trying to get this to work for my dell UPS on nut, but always end up with this error: Can't seem to figure out the issue! Parse error: syntax error, unexpected '$call' (T_VARIABLE) in /tmp/user.scripts/tmpScripts/UPS Monitor/script on line 14

Interesting, not sure why those are there, my password is stored in the config file for transmission I didnt create the docker, only the template for unraid, you could post here: https://github.com/haugene/docker-transmission-openvpn

Sorry for the late reply.. its been a busy couple weeks at work!! There seems to be an issue with adding multiple local networks in the cell you have above, I tried the same originally when I first made this template. I ended up adding a script to user scripts plugin that runs on server boot & that I run if I force a restart/update on Transmission. I have listed it below.... I know its a work around, but I havent figured out how to allow multiple networks in the docker template..... I use the script below for access loutside of my local network thru the VPN I have set up for my work computer / phone when I am not on ly local network. adjust the ip addresses to suit your network setup!! #!/bin/bash echo adding 10.1.0.0/25 LAN_NETWORK docker exec Transmission_VPN /bin/sh -c "/sbin/ip r a 10.1.0.0/24 via 172.17.0.1 dev eth0" echo Netowrk added exit

Most issues are usually a error in mapping / ports!! Glad you got it working!@!

what are you changing the destinations to? can you provide the template screenshot after you've made the change and get the error. Also a screenshot of the error might be helpful

you should be able to add Transmission parameters to your docker template and they will survive reboot as detailed here . Detailed part way down the page under "Transmission configuration options" for instance, you would add "TRANSMISSION_INCOMPLETE_DIR_ENABLED" with a value of "false" to disable the incomplete download directory. This holds true for any variable you want to survive a reboot.

I've only created the templates, Nukkit Might be able to update it for you.

TO be honest, I havent kept up with any new opvn locations that have been added, I added DE Berlin/Frakfurt this morning for you. You can add your own locations if any are missing. I'm not sure on your other issue, I've had no problems keeping with the most current version. Might want to post a support ticket here as I only created the Template for unraid, not the application itself! I currently run the Dev branch of his repository I'm currently running: Transmission: 2.94 (d8e60ee44f), RPC: 15 Web Control: 1.6.0 alpha (20180418)

after saome more troubleshooting,this may not be related to unraid.... I have a dual wan connection on my Asus router and I think it may be having some issues when my router is allowed to manage which connection it gives to a specific device.manually setting my server to a specific wan, seems to have fixed the issue for now.

diagnostics!! poweredge-diagnostics-20181016-1148.zip

Also get this when running Community apps. I currently have my DNS set to 8.8.8.8 & 8.8.4.4 and have no issues pinging either.... Download of appfeed failed. Community Applications requires your server to have internet access. The most common cause of this failure is a failure to resolve DNS addresses. You can try and reset your modem and router to fix this issue, or set static DNS addresses (Settings - Network Settings) of 8.8.8.8 and 8.8.4.4 and try again.

I've have had a problem for a while on one of my 3 servers where checking for updates doesnt work, just stays at checking. It was suggested that I remove the dev-pack plugin, but I dont have it installed. I have removed all plugins except OpenVPN, but it doesnt seem to help. I also can't update the server to a new version as the download never completes/starts. All I seem to get are the follwing errors. I've tryied changing DNS settings, but doesnt seem to make a difference. Check for update OS doesnt return results, update assistant never completes either. I'm not sure what else to try..... Oct 16 11:06:57 Poweredge nginx: 2018/10/16 11:06:57 [error] 5791#5791: *2313719 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.0.0.212, server: , request: "GET /plugins/dynamix.plugin.manager/include/ShowPlugins.php?check=0 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.0.0.222", referrer: "http://10.0.0.222/Plugins" Oct 16 10:48:05 Poweredge nginx: 2018/10/16 10:48:05 [error] 5791#5791: *2312370 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.0.0.212, server: , request: "GET /Main HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "poweredge"

Interesting, Mine has always been set to my router as main & 8.8.8.8 as secondary. Changing the main to google doesnt help either....

I have this issue as well, It was suggested to remove the dev-pack plugin, Here, but I've never had it installed. I also tired removing the nerd-pack plugin, but made no difference.... still havent found a fix. I also have pi-hole installed, but not running & I've had it installed for a couple years now with no issues.

I dont believe I have that one.... poweredge-diagnostics-20180921-0803.zip

Not sure if its something to do with the update, But i cant check for plugin updates, page never loads & I get the following error Sep 20 17:23:24 Poweredge nginx: 2018/09/20 17:23:24 [error] 6962#6962: *1736 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.1.0.6, server: , request: "GET /plugins/dynamix.plugin.manager/include/ShowPlugins.php?check=0 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.0.0.222", referrer: "http://10.0.0.222/Plugins"

You can change the OPENVPN provider by setting to advanced view & adjusting the Default values to whatever your location names are seeperated by "|" ie.... name1|name2|name3| etc.

ca you show me your folder mappings? Anytime ive had this in th epast its beena folder mapping issue during template creation!

can you show me this: