kaiguy

Happy Pro-license user since 2010 (you were, what, 5 at the time?). First build was an i3 in a tower case. I actually just recently retired one of the last remaining drives from that build--not even due to errors, just wanted to rid my system of all old Green 2TB drives for speed purposes. Then, like many people here, I did a JohnM Atlas-clone build around 2012. Aside from adding another HBA and many, many disks, my server has pretty much remained the same since then, happily chugging away 24/7. Unraid is great for many reasons: the drive aggregation, the continual evolution (VMs, Dockers FTW), the reliability, the community... I've probably turned 10-12 people on to Unraid, and I don't even have many tech-inclined friends. Happy Birthday, Unraid!!

This issue popped up for me last night and its been bugging me ever since. I have Plex data on an unassigned SSD, was direct streaming/direct playing a file, and I started getting constant hangs while watching a video. Perhaps it was because I was trying to watch a 4K remux, but I still experienced this issue with the file on the cache array. Cache is connected via mobo SATA3, whereas my parities and data drives are connected via a IBM1015/LSI/expander... so I'd think the mover process wouldn't interfere with the cache at all.

Just purchased this app. Excellent job! Question--have you ever revisted the request to implement unassigned devices? Even if its limited, like simply showing the devices and space on the disks view?

I just copied my whole sonarr appdata directory as a backup and upgraded in place. Been working great. My guess is it changes the database, so I wouldn't assume going back to stable will be possible. But if you try running it for a few days and don't like it, you can always just restore your backed up folder and won't be too far out of date.

Is there any way to access the phantom branch (sonarr v3) with this container? I know develop is an option, but my gut tells me that the container itself needs to be able to support the given branch for me to be able to just change a tag and update... Edit: Nevermind. I just changed the repository within the container to lsiodev/sonarr-preview and it started right up!

Appreciate the tip. Thanks again!

Thanks all. I'm comfortable with the flashing process (did the crossflash with my M1015 years ago), but I just hadn't found much info related to the 9201-8i as it relates to flashing firmware (especially since there seems to be no official 9201-8i firmware). I'll give it a go!

Can anyone please confirm that I can flash 9211-8i firmware on a 9201-8i card? And in the process remove the BIOS? Thanks!

Thanks for this! The only reference to port 443 I could find was: tcp6 0 0 :::443 :::* LISTEN 5814/docker-proxy Which I believe would be the LE container. Not sure why it won't let me start the container with 443... especially since it's been working fine for months.

I'm suddenly running into a problem where it appears LetsEncrypt container won't load because 443 is already in use. But I don't even have SSL enabled on my server, and prior to disabling, I sent the HTTPS port to 444. No changes to my server config, but I did have an unclean shutdown and am having a parity check (but that really shouldn't have any effect). /usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint letsencrypt (7c3343119f45bcf4276a0xxxxxxxxxf6791f5be978ae5): Bind for 0.0.0.0:443 failed: port is already allocated. I can't figure this one out! Any thoughts? THANKS!

Thanks for continuing to maintain this plugin! Just FYI -- I updated and the NUT service never started back up. I had to manually toggle the NUT service off then back on within the plugin settings. Now it appears to be working as expected.

Hmm... I get that if its coming in from outside, the port forward 443 to the correct internal host port would work as expected. On the LAN, the host port is listening on 8062, and you're connecting on https (443)... so unless you're leaving your LAN to make that connection, I don't know how this would work without specifying the port (https://plexpy.mydomain:8062)... But I could very well be missing something. Does your plexpy/reverse proxy container have a different IP than your unraid box?

Except on the local network, right?

If I want to continue using this container for reverse proxy, combined with the new RC with LetsEncrypt support, I'm going to need to use my second NIC and assign all my Docker containers their own IPs in order to not have a port 443 conflict, right? I'm having some trouble visualizing how best to move forward...

Is there any reason the delete.ds_store script wouldn't actually delete all the .ds_store files? Tried it last night after Fix Common Problems found a bunch of duplicate .ds_store files spanning pretty much all of my shares. I disabled the creation of .ds_store files on my Macs, ran the user script, then ran the Fix Common Problems extended test again. Still had many, many dupes. So I went through and manually deleted them. Just curious if I did something wrong, or that script perhaps needs an update. Thanks!

Mine is set up the same way as above, but instead of nobody / users I went with 99 / 100. Same result.

For whatever reason, I've had to increase the number of connections in nzbgbet to get to the same download speed as sab. No clue why that is. I've got a 300mbps connection and I am able to saturate my download. You may also want to take a look at performance tips on the nzbget wiki. Though my server is pretty beefy, I reduced the logging level as I just don't need that writing to my SSD constantly for every little thing.

Thanks, all, for clarifying. dmacias, I was curious if I'd have to manually add a dnsmasq entry in merlin, so I appreciate you specifically mentioning that. Last question hopefully--I installed the letsencrypt container, exposed appropriate ports, got the certs for my domain and subdomain... https://internal.ip.of.unraid works fine (albeit the cert doesn't like the url), but I can't get into http://internal.ip.of.unraid:81 ... Does the http not matter since the whole point is we're using https now? Just want to make sure this is by design before I continue on... Edit: Nevermind. I went ahead and set it up even though I can't access port 80 (actually 81) internally. As long as I reference https locally, I can access all the server apps. Forcing 80 to 443 redirect externally. Thanks again for the writeup!

I completely understand the concept and appeal to be able to securely access your services remotely, but how would this impact local use? I assume you wouldn't be going to your domain (I feel like my router wouldn't allow that) but still access your various services via the traditional methods when on your internal network. If some of the apps (like sonarr, for instance) require changing the URL base, would that just mean I'd have to change the way I locally access sonarr on my network (e.g., internalip:8989/sonarr)?

unRAID version of Plex is meant to run natively as a plugin on Slackware. Docker does not run Slackware.

Thanks, sparkly. Can confirm that Plex corrected the issue and the container now updates as expected.

I wrapped up my conversion from RFS to XFS last week. Since I have only one parity disk, I was able to do the drive reassignments with the "new config" tool and assignment swaps as detailed without mucking with my user shares. I followed the tutorial on the wiki and I'm happy to report that a parity check after all 10 drives were converted came back with zero sync errors! Looks like it even slightly sped up my parity check speed as well. But most importantly, I'm just glad my array doesn't spin up now when I update or stop a Docker as it was doing with my RFS-formatted drives. Not sure if you'd like to reflect in the wiki that it's now confirmed that the process works... Thanks to all who contributed!

Yep, same issue here: Atempting to upgrade to: https://downloads.plex.tv/plex-media-server/%20/plexmediaserver_%20_amd64.deb: 2017-02-02 09:32:29 ERROR 404: Not Found. ######################################################## # Upgrade attempt failed, this could be because either # # plex update site is down, local network issues, or # # you were trying to get a version that simply doesn't # # exist, check over the VERSION variable thoroughly & # # correct it or try again later. # ######################################################## Edit: Using the "latest" variable (since I am a PlexPass holder) on unRAID 6.2.4...

Here it is:

Of course. I'm about halfway through converting another drive, so I should have a screenshot this evening after work.