wreave

Perfect, thanks.

I did not, where would I get these if it should happen again?

Did a reboot while clenching and you were right, it came up okay. Any idea what causes this? Thanks again!

Will that resolve all the issues or causes the array to think the disks are "new"?

Suddenly got alerts about read errors, stopped my array and it is showing several drives as unassigned now. I know these drives are fine but I cannot start the array in maintenance mode to repair the xfs file system. How can I fix this? Thanks in advance for any help.

I am trying to create a new VM but when starting it I am stuck at the UEFI shell. I have tried following http://lime-technology.com/forum/index.php?topic=51874.0 but both fs0: and fs1: are not working (see screenshot). Any help is appreciated. EDIT: Looks like the issue is related to the OS not supporting OVMF. Recreating the VM with SeaBIOS resolved.

I've noticed some weirdness where the Stats plugin shows impossible spikes on my Bonded (2x1Gb) Ethernet connection (attached image). Is this something that has been discussed? Searches on the forum were a little messy and I wasn't able to find much useful information. Thanks!

Wrong port, change 1194 to 1198 Sent from my SM-G900F using Tapatalk Not sure how that happened but that was it. Thanks!

Hello, After the upgrade to unraid 6.2 it had me update my Docker image. Now the OpenVPN part of the Docker seems to be failing to start. I've included the logs below. [info] Starting OpenVPN... 2016-09-16 02:21:13,719 DEBG 'start-script' stdout output: Fri Sep 16 02:21:13 2016 OpenVPN 2.3.11 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on May 12 2016 2016-09-16 02:21:13,719 DEBG 'start-script' stdout output: Fri Sep 16 02:21:13 2016 library versions: OpenSSL 1.0.2h 3 May 2016, LZO 2.09 2016-09-16 02:21:13,719 DEBG 'start-script' stdout output: Fri Sep 16 02:21:13 2016 WARNING: file 'credentials.conf' is group or others accessible 2016-09-16 02:21:13,753 DEBG 'start-script' stdout output: Fri Sep 16 02:21:13 2016 UDPv4 link local: [undef] 2016-09-16 02:21:13,753 DEBG 'start-script' stdout output: Fri Sep 16 02:21:13 2016 UDPv4 link remote: [AF_INET]46.166.188.240:1194 2016-09-16 02:21:14,146 DEBG 'start-script' stdout output: Fri Sep 16 02:21:14 2016 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: C=US, ST=OH, L=Columbus, O=Private Internet Access, CN=Private Internet Access CA, [email protected] 2016-09-16 02:21:14,146 DEBG 'start-script' stdout output: Fri Sep 16 02:21:14 2016 OpenSSL: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed Fri Sep 16 02:21:14 2016 TLS_ERROR: BIO read tls_read_plaintext error Fri Sep 16 02:21:14 2016 TLS Error: TLS object -> incoming plaintext read error Fri Sep 16 02:21:14 2016 TLS Error: TLS handshake failed Fri Sep 16 02:21:14 2016 SIGUSR1[soft,tls-error] received, process restarting

That is definitely your problem. Try setting the host port to 81 and have your router port forward from 80 to 81.

Single domain only. Two separate dockers wouldn't work for automated renewals as they can't share the outside port 443. Unless your router can forward to different ports based on url (very rare) My router does a lot of things but that is not one of them. I guess I'll set up a 2nd container for now and worry about manually redoing the certs if needed (remapping ports for the renew process). My end goal is to move from one domain to another so this should achieve that. Actually now that I think about it that won't work since my outside 443 port can only map to one docker container.... damn

Single domain only. Two separate dockers wouldn't work for automated renewals as they can't share the outside port 443. Unless your router can forward to different ports based on url (very rare) My router does a lot of things but that is not one of them. I guess I'll set up a 2nd container for now and worry about manually redoing the certs if needed (remapping ports for the renew process). My end goal is to move from one domain to another so this should achieve that.

Does the nginx-letsencrypt docker support multiple domains, or do I need to make a seperate Docker container for each domain I have? Thanks!

