DieFalse

1, New Case, New SAS Controller (all new hardware minus drives) (new motherboard, processor, sas controller) Move 12 Drives from old case to new case sliding the last 4 drives to end of available slots. Add 4 new 4tb drives where the old 2tb was that are now at the end of the controller. 1 - Parity 4tb 2 - 4tb 3 - 4tb 4 - 4tb 5 - 4tb 6 - 4tb 7 - was 2tb now new 4tb 8- was 2tb now new 4tb 9- was 2tb now new 4tb 10- was 2tb now new 4tb 11 - now 2tb 12 - now 2tb 13 - now 2tb 14 - now 2tb 15 - 512gb ssd cache 16 - 512gb ssd cache

I just finished building my threadripper build with SAS card in my hotswap case. I now have more 4tb drives to add. Since I have the extra hot-swap bays, I don't want to remove any existing drives but I do want to move my 2tb to the end of my config. My question is, do I shutdown, move drives then boot up and move all drives around, or do I new config, shutdown, then move over? What is the best way? I have removed all data from all drives other than the first 3 drives (4 counting parity) and their location will not be changing.

Ok, so I set this up, configured my router. And attempted to boot a PC with Pxe and it doesn't detect anything from "dhcp". I would assume this uses dnsmasq with proxy enabled?

Right now 32GB however, upgrading today to new board/cpu with 128GB. Damned VM's keep wanting more lol.

What version of unraid are you on, and any issues?

The only thing I can find is 2016 or older. Does anyone have any current and working options for PXE / Netboot servers?

Yes, I especially want more info on the Family Tree wall. I was going to do similar with "AppSpace" displays, but this sounds like a better use since I have a TR1950xalso.

Does this still work or is there a better way? I have had my USB die off and the downtime was not fun nor was getting my backup to actually load correctly.

I feel your conundrum, however, MicroCenter is selling the 1950X TR for $729 right now with $30 off a mobo bundle. I pulled the trigger and build it Saturday.

Thank you all for your responses and especially thank you to PWM for this reply. This is the type of info I was looking for. I have some WD Blacks available and will try that option out as HellDriverUK suggested.

Mostly my fault. I had that thread open reading it and meant to create one but replied instead.

Ok. I have replaced the bad HDD, replaced the USB boot drive. I have also upgraded to 6.5.0 with same issue now 6.5.1-rc1 same issue.

So, I got curious as I used a Purple HDD from my NVR for my parity as it was on hand at the time. 4TB Purple. I never needed parity to rebuild but this command gave me some odd results. Can anyone decipher this? hdparm -N /dev/sda /dev/sda: SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 14 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 14 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 max sectors = 0/1, HPA is enabled

I find myself needing more than the 512GB SSD in space but dont want to use a cache pool to add more. I can get a 2TB SSHD cheap and wanted to see what others thought about SSHD vs SSD for cache drives.

Yes, it will work. The MITX is mounted to the 4 ATX main screws in that case, so no offset needed.

Calculate at 20watts per drive and make sure the rail can handle it on the PSU.

Depending on the exact case model, I think the smallest it will support without modification is ATX. Yes you can add a PCIE HBA (Host Bus Adapter) to the mobo for more ports. We typically use SAS cards with Sata breakouts. Like the LSI SAS9201-16i

Perfect!!!! That got what was different. 'overwrite.cli.url' => 'https://my.xxxxxxxxx.com/nextcloud', needed to be 'overwrite.cli.url' => 'https://my.xxxxxxxxx.com', now this works as anticipated. No clue why that would cause it to revert to https://IP vs domain.... strange! Thank you for supporting and helping even though its not 100% identical. It was very helpful.

My config.php is not complicated.... its the one you posted.... Maybe you mis-read and thought the nginx site conf was also in the config.php? here is Just the config.php ( and I will simplify it even more by removing redundancies) Config.php which has the overwritewebroot in it already. <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'ocgu1s592brc', 'passwordsalt' => 'saltremoved', 'secret' => 'secretremoved', 'trusted_domains' => array ( 0 => '192.168.1.175:444', 1 => 'my.xxxxxxxx.com/nextcloud', ), 'trusted_proxies' => array ( 0 => '192.168.1.175', 1 => 'my.xxxxxxxxxx.com', 2 => 'my.xxxxxxxx.com/nextcloud', ), 'overwritewebroot' => '/nextcloud', 'overwritehost' => 'my.xxxxxxx.com', 'overwrite.cli.url' => 'https://my.xxxxxxxxx.com/nextcloud', 'overwriteprotocol' => 'https', 'dbtype' => 'sqlite3', 'version' => '13.0.0.14', 'installed' => true, MAIL INFO REDACTED );

