sgt_spike

Thanks aptalca for the quick reply I figured it out. I had the www folder as read-only in the settings.

Please excuse the novice question. I'm trying to setup a store front with opencart and the files needed for the site has to writable. However when the container restarts it sets the permissions to read only. How can I change this for a specific folder/flies?

How do I configure multiple domains?

I have received the same error. I haven't done any maintenance for a couple of weeks so I cannot tell when this started.

How do I connect to a MariaDB Repository? Or how do I install the Connect engine?

it should read -p yourunraidip:32400:32400. I switch back to host and still cannot get plex to connect outside my network. Not even at plex.tv. All ports have been forwarded on router. I know at one point I was able to connect outside using plex.tv but for whatever reason went down again.

Which server are you referring to; plex, LE, unraid, and where in the proxy config file would I put the server's IP? I have LE and plex running on the same user defined network (172.18.0.0). It's my understanding that plex is then running in bridge mode, at this point. If I'm wrong, please enlighten me !!!! Below is the plex proxy config file I'm using. it's the boilerplate version, I just renamed the file, taking off the .sample server { listen 443 ssl; server_name plex.*; include /config/nginx/ssl.conf; client_max_body_size 0; proxy_redirect off; proxy_buffering off; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_plex plex; proxy_pass https://$upstream_plex:32400; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header X-Plex-Client-Identifier $http_x_plex_client_identifier; proxy_set_header X-Plex-Device $http_x_plex_device; proxy_set_header X-Plex-Device-Name $http_x_plex_device_name; proxy_set_header X-Plex-Platform $http_x_plex_platform; proxy_set_header X-Plex-Platform-Version $http_x_plex_platform_version; proxy_set_header X-Plex-Product $http_x_plex_product; proxy_set_header X-Plex-Token $http_x_plex_token; proxy_set_header X-Plex-Version $http_x_plex_version; proxy_set_header X-Plex-Nocache $http_x_plex_nocache; proxy_set_header X-Plex-Provides $http_x_plex_provides; proxy_set_header X-Plex-Device-Vendor $http_x_plex_device_vendor; proxy_set_header X-Plex-Model $http_x_plex_model; } }

Gobs, I had the same issues setting up plex. Here's what I did...... If you are using a user defined network for LE and plex, the plex port must be mapped to the host (unraid). To do this edit the config, Docker->click on edit. Change to Advance mode. In the "Extra Parameters" section add this line (changing info to your info) "-p UnRaidIP:32400:32400" this should look something like -p 192.168.1.10:32400:32400 This will allow the webui to load on local. I have not been able to get plex to load via a custom web address as the proxy.config file instructions seems a bit confusing IMHO.

I got the containers port mapped to the host and it connects to the web_ui. However I'm not sure why I keep getting a bad gateway error trying to connect with https://plex.spikedevelopments.com

So set network back to the user defined network and add a port setting in the plex setup. The port being 10.20.30.10:32400 to 172.18.0.6:32400. If I have it wrong it's because your last statement is unclear to me. i understand your first statement, is that in addition to your second statement or are they two separate setting types

Hello Experts! I have setup LE on a custom network. I'm trying to setup reverse proxy for my plex (linuxserver plex). I set plex up on the same custom network. At this point I cannot reach plex through the web_ui. I get "it's not reachable". Also port mappings don't show like the other linuxserver containers do, is that normal? Also I can't get the plex.subdomain.conf to work. I've tried it with a host setting and can't get it to work. I followed the instructions in the conf file to no avail. server { listen 443 ssl; server_name plextower.*; include /config/nginx/ssl.conf; client_max_body_size 0; proxy_redirect off; proxy_buffering off; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_plex plex; # proxy_pass https://$upstream_plex:32400; # proxy_pass https://172.18.0.3:32400; proxy_pass https://10.20.30.10:32400; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header X-Plex-Client-Identifier $http_x_plex_client_identifier; proxy_set_header X-Plex-Device $http_x_plex_device; proxy_set_header X-Plex-Device-Name $http_x_plex_device_name; proxy_set_header X-Plex-Platform $http_x_plex_platform; proxy_set_header X-Plex-Platform-Version $http_x_plex_platform_version; proxy_set_header X-Plex-Product $http_x_plex_product; proxy_set_header X-Plex-Token $http_x_plex_token; proxy_set_header X-Plex-Version $http_x_plex_version; proxy_set_header X-Plex-Nocache $http_x_plex_nocache; proxy_set_header X-Plex-Provides $http_x_plex_provides; proxy_set_header X-Plex-Device-Vendor $http_x_plex_device_vendor; proxy_set_header X-Plex-Model $http_x_plex_model; } } With the custom network I'm not sure which settings to change, if it's even possible.