Looks like hardlinks cannot be made for a directory anyways user@server:/mnt/cache/appdata/plex/Library# ln '/mnt/disk1/plex_metadata/Application Support' '/mnt/cache/appdata/plex/Library/Application Support' ln: ‘/mnt/disk1/plex_metadata/Application Support’: hard link not allowed for directory

Why not just change the /config mapping to point to some folder on the array? Of course you'd need to move it all there too. I have considered that but I would like to keep the core software on the SSD if possible. what version of unRaid. Symlink (and more to the point hardlink) support on user shares isn't supported on 6.1.x and only works on 6.2RC3+ It should work however by using a disk share Also, the core software is stored within the docker.img file, not within appdata Still on 6.1.x Maybe it is just easier to install it on a share off the cache then. Thanks for the info You'll have to use a disk share, not a user share. IE: set /config to be something like /mnt/disk1/appdata/Plex and not /mnt/user/appdata/Plex. Plex makes very extensive use of hardlinks which are incompatible with /mnt/user/... on 6.1.x Okay I might give that a try! But be aware that performance of the app as a whole (and transcoding in particular) is going to go downhill with appdata sitting on the array. If you really make extensive use of Plex, your best solution is to either turn off thumbnail generation (which will save huge amounts of storage space, but you'll probably have to start the db over again from scratch to get rid of the existing thumbnails) or a larger cache drive. Thanks for the heads up. I think I'll copy/pasta for now and see how it performs with the symlink and then I can roll back if needed.

Why not just change the /config mapping to point to some folder on the array? Of course you'd need to move it all there too. I have considered that but I would like to keep the core software on the SSD if possible. what version of unRaid. Symlink (and more to the point hardlink) support on user shares isn't supported on 6.1.x and only works on 6.2RC3+ It should work however by using a disk share Also, the core software is stored within the docker.img file, not within appdata Still on 6.1.x Maybe it is just easier to install it on a share off the cache then. Thanks for the info You'll have to use a disk share, not a user share. IE: set /config to be something like /mnt/disk1/appdata/Plex and not /mnt/user/appdata/Plex. Plex makes very extensive use of hardlinks which are incompatible with /mnt/user/... on 6.1.x Okay I might give that a try!

Why not just change the /config mapping to point to some folder on the array? Of course you'd need to move it all there too. I have considered that but I would like to keep the core software on the SSD if possible. what version of unRaid. Symlink (and more to the point hardlink) support on user shares isn't supported on 6.1.x and only works on 6.2RC3+ It should work however by using a disk share Also, the core software is stored within the docker.img file, not within appdata Still on 6.1.x Maybe it is just easier to install it on a share off the cache then. Thanks for the info

Why not just change the /config mapping to point to some folder on the array? Of course you'd need to move it all there too. I have considered that but I would like to keep the core software on the SSD if possible.

Hello, I am trying to configure a symlink for my plex meta data since it is taking up a large portion of my cache drive. However it appears when i configure the symlink and start plex i get the following error: WARNING COULDN'T CREATE /config/Library/Application Support, MAKE SURE I HAVE PERMISSON TO DO THAT! In the above example I made a symlink for the Application Support folder. I have made sure to give the symlink the same privileges as the original Application Support. I then tested making a symlink to just the Plex Media Sever folder but get the following on an endless loop: Starting Plex Media Server. 6 3000 /config/Library/Application Support unlimited Starting Plex Media Server. 6 3000 /config/Library/Application Support unlimited Are symlinks supported with this Docker? Is there a better way for me to have my Plex metadata stored on the array and not the cache? Thanks in advance for any help that can be provided.

