bcjenkins

Members
  • Posts

    34
  • Joined

  • Last visited

Everything posted by bcjenkins

  1. Also being discussed here in a different thread.
  2. Sure, tack them onto the end. It's just a mission statement.
  3. I had to read that a few times to spot the difference! Seems like it could be written a little more succinctly to state that Yes - Write to cache for new, move to array when mover runs. Prefer - Write to cache for new, move to cache when mover runs. Thanks for the pointer.
  4. I did not delete it. I am using a prefer cache on TV because Plex is recording TV shows there and I want them moved to disk afterwards. The TV folder exists in cache but not disk# Thanks.
  5. Greetings, I have a share called TV which is configured as attached. The share's directory does not exist in any of the physical disk mount points and when mover runs, it outputs the following error: emhttpd: shcmd (330): /usr/local/sbin/mover |& logger & root: mover: started find: `TV': No such file or directory root: mover: finished Thanks TV.cfg
  6. I do not have any dockers installed. I had deleted my docker.img file to reset.
  7. Lime-Tech provides docker support in the application which is why I selected them and paid for my license. Installing a docker seems to be a core feature and Lime-Tech's own templates, PlexMediaServer and Sync do not work either. Can we get to the point where we are working on a fix? What else can be provided as information?
  8. Is Community Applications supported by Lime-Tech? Preference is to keep system at point of support which is not confused between community support and official support. @dlandon Thanks for additional tests.
  9. See attached. No extra plugins installed. I am trying to install the mariadb from https://github.com/linuxserver/docker-templates/tree/master/linuxserver.io and I get the white screen. I have also noticed that br0 seems to be missing. I tried rm /var/lib/docker/network/files/local-kv.db /etc/rc.d/rc.docker restart It had no effect. cba-unr-01-diagnostics-20180410-0813.zip
  10. When attempting to add a container in docker, the following errors appear in the JS console in Firefox The connection to https://unraidServer/sub/var was interrupted while the page was loading. dynamix.js:34:10380 TypeError: container is null[Learn More] AddContainer:424:22 makeAllocations https://unraidServer/Docker/AddContainer:424:22 <anonymous> https://unraidServer/Docker/AddContainer:1247:34 i https://unraidServer/webGui/javascript/dynamix.js:4:27146 fireWith https://unraidServer/webGui/javascript/dynamix.js:4:27914 ready https://unraidServer/webGui/javascript/dynamix.js:4:29705 J https:///webGui/javascript/dynamix.js:4:29890 Upon clicking on the lick to add the container, I get a white screen with nothing being done.
  11. For those not using CA - https://github.com/linuxserver/docker-templates/tree/master/linuxserver.io
  12. /etc/rc.d/rc.docker ? usage /etc/rc.d/rc.docker start|stop|restart|status
  13. The following are ramblings of my journey to get a custom SSL cert for any number of hosts which I run in Docker containers or unRAID itself. This was done in unRAID 6.4 which is required due to features provided in unRAID. In my environment, I am leveraging IPv6 addresses for unRAID and Docker containers to provide a publicly routable address for all instances allowing for direct communication from clients without a need for proxying or NATing. To generate the SSL certs, I am using the acme.sh script which runs on unRAID without issue, and I am leveraging the LetsEncrypt DNS api to provide a cert so that communication with the server from LetsEncrypt is not needed. I created a share specifically for certs, and restricted it to local access only. In my use, I am hosting my DNS at Cloudflare and leveraging their API to create the necessary challenge records; all of which is built in to the acme.sh project. There are many DNS providers which are supported, and you can also use direct access as needed. So far, I have created a custom cert for unRAID and for Plex. The acme.sh script will create an individual cert directory for each cert. This allows you to restrict the container access to the cert which is applicable. I will be working on a script specific to LetsEncrypt and Cloudflare which will monitor IP address changes for hosts, and perform cert issuance and renewals. The following is the gist of what I used to get things running manually. It is performed from the cli of the unRAID server. You will need to replace ${variables} with the actual names or export them before running the command. # Show the IPv6 address of the unRAID server ifconfig # Show the IPv6 address of the Docker container docker inspect --format='{{range .NetworkSettings.Networks}}{{.GlobalIPv6Address}}{{end}}' ${dockaerContainerName} # Create the share in the unRAID panel # Create the directory structure for the acme.sh mkdir -p /mnt/user/${shareName}/acme/dnsapi # Obtain the acme.sh script and perform the install curl -s https://raw.githubusercontent.com/Neilpang/acme.sh/master/acme.sh > /mnt/user/${shareName}/acme.sh chmod +x /mnt/user/${shareName}/acme.sh /mnt/user/${shareName}/acme.sh --install --accountemail "${LetsEncryptEmail}" --home /mnt/user/${shareName}/acme # Download the Cloudflare DNS api script and make executable curl -s https://raw.githubusercontent.com/Neilpang/acme.sh/master/dnsapi/dns_cf.sh > /mnt/user/${shareName}/acme/dnsapi/dns_cf.sh chmod +x /mnt/user/${shareName}/acme/dnsapi/dns_cf.sh # Per usage instruction for Cloudflare api in the acme.sh: set the CF API key and email variables export CF_Key="${yourKey}" export CF_Email="${CloudflareEmail}" At this point you're ready to begin issuing certs. I'll provide an example for the unRAID server and Plex container. Prior to this, you will want to create AAAA records in the Cloudflare DNS panel. # Issue a cert for unRAID /mnt/user/${shareName}/acme/acme.sh --home /mnt/user/${shareName}/acme --issue --dns dns_cf --ecc -d ${yourFQDN} --keylength ec-256 # Backup existing cert mv /boot/config/ssl/certs/${certName}.pem /boot/config/ssl/certs/${certName}.bak # Create new cert using same name cat /mnt/user/${shareName}/acme/${yourFQDN}_ecc/fullchain.cer /mnt/user/${shareName}/acme/${yourFQDN}_ecc/${yourFQDN}.key > /boot/config/ssl/certs/${certName}.pem # Reload nginx /etc/rc.d/rc.nginx reload # Issue a cert for Plex - Plex didn't seem to support ecc certs in my testing. /mnt/user/${shareName}/acme/acme.sh --home /mnt/user/${shareName}/acme --issue --dns dns_cf -d ${yourFQDN} --keylength 2048 # Convert the cert to PKCS /mnt/user/${shareName}/acme/acme.sh --home /mnt/user/${shareName}/acme --toPkcs -d ${yourFQDN} --password ${certEncPass} # Configure your Docker container to add a path for the certs. # Configure the SSL cert settings in the Plex Netowrk Settings # Restart the container docker restart ${dockaerContainerName}
  14. It's pretty easy - docker restart ${dockerName}
  15. Greetings, I have a Mellanox Technologies MT27520 Family [ConnectX-3 Pro] card in my unRAID server. Upon server reboot, the GBIC has to be removed and reinserted for the card to come online. Has anyone experienced anything like this? The card/system worked fine with Ubuntu 16.04 and the Mellanox drivers from their site before I put unRAID onto the system. Thanks, B