Didn't see any errors. I modified the fetch key to the following if [[ ! -e /root/keyfile ]]; then mkdir -p /unlock mount -t cifs -o rw,nounix,iocharset=utf8,_netdev,file_mode=0777,dir_mode=0777,,vers=3.0,username=myuser,password=mypassword '//MEDIASERVER/index' '/mnt/disks/MEDIASERVER_index' cp -f /mnt/disks/MEDIASERVER_index/unlock.png /root/keyfile # umount /unlock rm -r /unlock fi restarted the server and got the following Sep 23 17:09:00 Tower emhttpd: shcmd (32): echo 128 > /sys/block/sdb/queue/nr_requests Sep 23 17:09:00 Tower emhttpd: shcmd (33): /usr/local/sbin/set_ncq sdd 1 Sep 23 17:09:00 Tower root: set_ncq: setting sdd queue_depth to 1 Sep 23 17:09:00 Tower emhttpd: shcmd (34): echo 128 > /sys/block/sdd/queue/nr_requests Sep 23 17:09:00 Tower kernel: mdcmd (40): start STOPPED Sep 23 17:09:00 Tower kernel: unraid: allocating 31100K for 1280 stripes (6 disks) Sep 23 17:09:00 Tower kernel: md1: running, size: 3907018532 blocks Sep 23 17:09:00 Tower kernel: md2: running, size: 3907018532 blocks Sep 23 17:09:00 Tower kernel: md3: running, size: 2930266532 blocks Sep 23 17:09:00 Tower kernel: md4: running, size: 1953514552 blocks Sep 23 17:09:01 Tower emhttpd: shcmd (35): udevadm settle Sep 23 17:09:01 Tower emhttpd: Opening encrypted volumes... Sep 23 17:09:01 Tower emhttpd: shcmd (37): /usr/sbin/cryptsetup luksOpen /dev/md1 md1 --key-file /root/keyfile Sep 23 17:09:01 Tower root: Failed to open key file. Sep 23 17:09:01 Tower kernel: device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: [email protected] Sep 23 17:09:01 Tower emhttpd: shcmd (37): exit status: 1 Sep 23 17:09:01 Tower emhttpd: shcmd (39): /usr/sbin/cryptsetup luksOpen /dev/md2 md2 --key-file /root/keyfile Sep 23 17:09:01 Tower root: Failed to open key file. Sep 23 17:09:01 Tower emhttpd: shcmd (39): exit status: 1 Sep 23 17:09:01 Tower emhttpd: shcmd (41): /usr/sbin/cryptsetup luksOpen /dev/md3 md3 --key-file /root/keyfile Sep 23 17:09:01 Tower root: Failed to open key file. Sep 23 17:09:01 Tower emhttpd: shcmd (41): exit status: 1 Sep 23 17:09:01 Tower emhttpd: shcmd (43): /usr/sbin/cryptsetup luksOpen /dev/md4 md4 --key-file /root/keyfile Sep 23 17:09:01 Tower root: Failed to open key file. Sep 23 17:09:01 Tower avahi-daemon[11634]: Server startup complete. Host name is Tower.local. Local service cookie is 2421470760. Sep 23 17:09:01 Tower emhttpd: shcmd (43): exit status: 1 Sep 23 17:09:01 Tower emhttpd: shcmd (45): /usr/sbin/cryptsetup luksOpen /dev/sdf1 sdf1 --key-file /root/keyfile Sep 23 17:09:01 Tower root: Failed to open key file. Sep 23 17:09:01 Tower emhttpd: shcmd (45): exit status: 1 Sep 23 17:09:01 Tower emhttpd: Missing encryption key Sep 23 17:09:01 Tower kernel: mdcmd (41): stop Sep 23 17:09:01 Tower kernel: md1: stopping Sep 23 17:09:01 Tower kernel: md2: stopping Sep 23 17:09:01 Tower kernel: md3: stopping Sep 23 17:09:01 Tower kernel: md4: stopping Sep 23 17:09:02 Tower avahi-daemon[11634]: Service "Tower" (/services/ssh.service) successfully established. Sep 23 17:09:02 Tower avahi-daemon[11634]: Service "Tower" (/services/smb.service) successfully established. Sep 23 17:09:02 Tower avahi-daemon[11634]: Service "Tower" (/services/sftp-ssh.service) successfully established.