If it is a clean install in an empty config folder, the issue is likely due to cert generation. Most likely, your port 80 is not forwarded to the container properly, or there is an issue with your domain url setting. The letsencrypt log in the config folder can point you in the right direction There are no log files in config/nginx-letsencrypt/log/letsencrypt or in /nginx Is this where I should be looking? Oh oops. Nevermind. The initial one doesn't log to that file, but logs to the docker log. Type the following in the unraid terminal and it should show the error: docker logs Nginx-letsencrypt I got the following Restarting web server * Starting nginx nginx ...fail! * Starting nginx nginx ...fail! * Starting authentication failure monitor fail2ban ERROR No file(s) found for glob /config/log/nginx/error.log ERROR Failed during configuration: Have not found any log file for nginx-http-auth jail ...fail! *** Running /etc/rc.local... *** Booting runit daemon... Thanks for the help Please post your container settings I have linked my container settings with 2 things to note: 1. I've changed the domain and email for security 2. My router is port forwarding 80 to 81 and the docker switches it back to 80 http://i.imgur.com/njOCKA0.jpg Port 443 is the one used for cert generation. Is it forwarded? The log you posted is missing the beginning part about certs and other local files. So 443 is/was also forwarded. Now i just restarted the Docker to get you fresh Docker logs and now it is starting... I am going to make sure i can get everything working as expected (site-conf) and make sure it all works but the cert seems to be good. I changed nothing so this is very strange. Thanks for your time.

If it is a clean install in an empty config folder, the issue is likely due to cert generation. Most likely, your port 80 is not forwarded to the container properly, or there is an issue with your domain url setting. The letsencrypt log in the config folder can point you in the right direction There are no log files in config/nginx-letsencrypt/log/letsencrypt or in /nginx Is this where I should be looking? Oh oops. Nevermind. The initial one doesn't log to that file, but logs to the docker log. Type the following in the unraid terminal and it should show the error: docker logs Nginx-letsencrypt I got the following Restarting web server * Starting nginx nginx ...fail! * Starting nginx nginx ...fail! * Starting authentication failure monitor fail2ban ERROR No file(s) found for glob /config/log/nginx/error.log ERROR Failed during configuration: Have not found any log file for nginx-http-auth jail ...fail! *** Running /etc/rc.local... *** Booting runit daemon... Thanks for the help Please post your container settings I have linked my container settings with 2 things to note: 1. I've changed the domain and email for security 2. My router is port forwarding 80 to 81 and the docker switches it back to 80 http://i.imgur.com/njOCKA0.jpg

If it is a clean install in an empty config folder, the issue is likely due to cert generation. Most likely, your port 80 is not forwarded to the container properly, or there is an issue with your domain url setting. The letsencrypt log in the config folder can point you in the right direction There are no log files in config/nginx-letsencrypt/log/letsencrypt or in /nginx Is this where I should be looking? Oh oops. Nevermind. The initial one doesn't log to that file, but logs to the docker log. Type the following in the unraid terminal and it should show the error: docker logs Nginx-letsencrypt I got the following Restarting web server * Starting nginx nginx ...fail! * Starting nginx nginx ...fail! * Starting authentication failure monitor fail2ban ERROR No file(s) found for glob /config/log/nginx/error.log ERROR Failed during configuration: Have not found any log file for nginx-http-auth jail ...fail! *** Running /etc/rc.local... *** Booting runit daemon... Thanks for the help

If it is a clean install in an empty config folder, the issue is likely due to cert generation. Most likely, your port 80 is not forwarded to the container properly, or there is an issue with your domain url setting. The letsencrypt log in the config folder can point you in the right direction There are no log files in config/nginx-letsencrypt/log/letsencrypt or in /nginx Is this where I should be looking?

I lost my nginx-letsencrypt docker info and now I am trying to create it again using the same domains and email and everything. There seems to be an error with it launching nginx however as I get this error when starting the docker up: Preparing to generate server certificate for the first time Temporarily stopping Nginx * Stopping nginx nginx ...done. Generating/Renewing certificate Restarting web server * Starting nginx nginx ...fail! * Starting nginx nginx ...fail! * Starting authentication failure monitor fail2ban ...fail! Any ideas? Edit: To clarify this is a clean install with no changes to anything other than the info entered into unRAID when making the docker. Thanks for anything you can do.

Thank you for the clarification