My "Domain.com" is under a commercial SSL certificate. I am using LE for my.domain.com only. I can not use domain.com to create a wildcard through LE. I don't want to continue to derail the thread to figure that issue out as I am soon going to be registering a new domain for use solely for the server, so I will address that then. As for this config, here are the two files I modified: Config.php <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'ocgu1s592brc', 'passwordsalt' => 'saltremoved', 'secret' => 'secretremoved', 'trusted_domains' => array ( 0 => '192.168.1.175:444', 1 => 'my.xxxxxxxx.com', 2 => 'www.my.xxxxxxxx.com', 3 => 'cloud.xxxxxxxx.com', 4 => 'nextcloud.xxxxxxx.com', 5 => 'my.xxxxxxxx.com/nextcloud', ), 'trusted_proxies' => array ( 0 => '192.168.1.175', 1 => 'my.xxxxxxxxxx.com', 2 => 'nextcloud.xxxxxxx.com', 3 => 'my.xxxxxxxx.com/nextcloud', ), 'overwritewebroot' => '/nextcloud', 'overwritehost' => 'my.xxxxxxx.com', 'overwrite.cli.url' => 'https://my.xxxxxxxxx.com/nextcloud', 'overwriteprotocol' => 'https', 'dbtype' => 'sqlite3', 'version' => '13.0.0.14', 'installed' => true, MAIL INFO REDACTED ); LE-NGINX-siteconf-default server { listen 80; server_name my.xxxxxxxx.com nextcloud.xxxxxxxxx.com cloud.xxxxxxxxx.com; return 301 https://$server_name$request_uri; #enforce https } server { listen 443 ssl http2 default_server; root /config/www; index index.html index.htm index.php; server_name my.xxxxxxxxx.com nextcloud.xxxxxxxxx.com cloud.xxxxxxxxx.com; #add_header Strict-Transport-Security max-age=31536000 always; add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ssl_prefer_server_ciphers on; client_max_body_size 0; #PLEX location /web { # serve the CSS code proxy_pass http://192.168.1.175:32400; } #Main /plex rewrite location /plex { # proxy request to plex server proxy_pass http://192.168.1.175:32400/web; } location /stats { #proxy plexpy to server proxy_pass http://192.168.1.175:8181; } location /jackett { #proxy jackett to server proxy_pass http://192.168.1.175:9117; } location /couch { #proxy couchpotato to server proxy_pass http://192.168.1.175:5050; } location /sonarr { #proxy sonarr to server proxy_pass http://192.168.1.175:8989; } location /nowshowing/ { #proxy nowshowing to server proxy_pass http://192.168.1.175:6878/; } location /nextcloud { proxy_pass https://192.168.1.175:444/nextcloud; } location /htpc { #proxy htpcmanager to server proxy_pass http://192.168.1.175:8085; } location /request { return 301 $scheme://$host/request/; } location /request/ { proxy_pass http://192.168.1.175:3579; proxy_set_header Host $host; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Ssl on; proxy_set_header X-Forwarded-Proto $scheme; proxy_read_timeout 90; proxy_redirect http://127.0.0.1:5000 https://$host; } if ($http_referer ~* /request/) { rewrite ^/dist/(.*) $scheme://$host/request/dist/$1 permanent; } }

I ran into a problem where my SSL is not valid for https://sub.vanitydomain.com as I use a ssl for https://my.vanitydomain.com so I have to use /nextcloud to use this SSL, also, with 1&1 hosting, I can not get https://nextcloud.vanitydomain.com to goto a "port" as I can only forward 443/80 to one IP in my network. If I put nextcloud.vanitydomain.com I have no way to point it to nexcloud directly. The ONLY thing from the guide that changed was pointing to the /nextcloud instead of x.y.z There has to be a setting or configuration that changes the domain call to the internal IP. I understand the not "supporting" but can you atlease point me to what would revert to internal vs external? I have the overwrite cli/web/host all set to the right endpoints. I followed the guide in the first post and the link to the "letsencrypt nginx settings page" which also spoke about /x and showed the example for it.

I followed the tutorial in the first post and all works on the local network. When accessing the reverse proxy outside of the network it changes my domain to my internal IP and fails. from: https://myvanitydomain.com/nextcloud to https://192.168.1.175/nextcloud/ If I am on VPN it works app and all, off VPN, it fails due to this. What would cause this?

I ended up getting pretty lucky and found a Norco RPC-4116 for $295 (free shipped) which will allow me to use my blu-ray drive and add a 1x5.25 to 8x2.5 hot swap tray also. This will use all 24 drives of my license and fit nicely. I am glad yours sold and thanks again for offering it to me! now all I need is a good SAS card (I have 10 on-board sata ports, now I need 14 more lol)

Yes it is reverse proxies through nginx letsencrypt, I have read back to page 6 and only see one mention of a grey login screen but have yet to see what causes it or the proposed fix. I can access it locally non proxied so I can assume it's in the reverse proxy configuration and maybe a permissions of a resource it cant see, kind of like serving the plex css addition of /web to make plex work correctly. Am I atleast on the right track?

I've been using and love this docker for several months now, however with the latest update (now has backgrounds on login page) the page will not load on any mobile devices. It says "Loading...." and then blanks out. Has anyone heard or seen this problem yet?