Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Ntouchable

  • Rank
  1. I managed to fix this eventually in the following way: Mounted Let'sEncypt config files to inside the Plex docker config in the following manner: /letsencrypt = /mnt/user/data/letsencrypt/ Plex settings in browser > Network > Custom certificate location = /letsencrypt/keys/letsencrypt/privkey.pfx Custom certificate encryption key = /letsencrypt/keys/letsencrypt/privkey.pem Custom certificate domain = plex.XXXXXX.com Custom server access URLs = https://plex.XXXXXX.com:443 In the file in /mnt/appdata/letsencrypt/nginx/proxy-confs/plex.domain.conf > change the line "proxy_pass https://$upstream_plex:32400" to proxy_pass https://UnRaidServerIP:32400 Optional - 301 redirect so that it forces https - Go to /mnt/appdata/letsencrypt/nginx/site-confs/default > remove the "#" signs next to the code: server { listen 80; server_name _; return 301 https://$host$request_uri; } Optional - Plex UI in browser > Network > Secure connections = Required. Hope this helps someone out there.
  2. I have recently set up UnRaid mostly following "SpaceInvader One's" youtube videos. In particular this one - I struggled a lot to get it set up initially until I eventually realise that I could not port forward to WAN due to Carrier Grade NAT. I managed to get in contact with my ISP who were able to sort me out with a static IP. I have since managed to get https and my domain name working with LetsEncrypt and Nextcloud. However, I cannot seem to get Plex working with https and my domain name. It have managed to set it up behind the reverse proxy like so: And if I open up Plex I it is shows the green tick for Remote Access and I can connect remotely with my phone, etc. However, the last piece of the puzzle I have struggled with over the last month is: HTTPS - How to get https working using Let's Encrypt? Domain Name - How to set up Plex such that I can access it by simply going to "plex.mydomainname.com" in my browser? (I have pfSense running on my router with port 32400 forward to my UnRaid server). I assume I am probably missing something relatively obvious...
  3. Update Everything seems to be working fine. I ran a "Filesystem Check" in Maintenance mode and it came back without any errors.
  4. @ Johnnie.black It appears to be working. I will confirm once disk is completely rebuilt. Thank you very much. *fingers crossed*
  5. Yes, I know which disk is which. I can even mount the remaining data disk in unassigned devices and browse it.
  6. Disk 1, Disk 2, Parity. I use the server as a switch too, so it is currently running with the array stopped. I have the dead disk in my PC at the moment. I have recovered some stuff from the good sectors. A lot of the data is corrupt though.
  7. Diagnostics Zip attached. I still have the original disk. PERC 6/i is some kind of old dell raid controller, which I use to set all the drives up individually. Starting to realise this might not be ideal when something goes wrong... tower-diagnostics-20190315-1445.zip
  8. Context: Dell R710ii + PERC 6/i - Brought 6 months ago on eBay. 3 x WD Red Drives - 2 Data drives + 1 Parity Been using Linux for a few years. Earlier this week one of my hard drives failed - one of the 2 data drives. I have a replacement to swap in that has arrived from Amazon. My problem starts after installing a new hard drive: When the drive failed I had to reconfigure them in the Dell Config menu, which gives the drives new ID's. When I tried to assign the drives to the array, it just said "Wrong" next to them. As a result of some Googling I did the following: - Tools > NewConfig > Preserve Current Assignments > All > Proceed. Assigned the drives to their corresponding slots > Tick Parity is already valid: "Warning - If parity is already valid, both data drives must have original data." Cancel Not quite sure how to proceed at this point. How do I rebuild the lost data onto my new hard drive, using the parity drive and my other good data drive? Any help much appreciated.