Thanks for the guidance. trying it now

Can I use a SMB share to access the keyphase?

sure did. The drive is attached to a PCIe m.2 sata adapter. could it be the PCIe card or maybe the PCIe slot?

Seems to be doing it again and the crc error count is increasing Sep 21 10:39:25 Tower kernel: ata5.00: exception Emask 0x10 SAct 0xc SErr 0xc00100 action 0x6 frozen Sep 21 10:39:25 Tower kernel: ata5.00: irq_stat 0x08000000, interface fatal error Sep 21 10:39:25 Tower kernel: ata5: SError: { UnrecovData Handshk LinkSeq } Sep 21 10:39:25 Tower kernel: ata5.00: failed command: WRITE FPDMA QUEUED Sep 21 10:39:25 Tower kernel: ata5.00: cmd 61/00:10:f8:e0:31/0a:00:02:00:00/40 tag 2 ncq dma 1310720 ou Sep 21 10:39:25 Tower kernel: res 40/00:14:f8:e0:31/00:00:02:00:00/40 Emask 0x10 (ATA bus error) Sep 21 10:39:25 Tower kernel: ata5.00: status: { DRDY } Sep 21 10:39:25 Tower kernel: ata5.00: failed command: WRITE FPDMA QUEUED Sep 21 10:39:25 Tower kernel: ata5.00: cmd 61/00:18:f8:ea:31/06:00:02:00:00/40 tag 3 ncq dma 786432 out Sep 21 10:39:25 Tower kernel: res 40/00:14:f8:e0:31/00:00:02:00:00/40 Emask 0x10 (ATA bus error) Sep 21 10:39:25 Tower kernel: ata5.00: status: { DRDY } Sep 21 10:39:25 Tower kernel: ata5: hard resetting link Sep 21 10:39:26 Tower kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Sep 21 10:39:26 Tower kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180531/psargs-330) Sep 21 10:39:26 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20180531/psparse-516) Sep 21 10:39:26 Tower kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180531/psargs-330) Sep 21 10:39:26 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20180531/psparse-516) Sep 21 10:39:26 Tower kernel: ata5.00: configured for UDMA/133 Sep 21 10:39:26 Tower kernel: ata5: EH complete Sep 21 10:40:01 Tower crond[1803]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null

Because I had issues with my docker, I had to delete mariadb (including the container image). I copied my databases to preserve my databases. How do I copy a db folder back into the database folder?

That's great, but not ready to stop worrying just yet. What do I need to look for if things start to go haywire again. What in the logs shows you all is fine? What should I be looking for? Also on the cache drive page, there is a warning about udma crc error count. Will this eventually correct itself?

Replaced the SATA cable on the cache drive. Still having various issues with the cache drive. Rebooting the server took quite a long time. It started the array but hung on "starting services". Not sure if that was because of the read/write issues I am having with the cache drive. My docker containers and vms files all reside on my cache drive. To get array completely up and running I had to change my cache settings in Global Share Settings start the array then change it back. So far everything seems to be working. My concern is the cache drive. I've attached the smart report along with the diag after the cable was replaced. tower-diagnostics-20180921-0847.zip tower-smart-20180921-0823.zip

Need help figuring out what's going on with docker. I had updates to some container and just to update them. I got an error, can't remember what, so I ran common fix which stated "Unable to Write to Docker Images file". Searching for this error in the forum told me to delete my image file and reinstall the apps again. I deleted the docker image file created a new one and started the reinstall. I received the same error as before, so I ran common fix again and got the same "Unable to Write to Docker Images file" error again. At this point I'm not sure what to do. Diagnostics attached Thanks in advance tower-diagnostics-20180920-1639.zip

What’s the command for entering the key phrase from the command line? setting up pfsense on a VM and rebooted the server. Now I can’t get the whole network back up

If I connect it using B-Key slot on the adapter card (also requires a SATA cable attached) UnRaid recognizes the SSD. However trying to run it as a PCIe SSD, UnRaid doesn't Recognize it. It's recognized by the BIOS either way as an SSD Drive.

Has anyone had any trouble adding a SATA SSD M.2 drive to their cache pool?

I need some assistance getting this to work. I add the two scripts to the flash. the fetch_key doesn't load the key file from my windows 10 computer. I checked the firewalls and that's not an issue. What else could it be? What log should I be referencing to see what happens during the boot?

Is it possible to store the UnRaid OS on an M.2 SSD instead of a flash drive? Not looking for performance increase just getting away from the flash drive