mnz88

Well, I'm still seeing the random crashes. I am using the Fix Common Problems "Troubleshooting Mode", but it seems that at some point it stopped logging to the Syslog file in its directory. This time I could still ping the server but couldn't see anything from the console. Nor could I access the server through SSH or the web interface. At least it didn't take down my entire network this time. I'm attaching the last diagnostic log it took if that helps anybody. I'd really appreciate it if somebody could help me out with this. Thanks! mnz-serv-diagnostics-20170126-1341.zip

I just updated the BIOS about a week ago. I'm fairly certain that all BIOS settings are stock, but I'll take another look through the manual and make sure nothing looks wonky. I just upgraded to v6.3.0-rc6, so we'll see if that helps at all. Thanks!

I have been battling off and on with my unRAID box randomly crashing every day or two for the past year or so. I'm at my wit's end, because I can't seem to figure out what triggers it. Sometimes it crashes when I start or stop the array, sometimes it crashes overnight. At first, I thought the issue was my NIC because the server crashing would sometimes lock up my entire network. I installed a new Intel NIC and disabled the onboard NIC in the BIOS. I've run 24 hours worth of memtests with no errors. I even ran the system with Windows Server installed for several days (and saw no issues). I've installed the "Fix Common Problems" plugin, and it doesn't come up with anything. During this most recent crash, I managed to pull a diagnostic off of it before it went down. In addition, I had a syslog tail running to the attached text file. If somebody could help me out with this, I'd be eternally grateful... eternally. I've spent countless hours trying to troubleshoot this. Thanks! mnz-serv-diagnostics-20170118-1950.zip syslogtail2.zip

Not sure if my fault or not but i seem to be getting this error as described back on Dec 30 "[crit] VPN port not found in ovpn file, please check ovpn file for port number of gateway" I've actually just pulled down the image for the first time, here is the ovpn file if someone could cast an eye over it and offer some help. I've got the key and ca file in the openvpn dir. client dev tun proto tcp remote au1-ovpn-tcp.purevpn.net 80 persist-key persist-tun ca ca.crt tls-auth Wdc.key 1 cipher AES-256-CBC comp-lzo verb 1 mute 20 route-method exe route-delay 2 route 0.0.0.0 0.0.0.0 float auth-user-pass auth-retry interact ifconfig-nowarn Thanks! hi can you try pulling down the latest image, ive made some tweaks to the regex im using, if its still not working then please post the output of the supervisord.log file Hey Binhex, I was having this same issue after updating this morning. I just forced update per your suggestion to Certo and it's working again. Thanks!

yeah ive had a few stabs at trying to get this to work in he past but been frustrated with iptables blocking. you have spurred me on to take another swing at this and i eventually stumbled across the right entries to allow this to work. i have gone with a stricter approach than the above, simply because i want to limit the ability for the deluge daemon to talk to anything outside of your own lan, and thus reduce the chance of ip leakage of your isp ip. so firstly pull down the new image then if you define the "LAN_RANGE" env variable e.g.:- 192.168.1.1-192.168.1.100 then you should be able to talk to the deluge daemon from any ip in that range, give it a try and let me know how you get on Just tried this out, and it's working! I've been following this thread hoping this would eventually work. Thanks so much binhex.